*** From dhcp-client -- To unsubscribe, see the end of this message. ***
I would like to point out that the problem you are experiencing is
probably that @Home's DHCP server is violating the DHCP protocol
specification. This is why you are losing. They are doing this to be
compatible with some windows breakage, so it's hard to blame them, but
nonetheless, this is what's going on.
So while I agree that it's sad that NT is working better than the ISC
client, the reason it's working better is that @Home's DHCP setup has
been broken to accomodate NT, not that the ISC client is hard to set
up. In most situations, the ISC client is very easy to set up. Sigh.
Anyway, now that I've gotten that off my chest (grin) let's address
your immediate needs.
> One thing I wondered about was the identifier: the "01:" in
> front of the MAC address. Is that correct?
The 01 is correct, assuming that your network interface is an ethernet
card. Search for "Client-identifier" in doc/rfc2132.txt for
details. This is what the Windows client will send too.
As to the hostname thing, try this:
send host-name 43:35:39:30:34:33:33:36:2d:41:0;
This duplicates a Win95 bug which may still be in Win98 that causes
the client to NUL-terminate any ASCII strings it sends.
Failing that, run tcpdump as you boot your Win98 or NT system and send
me the trace. The command line to tcpdump should be:
tcpdump -vv -x -s 1500 -e udp port 67
_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.
------------------------------------------------------------------------------
