From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 17:28:34 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A549F1065670 for ; Wed, 22 Aug 2012 17:28:34 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) by mx1.freebsd.org (Postfix) with ESMTP id 3D24B8FC08 for ; Wed, 22 Aug 2012 17:28:33 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1T4Ej8-000DrS-QF ; Wed, 22 Aug 2012 20:28:22 +0300 Date: Wed, 22 Aug 2012 20:28:22 +0300 From: Vitalij Satanivskij To: YongHyeon PYUN Message-ID: <20120822172822.GA52909@hell.ukr.net> References: <20120821095527.GA33206@hell.ukr.net> <20120821164217.GA45780@hell.ukr.net> <20120821222701.GA94197@server.rulingia.com> <20120822171253.GB3300@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120822171253.GB3300@michelle.cdnetworks.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Vitalij Satanivskij , Peter Jeremy , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2012 17:28:34 -0000 ok next round :) dhclient updated to Revision 239564 with fxp : Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:06:48 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:06:48 home dhclient: New Routers (fxp0): xx.xx.xx.1 Aug 22 20:06:50 home kernel: fxp0: link state changed to UP Aug 22 20:06:53 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:06:53 home kernel: fxp0: link state changed to DOWN Aug 22 20:06:53 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:06:53 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:06:53 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:06:55 home kernel: fxp0: link state changed to UP Aug 22 20:07:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:07:01 home kernel: fxp0: link state changed to DOWN Aug 22 20:07:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:07:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:07:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:07:03 home kernel: fxp0: link state changed to UP Aug 22 20:07:07 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:07:07 home kernel: fxp0: link state changed to DOWN Aug 22 20:07:07 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:07:07 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:07:07 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:07:09 home kernel: fxp0: link state changed to UP Aug 22 20:07:13 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:07:13 home kernel: fxp0: link state changed to DOWN Aug 22 20:07:13 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:07:13 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:07:13 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:07:15 home kernel: fxp0: link state changed to UP ifconfig show that iface doesn't loose ip adress but, link realy loosed (for example 10 from icmp pachets cannot reach destination) Yes, my problem easy fixed by changed ethernet card to em, but there are meny motherboard with integrated ether's... YongHyeon PYUN wrote: YP> On Wed, Aug 22, 2012 at 08:27:01AM +1000, Peter Jeremy wrote: YP> > On 2012-Aug-21 19:42:17 +0300, Vitalij Satanivskij wrote: YP> > >Look's like dhclient do down/up sequence - YP> > YP> > Not intentionally. YP> > YP> > >Aug 21 19:21:00 home kernel: fxp0: link state changed to UP YP> > >Aug 21 19:21:01 home kernel: fxp0: link state changed to DOWN YP> > >Aug 21 19:21:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx YP> > >Aug 21 19:21:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 YP> > >Aug 21 19:21:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.xx YP> > >Aug 21 19:21:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx YP> > >Aug 21 19:21:03 home kernel: fxp0: link state changed to UP YP> > YP> > I can reproduce this behaviour - but only on fxp (i82559 in my case) YP> > NICs. My bge (BCM5750) and rl (RTL8139) NICs do not report the YP> > spurious DOWN/UP. (I don't normally run DHCP on any fxp interfaces, YP> > so I didn't see it during my testing). YP> > YP> > The problem appears to be the YP> > $IFCONFIG $interface inet alias 0.0.0.0 netmask 255.0.0.0 broadcast 255.255.255.255 up YP> > executed by /sbin/dhclient-script during PREINIT. This is making the YP> > fxp NIC reset the link (actually, assigning _any_ IP address to an fxp YP> > NIC causes it to reset the link). The post r239356 dhclient detects YP> YP> This comes from the hardware limitation. Assigning addresses will YP> result in programming multicast filter and fxp(4) controllers YP> require full controller reset to reprogram the multicast filter. YP> YP> > the link going down and exits. YP> > YP> > >Before r239356 iface just doing down/up without dhclient exit and YP> > >everything work fine. YP> > YP> > For you, anyway. Failing to detect link down causes problems for me YP> > because my dhclient was not seeing my cable-modem resets and therefore YP> > failing to reacquire a DHCP lease. YP> > YP> > -- YP> > Peter Jeremy YP> YP> YP> _______________________________________________ YP> freebsd-current@freebsd.org mailing list YP> http://lists.freebsd.org/mailman/listinfo/freebsd-current YP> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"