dhcpd on Solaris 10

[A.L.M.Buxey at lboro.ac.uk]

Hi,

> 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.


alan