*** From dhcp-client -- To unsubscribe, see the end of this message. ***
> The problem is repeatable by disconnecting the ethernet link
> to the ASDL modem, killing dhclient, and restarting it the same way as
> always. Again, this is a straight-laced Slackware 3.6 system with kernel
> 2.0.36.
It really depends on the kernel. You could argue that dhclient
shouldn't try to ping the router at all when it's in the INIT-REBOOT
state - it should just adopt the lease. Maybe I should make this
configurable. The reason it's the way it is is so that if you roam
to sites that don't do DHCP (all fourteen of them in the continental
U.S. :') you can still have your DHCP client autoconfigure the
network. However, if you're not roaming to such sites, pinging the
router is superfluous.
> If I use Win95 to connect to the same hookup and bring it up in
> winipcfg, I get the machine's name as part of the internet address
> (i.e. bruce.rdu.bellsouth.net) instead of what I expected, which
> was something very much like adsl-77-240-47.rdu.bellsouth.net. Does
> anyone know if this is Win95 playing a trick or is there really a
> way for me to influence the name of the system via DHCP? If I can
> influence it, how can I set up the dhclient to do it?
What's displayed in winipcfg is the name you gave your machine,
concatenated with the domain name supplied by the DHCP server. The
DHCP server is informed of the name you chose, but probably isn't
doing anything with it. Have you tried doing an nslookup on the name
that winipcfg is reporting?
_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.
------------------------------------------------------------------------------
