#19085: nanostation m5 loco xw "loses" interface
------------------------+------------------------
Reporter: anonymous | Owner: developers
Type: defect | Status: new
Priority: normal | Milestone:
Component: kernel | Version: Trunk
Resolution: | Keywords:
------------------------+------------------------
Comment (by leoso):
Replying to [comment:26 bmoffitt@…]:
> I have been testing some LOCO M5 XW units, and both under r42711 (kernel
3.10.49) and a more recent build using 3.18.14 I saw the Access Points
losing contact with the router into which they were plugged. I put in a
script to ping the router every 5 minutes, and the ping failed with
disturbing frequency.
>
> in 3.10.49, however, the same thing was happening at the client end -
the LOCO would lose touch with the device attached to it and require a
reboot. However, in 3.18.14, I did not observe that particular problem. So
it appears something changed, although I'm not sure what.
Can you explain your installation in detail? Where is your client
connected? On loco eth0 interface?
I am asking because if eth0 is down, there is only wifi interface working
on loco. So if your client is connected with loco eth0 and your router
also, both devices should not be able to connect to loco via cable.
--
Ticket URL: <https://dev.openwrt.org/ticket/19085#comment:27>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
