Date: Thu, 5 Apr 2012 13:22:37 -0700 From: YongHyeon PYUN <pyunyh@gmail.com> To: Peter Jeremy <peterjeremy@acm.org> Cc: freebsd-net@freebsd.org Subject: Re: dhclient behaviour on link status changes Message-ID: <20120405202237.GC14289@michelle.cdnetworks.com> In-Reply-To: <20120405023946.GA63311@server.vk2pj.dyndns.org> References: <20120404211749.GA16579@server.vk2pj.dyndns.org> <20120405023946.GA63311@server.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > 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 > -- > Peter Jeremy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120405202237.GC14289>