Re: dhcp-client cleanup

Bit Twister wrote:
On Sun, 26 Feb 2006 16:38:41 -0500, cga wrote:

# dhclient --help
Internet Software Consortium DHCP Client
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.



Well there you are, you need a new and improved client.

$ dhclient --help
Internet Systems Consortium DHCP Client V3.0.3
Copyright 2004-2005 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Usage: dhclient [-1dqr] [-nw] [-p <port>] [-s server]
[-cf config-file] [-lf lease-file][-pf pid-file] [-e VAR=val]
[-sf script-file] [interface]

He he.. the problem here is that this older version is the one I have in sarge .. the system that never had a problem connecting.. But this is a useful lead. I don't know for sure what version etch installed but on sarge there is a dh3client package available - which I did not install - and that should be more or less the one you're running..



That is normaly a day one condition and would expect that.


meaning the lease only gets written to disk after you shut down the system..?


No, when the client gets it's first lease.



... or more of a timing issue.. networking is started too early and does something that makes further manual attempts fail..


I know with an old release of my software and a slow dhcp server, I
would miss a lease. I created a network_ck script to ping the gateway
and if failed, re-run the network script and would get a lease.

marginally possible.. I never thought of running ifup in a loop to check whether I would eventually obtain a lease after a few dozen attempts.



It would seem, you could release the ip lease under win98, boot etch to
rule out dhcp server interaction about assigned IP address.



I tried that but it did not work.. that's why I was thinking that something happens when I start etch that partly initializes the connection process.. fails.. and leaves me in a "funny" state where further attempts to bring up the connection manually just fail..otoh as I mentioned earlier.. if I wait long enough it would seem that I am all of a sudden able to bring up the connection.. my guess being that the dhcp server at the other end eventually detects that I am not connected and does some cleanup.. have not evidence this is the case, though.. just a hunch..


I understand, but, you started out wanting to have the server reset.

Well not reset the server .. just be able to tell it to clean up everything that concerns me. The problem I am trying to work around is the fact that my ISP only support Windows PC's and MAC's.. So I can't just pick up the phone .. complain that I am unable to obtain a lease reliably and ask them to look into it.. Since I do not have access to their dhcp setup I'm pretty much stuck with the guessing game approach ... unless I choose to spend countless hours tracing the actual dhcp packets and - perhaps - eventually figuring out what's going on.

We showed the problem did not clear up when you released the ip addy
with windows.

my impression is that whatever etch does at bootup fails but does not leave me with a clean slate. If I boot into windows.. release the lease and then boot into sarge.. I am connected with a new lease.. never fails.. if I do the same thing with the etch system it always fails at bootup and ensuing attempts to bring up my connection manually are almost always unsucessful.. So my impression is that it not only fails but whatever it does messes up things so that I am unable to connect manually thereafter..

Since you are using the same hardware, you should have received a lease.


etch installs a 2.6.12 kernel by default - that's the reason I installed it in the first place.. I needed a recent 2.6 kernel for a totally different reason - and these new kernels use that new udev, hotplug, devfs stuff so even though the hardware is the same, the software that handles it has undergone drastic changes.. and my feeling is that - at least where I and my ISP are concerned - the debian scripts that handle the connection at startup do no do the right thing.. That's why I thought I could try disabling them.. realeasing the lease.. and then running ifup manually might be successful and that could give me some understanding of what's going on.

I would get a new and improved dhclinet

I suppose I could download the v3 version of the dhclient package using my sarge connection and install it on the etch system.. likely to be messy since the dh3client might have dependencies and I might have to upgrade/install a bunch of other things..

before doing anything else.
You still maybe stuck with reading dhcp packets.

I would hate to have to do that without being able to see how they are configured at the other end.. After all while my ISP are doing some form of dhcp I would not be surprised if they had tweaked it one way or another to suit their "business needs" .. wouldn't be the first time a commercial entity add their own "enhancements" to the standard as described in the rfc's.

I'm beginning to think that it might be easier to install sarge on a gateway machine and connect the laptop to it ;-)

Thanks.
.

Relevant Pages

  • Re: Advanced WinINet - Please HELP!
    ... You'd have to actually verify that DHCP packets are making it through the ... when the lease expires without the device being able to renew it first. ... You can detect that a connection has changed and terminate your current ... or whatever), you could trigger the FTP process, again. ...
    (microsoft.public.windowsce.embedded.vc)
  • Re: DHCP too slow - trying to cache
    ... wi-fi television remote control designed to be used in the home. ... the wi-fi connection is to be kept off as much as possible ... I'm seeing 30 seconds or more when DHCP is ... Even if you've reconnected before the lease expires, ...
    (microsoft.public.windowsce.app.development)
  • Re: DHCP too slow - trying to cache
    ... So, when you *don't* use DHCP, the connection is 20-30 seconds faster? ... > wi-fi television remote control designed to be used in the home. ... Even if you've reconnected before the lease expires, ...
    (microsoft.public.windowsce.app.development)
  • Re: dhcp-client cleanup
    ... Internet Systems Consortium DHCP Client V3.0.3 ... Copyright 2004-2005 Internet Systems Consortium. ... when the client gets it's first lease. ...
    (comp.os.linux.networking)
  • Re: DHCP too slow - trying to cache
    ... The dhcp spec does specify that a dhcp client should wait a random time ... > connection to the AP and another 7 or so to get the address. ... >> wi-fi television remote control designed to be used in the home. ... Even if you've reconnected before the lease expires, ...
    (microsoft.public.windowsce.app.development)
Loading