thr3ads.net - freebsd stable - fxp0 interface going up/down/up/down (dhclient related?) [Jun 2013]

If this information is useful, please help other people find it:
Share via:

Alban Hertroys

2013-Jun-09 10:21 UTC

fxp0 interface going up/down/up/down (dhclient related?)

I'm having an issue where my fxp0 interface keeps looping between DOWN/UP,
with dhclient requesting a lease each time in between. I think it's caused
by dhclient:

solfertje # dhclient -d fxp0
DHCPREQUEST on fxp0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPREQUEST on fxp0 to 255.255.255.255 port 67
DHCPACK from 109.72.40.1
bound to 141.105.10.89 -- renewal in 7200 seconds.
fxp0 link state up -> down
fxp0 link state down -> up
DHCPREQUEST on fxp0 to 255.255.255.255 port 67
DHCPACK from 109.72.40.1
bound to 141.105.10.89 -- renewal in 7200 seconds.
fxp0 link state up -> down
fxp0 link state down -> up
DHCPREQUEST on fxp0 to 255.255.255.255 port 67
DHCPACK from 109.72.40.1
bound to 141.105.10.89 -- renewal in 7200 seconds.
fxp0 link state up -> down
fxp0 link state down -> up
DHCPREQUEST on fxp0 to 255.255.255.255 port 67
DHCPACK from 109.72.40.1
bound to 141.105.10.89 -- renewal in 7200 seconds.
fxp0 link state up -> down
fxp0 link state down -> up
DHCPREQUEST on fxp0 to 255.255.255.255 port 67
DHCPACK from 109.72.40.1
bound to 141.105.10.89 -- renewal in 7200 seconds.
fxp0 link state up -> down
^C

In above test I turned off devd (/etc/rc.d/devd stop) and background dhclient
(/etc/rc.d/dhclient stop fxp0), and I still go the above result. There's
practically no time spent between up/down cycles, this just keeps going on and
on.
fxp0 is the only interface that runs on DHCP. The others have static IP's.

Initially I thought the issue might be caused by devd, because I have both
ethernet and 822.11 type NICs (2x ethernet, 1x wifi) in that system.

This is 9-STABLE from yesterday.

Before, I had 9-RELEASE running on this system with the same config, and that
worked well.

I'm not sure it's related, but on the wireless interface I get  alot of:
Jun  9 12:08:11 solfertje kernel: ath0: stuck beacon; resetting (bmiss count 4)

ifconfig reads:
solfertje # ifconfig 
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
        ether 68:05:ca:17:fe:f7
        inet 10.236.150.1 netmask 0xffffff00 broadcast 10.236.150.255
        inet6 fe80::6a05:caff:fe17:fef7%em0 prefixlen 64 scopeid 0x2 
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
        media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
        ether 6c:fd:b9:68:db:36
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
        status: running
fxp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
       
options=4219b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,WOL_MAGIC,VLAN_HWTSO>
        ether 00:0e:0c:b2:04:b0
        inet6 fe80::20e:cff:feb2:4b0%fxp0 prefixlen 64 scopeid 0x9 
        inet 141.105.10.89 netmask 0xffffff80 broadcast 141.105.10.127
        nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
        media: Ethernet autoselect (100baseTX <full-duplex>)
        status: active
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128 
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0xd 
        inet 127.0.0.1 netmask 0xff000000 
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
1500
        ether 6c:fd:b9:68:db:36
        inet 10.236.151.1 netmask 0xffffff00 broadcast 10.236.151.255
        inet6 fe80::6efd:b9ff:fe68:db36%wlan0 prefixlen 64 scopeid 0xe 
        nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
        media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
        status: running
        ssid solfertje channel 11 (2462 MHz 11g) bssid 6c:fd:b9:68:db:36
        regdomain 32924 country CN indoor ecm authmode WPA privacy MIXED
        deftxkey 3 TKIP 2:128-bit TKIP 3:128-bit txpower 20 scanvalid 60
        protmode CTS wme burst dtimperiod 1 -dfs
pflog0: flags=141<UP,RUNNING,PROMISC> metric 0 mtu 33152
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>

And the hardware is as follows:
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: pciconf.txt
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20130609/e3dbebf9/attachment.txt>
-------------- next part --------------

Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.

Jeremy Chadwick

2013-Jun-09 10:44 UTC

head link

fxp0 interface going up/down/up/down (dhclient related?)

