*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> Changed that ... same result. On a lark, I tried dhcp-2.0b1p23;
> however, I got the same result. I noticed in looking at those
> packets, that there is a vendor flag set for joind but not dhcp
> in the server reply...
Right, that's the problem. Fixed in the next snapshot - you can set
a flag, "always-send-rfc1048" to indicate that even though the client
is brokenly not sending the right magic cookie, you want the BOOTP
response to contain an RFC1048-style vendor extensions field anyway.
I've also added some trivial code so that if you get a non-RFC1048
bootrequest packet, it's logged as such so that you can see why it's
happening and know to grep for rfc1048 in the manual page... :')
_MelloN_
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
------------------------------------------------------------------------------
