Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Aug 2012 08:27:01 +1000
From:      Peter Jeremy <peter@rulingia.com>
To:        Vitalij Satanivskij <satan@ukr.net>
Cc:        current@freebsd.org
Subject:   Re: dhclient cause up/down cycle after 239356 ?
Message-ID:  <20120821222701.GA94197@server.rulingia.com>
In-Reply-To: <20120821164217.GA45780@hell.ukr.net>
References:  <20120821095527.GA33206@hell.ukr.net> <CAGH67wSsMTSHHHi=Qzu6kJ%2BMtFKH9s5zPTdFYSj0WD1duwWuzA@mail.gmail.com> <20120821164217.GA45780@hell.ukr.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--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 <satan@ukr.net> 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--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120821222701.GA94197>