Re: dhclient cause up/down cycle after 239356 ?

From: Vitalij Satanivskij <satan_at_ukr.net>
Date: Wed, 22 Aug 2012 20:28:22 +0300
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 <satan_at_ukr.net> 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_at_freebsd.org mailing list
YP> http://lists.freebsd.org/mailman/listinfo/freebsd-current
YP> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
Received on Wed Aug 22 2012 - 15:28:34 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:29 UTC