Date: Thu, 5 Apr 2012 14:44:59 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: YongHyeon PYUN <pyunyh@gmail.com> Cc: freebsd-net@freebsd.org Subject: Re: dhclient behaviour on link status changes Message-ID: <20120405044459.GB63311@server.vk2pj.dyndns.org> In-Reply-To: <20120405202237.GC14289@michelle.cdnetworks.com> References: <20120404211749.GA16579@server.vk2pj.dyndns.org> <20120405023946.GA63311@server.vk2pj.dyndns.org> <20120405202237.GC14289@michelle.cdnetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--lEGEL1/lMxI0MVQ2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Apr-05 13:22:37 -0700, YongHyeon PYUN <pyunyh@gmail.com> wrote: >On Thu, Apr 05, 2012 at 12:39:46PM +1000, Peter Jeremy wrote: >> On 2012-Apr-05 07:17:49 +1000, Peter Jeremy <peterjeremy@acm.org> wrote: >> >/etc/devd.conf includes a rule to start dhclient when an Ethernet or >> >802.11 interface reports "link up", with a comment: "No link down rule >> >exists because dhclient automatically exits when the link goes down." >> >IMHO, this is the desired behaviour, unfortunately it's not the way >> >dhclient actually behaves. In my experience, dhclient will exit when >> >the interface goes down but ignores link status changes. >>=20 >> I found an easy way to correct the behaviour & submitted bin/166656 >Hmm, wouldn't this make dhclient die when speed/duplex/flow control >of established connection is changed by admin or remote link partner? >For instance, >#ifconfig foo0 media mdiaopt flow If the speed/duplex/flow control change triggered a "LINK DOWN" "LINK UP" kernel message then, yes, that would cause dhclient to restart. I think that depends on the NIC. I guess a potential work-around would be to have dhclient ignore outages shorter than a configurable value. I hadn't considered that because it's not something that I ever do on a running system. (This investigation was prompted by my ISP's approach to address grooming - they just remotely reboot the cablemodem and expect clients to re-DHCP. Existing valid leases are just ignored. Since the FreeBSD dhclient ignores the link outage, I just lose Internet connectivity until I manually restart DHCP). --=20 Peter Jeremy --lEGEL1/lMxI0MVQ2 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAk99I0sACgkQ/opHv/APuIcGjwCeJqaxwJVIUe3od7C5NdFNjznC 46YAn3m27R/2mf5uxinJv09CQChyUWvq =TCQI -----END PGP SIGNATURE----- --lEGEL1/lMxI0MVQ2--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120405044459.GB63311>