On Sun, Jun 09, 2013 at 12:21:37PM +0200, Alban Hertroys
wrote:> I'm having an issue where my fxp0 interface keeps looping between
DOWN/UP, with dhclient requesting a lease each time in between. I think it's
caused by dhclient:
> 
> solfertje # dhclient -d fxp0
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> send_packet: Network is down
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> ^C
> 
> In above test I turned off devd (/etc/rc.d/devd stop) and background
dhclient (/etc/rc.d/dhclient stop fxp0), and I still go the above result.
There's practically no time spent between up/down cycles, this just keeps
going on and on.
> fxp0 is the only interface that runs on DHCP. The others have static
IP's.
> 
> Initially I thought the issue might be caused by devd, because I have both
ethernet and 822.11 type NICs (2x ethernet, 1x wifi) in that system.
> 
> This is 9-STABLE from yesterday.
> 
> Before, I had 9-RELEASE running on this system with the same config, and
that worked well.
And so what I predicted begins...

The issue is described in the 8.4-RELEASE Errata Notes; the driver is
using the same driver version as in stable/9, hence you're experiencing
the same problem.  See Open Issues:

http://www.freebsd.org/releases/8.4R/errata.html

No fix for this has been committed.  It is still under discussions by
multiple kernel folks as to where the fix should be applied (dhclient or
the fxp(4) driver), because the changes made to dhclient (that tickle
this bug) may actually affect more drivers than just fxp(4).

You can start by reading the (extremely long but very informative)
thread here.  I do urge you to read all the posts, not skim them:

http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073440.html
http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/thread.html#73440

The only known workarounds at this time are:

a) Cease use of DHCP; set a static IP in rc.conf,

b) Try some of the patches mentioned within the above thread,
specifically this one:

http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073581.html

The patch is for head (CURRENT) so it may not patch cleanly.  If not,
you can try to work the patch in yourself/by hand, or you can ask
Yong-Hyeon or others for help.
> I'm not sure it's related, but on the wireless interface I get 
alot of:
> Jun  9 12:08:11 solfertje kernel: ath0: stuck beacon; resetting (bmiss
count 4)
Absolutely 100% unrelated.  That issue has been around for years, and
the root cause varies tremendously.  I discussed it back in February
2011:

http://lists.freebsd.org/pipermail/freebsd-stable/2011-February/061700.html

If you want to know how I solved that problem, I can tell you, but I'm
certain you won't be happy to hear what I have to say.

If you're concerned about this problem, please start another thread
discussing it.  I'm sure Adrian Chadd can provide you lots of insights,
but most of them are already in his response to my above thread/post.
> {snipping other stuff}
-- 
| Jeremy Chadwick                                   jdc at koitsu.org |
| UNIX Systems Administrator                http://jdc.koitsu.org/ |
| Making life hard for others since 1977.             PGP 4BD6C0CB |

YongHyeon PYUN

2013-Jun-09 11:45 UTC

head link

fxp0 interface going up/down/up/down (dhclient related?)

On Sun, Jun 09, 2013 at 12:21:37PM +0200, Alban Hertroys
wrote:> I'm having an issue where my fxp0 interface keeps looping between
DOWN/UP, with dhclient requesting a lease each time in between. I think it's
caused by dhclient:
> 
> solfertje # dhclient -d fxp0
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> send_packet: Network is down
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> fxp0 link state down -> up
> DHCPREQUEST on fxp0 to 255.255.255.255 port 67
> DHCPACK from 109.72.40.1
> bound to 141.105.10.89 -- renewal in 7200 seconds.
> fxp0 link state up -> down
> ^C
> 
> In above test I turned off devd (/etc/rc.d/devd stop) and background
dhclient (/etc/rc.d/dhclient stop fxp0), and I still go the above result.
There's practically no time spent between up/down cycles, this just keeps
going on and on.
> fxp0 is the only interface that runs on DHCP. The others have static
IP's.
> 
Try attached patch and let me know whether it also works for you.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fxp.init.diff
Type: text/x-diff
Size: 2785 bytes
Desc: not available
URL:
<http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20130609/70f3d5e4/attachment.diff>

freebsd stable - Jun 2013 - fxp0 interface going up/down/up/down (dhclient related?)

fxp0 interface going up/down/up/down (dhclient related?)

fxp0 interface going up/down/up/down (dhclient related?)

fxp0 interface going up/down/up/down (dhclient related?)