Date: Wed, 27 Jul 2005 13:13:32 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: David Gilbert <dgilbert@dclg.ca> Cc: Mike Jakubik <mikej@rogers.com>, Doug Barton <dougb@freebsd.org>, Peter Wemm <peter@freebsd.org>, freebsd-current@freebsd.org Subject: Re: dhclient sucks Message-ID: <20050727201332.GA23927@odin.ac.hmc.edu> In-Reply-To: <17127.41923.312257.159166@canoe.dclg.ca> References: <42E583F9.3070703@rogers.com> <200507261853.07513.peter@wemm.org> <1242.172.16.0.199.1122429678.squirrel@172.16.0.1> <200507271215.14369.doconnor@gsoft.com.au> <42E6F5EA.7030801@samsco.org> <42E71F77.6010705@FreeBSD.org> <17127.41923.312257.159166@canoe.dclg.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment Content-Transfer-Encoding: quoted-printable On Wed, Jul 27, 2005 at 11:09:55AM -0400, David Gilbert wrote: > The ISC dhclient would probe multiple interfaces simultaneously. The > new one waits for some amount o ftime on my hardwire ethernet (rarely > used) before probing my wireless. The result is a longer startup. Try: background_dhclient=3D"YES" hmm, it might be worth allowing this to be a list of interfaces so rarely used interfaces could be listed and you'd still get the non-POLA violating synchronous startup on the others most of the time. > Since the changes to the wireless code, the ISC dhclient would notice > a change in the state of the wireless (new ssid, for instance) and > quickly sync up. The new dhclient sometimes does, but more often than > not requires that I "ifconfig ath0 ssid foo" ... which is annoying. > With the old ISC client, leaving the ssid blank was sufficient. This should not be the case and in fact, the new dhclient should be much faster because it is immediately notified of changes in association via the routing socket rather than waiting to poll for changes. > An extention of this is that randomly, after some long amount of time > online (often a day or two), ath0 seems to disassociate with the only > local access point in my home and reqire I ifconfig a bunch of times. > This may or may not be a dhclient thing --- but I tend to think it's > related ... if for no other reason than it started occuring at the > same time as the dhclient was checked in. This has nothing to do with dhclient since association has nothing to do with dhclient. I think it may been worked around with a commit earlier today. In my view, most problems with dhclient seem to be driver media handling issues. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFC5+rrXY6L6fI4GtQRAsgHAKCZgVq4J48l0PC812RWEsg77s9dPwCgvPOY +AtX02gNEDqwOhn6mr87S+I= =rDCu -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050727201332.GA23927>