#19085: nanostation m5 loco xw "loses" interface
------------------------+------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: reopened
Priority: normal | Milestone:
Component: kernel | Version: Trunk
Resolution: | Keywords:
------------------------+------------------------
Comment (by bmoffitt):
Folks-
I flashed the latest nightly from the trunk (r47896) to test on a pair of
Ubiquiti LOCO M5 XW radios. They have been running for a couple of hours
now; the client side has been flawless, but I see some very odd behavior
in the dmesg for the Access Point side:
[ 52.885082] random: nonblocking pool is initialized
[ 2086.730654] eth0: link down
[ 2086.733554] br-lan: port 1(eth0) entered disabled state
[ 2087.731803] eth0: link up (100Mbps/Full duplex)
[ 2087.736466] br-lan: port 1(eth0) entered forwarding state
[ 2087.742041] br-lan: port 1(eth0) entered forwarding state
[ 2089.740331] br-lan: port 1(eth0) entered forwarding state
[ 2913.722358] eth0: link down
[ 2913.725310] br-lan: port 1(eth0) entered disabled state
[ 2914.723475] eth0: link up (100Mbps/Full duplex)
[ 2914.728137] br-lan: port 1(eth0) entered forwarding state
[ 2914.733696] br-lan: port 1(eth0) entered forwarding state
[ 2916.731995] br-lan: port 1(eth0) entered forwarding state
[ 3792.713089] eth0: link down
[ 3792.715993] br-lan: port 1(eth0) entered disabled state
[ 3793.714170] eth0: link up (100Mbps/Full duplex)
[ 3793.718832] br-lan: port 1(eth0) entered forwarding state
[ 3793.724408] br-lan: port 1(eth0) entered forwarding state
[ 3795.722687] br-lan: port 1(eth0) entered forwarding state
[ 4905.700388] eth0: link down
[ 4905.703287] br-lan: port 1(eth0) entered disabled state
[ 4906.701538] eth0: link up (100Mbps/Full duplex)
[ 4906.706198] br-lan: port 1(eth0) entered forwarding state
[ 4906.711773] br-lan: port 1(eth0) entered forwarding state
[ 4908.710040] br-lan: port 1(eth0) entered forwarding state
[ 7286.674923] eth0: link up (10Mbps/Half duplex)
[ 7288.674905] eth0: link up (100Mbps/Full duplex)
[ 8076.665133] eth0: link down
[ 8076.668051] br-lan: port 1(eth0) entered disabled state
[ 8077.666274] eth0: link up (100Mbps/Full duplex)
[ 8077.670957] br-lan: port 1(eth0) entered forwarding state
[ 8077.676515] br-lan: port 1(eth0) entered forwarding state
[ 8079.674785] br-lan: port 1(eth0) entered forwarding state
As you can see, every so often the Ethernet port just goes down for almost
exactly one second.
The configuration of that radio is just a standard Access Point config,
with WPA2 PSK authentication/encryption. It is plugged into a switch on a
"2Wire" brand router (so I cannot be absolutely sure the router is not at
fault).
Question to psyke83 - you noted that "my patch won't help except for loco
m5" but tillw noted "we compiled and flashed latest trunk today to a
Nanostation Loco XW. The bug described in this ticket occured after about
1 hour." As far as I know the m5 is the only loco that has the xw
architecture currently. Am I missing something here?
-Bill
--
Ticket URL: <https://dev.openwrt.org/ticket/19085#comment:55>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
