*** From dhcp-server -- To unsubscribe, see the end of this message. ***
I doubt that Linux will think it is a MS client, since the code checks the
other way (assumes Non-Microsoft if the hostname coming from the client does
not contain a null character at the end of the option).
Our NWT also uses dhcpcd for the client, and we work fine with Microsoft and
Non-Microsoft DHCP servers, the problem, as I understand it, is that CE
provides the DHCP code as a DLL without providing enough information to do
anything useful (we had to reverse engineer quite a bit to do what we are
currently doing on it (on our WBT, not our NWT)).
Looking at this and a few other responses, I think I was being
misunderstood... Let me try to rephrase... The problem is with the ISC
server failing to detect the CE WBT as a Microsoft client (it thinks that
the CE WBT is an RFC 2132 compliant client [according to the BOOTP Extension
/ DHCP Option Field Format description]). Linux clients don't put the null
in the hostname, so should always be interpreted as Linux clients.
Dave
> -----Original Message-----
> From: Michael H. Warfield [SMTP:[EMAIL PROTECTED]]
> Sent: Friday, April 02, 1999 4:10 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Detecting Microsoft / Non-Microsoft clients
>
> *** From dhcp-server -- To unsubscribe, see the end of this message.
> ***
>
> Off on a subject other than Windows CE...
>
> Dave Gotwisner enscribed thusly:
> > Looking at 2.0 patch level 18, the software expects a hostname field
> coming
> > from the client in order to determine Microsoft / non-Microsoft for null
> > termination. Windows CE does not send a hostname (or any other options
> :()
> > although it still requires a null terminator.
>
> Huh? Oh sh****... And what happens when I set up a Linux box to
> specify the hostname when requesting an address? What happens if the
> server thinks that this Linux box is a Microsoft client? :-)
>
> I currently do that with the -h {hostname} option to dhcpcd
> (yes, the other dhcp client program). I see that it can also be done
> with the dhclient program, just not as easy (since the host name is
> buried in the config file).
>
> Then there is also the "pump" program which is in the new RedHat
> StarBuck (RedHat 5.9 - Pre 6.0 Beta), which is yet another dhcp client.
> I noticed that it doesn't currently send the hostname over to the server
> and I was just getting ready to try and figure out how to make it do
> that as well.
>
> I do that so that I can get the dynamic DNS to pick up the name
> of the Linux system and insert it into the DNS. If dhcpd is interpreting
> that field to indicate that this is a Microsoft box, what's going to
> break when it's wrong?
>
> [...]
>
> Mike
> --
> Michael H. Warfield | (770) 985-6132 | [EMAIL PROTECTED]
> (The Mad Wizard) | (770) 925-8248 |
> http://www.wittsend.com/mhw/
> NIC whois: MHW9 | An optimist believes we live in the best of all
> PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
>
>
>
> --------------------------------------------------------------------------
> ----
> 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.
> --------------------------------------------------------------------------
> ----
------------------------------------------------------------------------------
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.
------------------------------------------------------------------------------
