From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 22:27:15 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4790106566C for ; Tue, 21 Aug 2012 22:27:15 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD008FC12 for ; Tue, 21 Aug 2012 22:27:14 +0000 (UTC) Received: from server.rulingia.com (c220-239-249-137.belrs5.nsw.optusnet.com.au [220.239.249.137]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7LMR7Re085177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Aug 2012 08:27:08 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q7LMR2Q5094860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Aug 2012 08:27:02 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q7LMR1mj094859; Wed, 22 Aug 2012 08:27:01 +1000 (EST) (envelope-from peter) Date: Wed, 22 Aug 2012 08:27:01 +1000 From: Peter Jeremy To: Vitalij Satanivskij Message-ID: <20120821222701.GA94197@server.rulingia.com> References: <20120821095527.GA33206@hell.ukr.net> <20120821164217.GA45780@hell.ukr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20120821164217.GA45780@hell.ukr.net> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: 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: Tue, 21 Aug 2012 22:27:16 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-21 19:42:17 +0300, Vitalij Satanivskij wrote: >Look's like dhclient do down/up sequence - Not intentionally. >Aug 21 19:21:00 home kernel: fxp0: link state changed to UP >Aug 21 19:21:01 home kernel: fxp0: link state changed to DOWN >Aug 21 19:21:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >Aug 21 19:21:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >Aug 21 19:21:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.xx >Aug 21 19:21:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx >Aug 21 19:21:03 home kernel: fxp0: link state changed to UP I can reproduce this behaviour - but only on fxp (i82559 in my case) NICs. My bge (BCM5750) and rl (RTL8139) NICs do not report the spurious DOWN/UP. (I don't normally run DHCP on any fxp interfaces, so I didn't see it during my testing). The problem appears to be the=20 $IFCONFIG $interface inet alias 0.0.0.0 netmask 255.0.0.0 broadcast 255.2= 55.255.255 up executed by /sbin/dhclient-script during PREINIT. This is making the fxp NIC reset the link (actually, assigning _any_ IP address to an fxp NIC causes it to reset the link). The post r239356 dhclient detects the link going down and exits. >Before r239356 iface just doing down/up without dhclient exit and >everything work fine. For you, anyway. Failing to detect link down causes problems for me because my dhclient was not seeing my cable-modem resets and therefore failing to reacquire a DHCP lease. --=20 Peter Jeremy --17pEHd4RhPHOinZp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA0CzUACgkQ/opHv/APuIfPiwCgsdSK2xDSpxG3e2WV3OqzDwcl 3+0AoLO+E0TNyH24OjfUz2Pm2hmZIIh1 =4TdU -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp--