[gPXE] DHCP Cleint ID in gPXE 1.0.0?
Jonathan Andrews
jon at jonshouse.co.uk
Sat Mar 20 08:33:41 EDT 2010
> So about that DHCP request packet modification business... I'd like
to
> ask community-wide, has anyone else come across the situation Steven
> Shiau describes, where their server gives gPXE one IP and the
> finally-booted OS another? It might be good to get a sense of how
> common it is, in order to prioritize work on it.
>
Some comments on this :
1) Why is that an issue ? So what if the IP changes, the MAC didn't !
Some DHCP servers try and push the same IP back to the same MAC, some
fully respect the data in the request field, the second option is more
correct - but less pleasing
2) "static" assigned DHCP clients seem to always be honoured if the
server implements it
3) IP changes when clients are substituted are not uncommon, for example
if I use the linux kernel DHCP client, then use the userspace "dhclient"
the lease is not handed over and the IP *sometimes* changes
4) The ClientID field is simply a way for the author of the protocol to
say "Non MAC based networks could use this too" - I personally would
ignore the hell out of it, if some 3rd party SAN box vendor or M/Soft
decide to use it my bet is that they miss use it !
Cheers,
Jon
More information about the gPXE
mailing list