*** From dhcp-client -- To unsubscribe, see the end of this message. ***
> I guess what I am trying to say is that regardless of whether or not
> I have connectivity, I shouldn't get a "network unreachable" error
> from ping (indicating the route table is not set up). I was
> expecting the interface and route table to be programmed from the
> old lease info and therefore I would receive a timeout from not
> seeing a response from the other side when I had my connectivity
> issue.
The interface and route table info _is_ programmed before the ping is
attempted, unless there's a bug in the client script. I'd welcome
any efforts you'd care to undertake to see what's going on - I don't
have a Linux system on which I can test or debug this. My suspicion
is that the script is actually doing the right thing, but that when
Linux fails to ARP the router, the error you get is "no route to
host." That's just a guess, though.
> In any case, thanks to you and for all who worked hard developing and
> testing this software. It had been very useful to me and it saved me from a
> need to implement a M$ solution just to talk ADSL!
You're welcome!
_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.
------------------------------------------------------------------------------
