dhcpd on Solaris 10
jason.penton at gmail.com
Sat Apr 25 16:54:08 UTC 2009
So why is it that when a client receives an OFFER with a zeroed
siaddr, it never sends out the DHCP REQUEST (as if it was unhappy with
the OFFER). I tested with Windows, linux and solaris clients??????? On
a linux box, the EXACT same code with the EXACT same config (i.e. no
next-server setting) the siaddr is set to the ip address of the DHCP
On Sat, Apr 25, 2009 at 6:39 PM, <A.L.M.Buxey at lboro.ac.uk> wrote:
>> I'd imagine that on other OS's (linux) the siaddr is set
>> automatically. Seems that on Solaris 10 update 6, it does not.
> to quote the post 3.0.2 changelog
> The siaddr field was being improperly set to the server-identifier when responding to DHCP messages. RFC2131 clarified the siaddr field as meaning the 'next server in the bootstrap process', eg a tftp server. The siaddr field is now left zeroed unless next-server is configured.
> dhcp-users mailing list
> dhcp-users at lists.isc.org
More information about the dhcp-users