Torgeir.Wulfsberg at kongsberg.com
2012-Nov-22 13:32 UTC
[syslinux] Syslinux Digest, Vol 116, Issue 20
Hi!
We use Windows tftp-servers (so I dont think switching now would be an
alternative). But I can try to suggest it.
More specific, vendor id of the mac address, is what I want to be able to
"choose" (if match) which bootmenu to display.
Like all broadcom NICs we have would boot the undionly.kpxe "menu!! (I am
having some trouble with broadcom (PCI fiber) and iPXE :)
And the rest would use ipxe.pxe (works best for our setup).
Would it be much work to implement or rather have available as an patch, so if
anyone else are in need of this later, we could just patch the code and compile
ourself.
Torgeir
________________________________________
Message: 3
Date: Wed, 21 Nov 2012 10:19:14 -0800
From: "H. Peter Anvin" <hpa at zytor.com>
To: syslinux at zytor.com
Subject: Re: [syslinux] pxelinux load configuration files (ARP type
code, and IPaddress in hex)
Message-ID: <50AD1B22.6050004 at zytor.com>
Content-Type: text/plain; charset=UTF-8
On 11/21/2012 06:49 AM, Torgeir.Wulfsberg at kongsberg.com
wrote:>
> Is is possible to make pxelinux look for MAC and IP, removing one hex digit
(or 2 for mac) and try again like this:
>
> /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd
> /mybootdir/pxelinux.cfg/C000025B
> /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc
> /mybootdir/pxelinux.cfg/C000025
> /mybootdir/pxelinux.cfg/01-88-99-aa-bb
> /mybootdir/pxelinux.cfg/C00002
> /mybootdir/pxelinux.cfg/01-88-99-aa
> /mybootdir/pxelinux.cfg/C0000
> /mybootdir/pxelinux.cfg/01-88-99
> /mybootdir/pxelinux.cfg/C000
> /mybootdir/pxelinux.cfg/01-88
> /mybootdir/pxelinux.cfg/C00
> /mybootdir/pxelinux.cfg/01
> /mybootdir/pxelinux.cfg/C0
> /mybootdir/pxelinux.cfg/C
> /mybootdir/pxelinux.cfg/default
>
> We could be in need for a custom file/menu for this group of addresses (as
an example): /mybootdir/pxelinux.cfg/01-88-99-aa
>
Not really very useful; besides the rather obvious ambiguity, there
simply isn't a lot of locality in MAC space.
There *may* be some value in specifically the OID portion of the MAC
address (the 01 for Ethernet plus three octets), but I have yet to hear
a compelling enough use case for everyone else to take the load time
penalty.
-hpa
________________________________
CONFIDENTIALITY
This e-mail and any attachment contain KONGSBERG information which may be
proprietary, confidential or subject to export regulations, and is only meant
for the intended recipient(s). Any disclosure, copying, distribution or use is
prohibited, if not otherwise explicitly agreed with KONGSBERG. If received in
error, please delete it immediately from your system and notify the sender
properly.
Which of these are you doing, if any?:
1. Native PXE -> iPXE -> PXELINUX
2. Native PXE -> PXELINUX -> iPXE
If you are doing #1, then you can control which config-file PXELINUX will
use by setting options 209 and 210 from an iPXE script or the iPXE shell.
If you are doing #2, then if we forget about patching PXELINUX for a moment,
is your deeper goal simply for PXELINUX to choose the right iPXE based on
the MAC address?
- Shao Miller
-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On
Behalf Of Torgeir.Wulfsberg at kongsberg.com
Sent: Thursday, November 22, 2012 08:33
To: syslinux at zytor.com
Subject: Re: [syslinux] Syslinux Digest, Vol 116, Issue 20
Hi!
We use Windows tftp-servers (so I dont think switching now would be an
alternative). But I can try to suggest it.
More specific, vendor id of the mac address, is what I want to be able to
"choose" (if match) which bootmenu to display.
Like all broadcom NICs we have would boot the undionly.kpxe "menu!! (I am
having some trouble with broadcom (PCI fiber) and iPXE :)
And the rest would use ipxe.pxe (works best for our setup).
Would it be much work to implement or rather have available as an patch, so
if anyone else are in need of this later, we could just patch the code and
compile ourself.
Torgeir
________________________________________
Message: 3
Date: Wed, 21 Nov 2012 10:19:14 -0800
From: "H. Peter Anvin" <hpa at zytor.com>
To: syslinux at zytor.com
Subject: Re: [syslinux] pxelinux load configuration files (ARP type
code, and IPaddress in hex)
Message-ID: <50AD1B22.6050004 at zytor.com>
Content-Type: text/plain; charset=UTF-8
On 11/21/2012 06:49 AM, Torgeir.Wulfsberg at kongsberg.com
wrote:>
> Is is possible to make pxelinux look for MAC and IP, removing one hex
digit (or 2 for mac) and try again like this:>
> /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd
> /mybootdir/pxelinux.cfg/C000025B
> /mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc
> /mybootdir/pxelinux.cfg/C000025
> /mybootdir/pxelinux.cfg/01-88-99-aa-bb
> /mybootdir/pxelinux.cfg/C00002
> /mybootdir/pxelinux.cfg/01-88-99-aa
> /mybootdir/pxelinux.cfg/C0000
> /mybootdir/pxelinux.cfg/01-88-99
> /mybootdir/pxelinux.cfg/C000
> /mybootdir/pxelinux.cfg/01-88
> /mybootdir/pxelinux.cfg/C00
> /mybootdir/pxelinux.cfg/01
> /mybootdir/pxelinux.cfg/C0
> /mybootdir/pxelinux.cfg/C
> /mybootdir/pxelinux.cfg/default
>
> We could be in need for a custom file/menu for this group of addresses (as
an example): /mybootdir/pxelinux.cfg/01-88-99-aa>
Not really very useful; besides the rather obvious ambiguity, there
simply isn't a lot of locality in MAC space.
There *may* be some value in specifically the OID portion of the MAC
address (the 01 for Ethernet plus three octets), but I have yet to hear
a compelling enough use case for everyone else to take the load time
penalty.
-hpa
________________________________
CONFIDENTIALITY
This e-mail and any attachment contain KONGSBERG information which may be
proprietary, confidential or subject to export regulations, and is only
meant for the intended recipient(s). Any disclosure, copying, distribution
or use is prohibited, if not otherwise explicitly agreed with KONGSBERG. If
received in error, please delete it immediately from your system and notify
the sender properly.
_______________________________________________
Syslinux mailing list
Submissions to Syslinux at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.
Maybe Matching Threads
- pxelinux load configuration files (ARP type code, and IPaddress in hex)
- pxelinux search order for configuration file
- pxelinux properly configured cannot find "default" configuration file
- Confusion on lpxelinux vs. gpxelinux vs. ipxe vs gpxe.
- SYSLINUX 3.73 release imminent