[Solved] WRT3200ACM: Unstable LAN connections

For Developers
#1

Environment:
Hardware: WRT3200ACM
Firmware: LEDE Reboot 17.01.4 r3560-79f57e422d
Packages: AdBlock + sqm-scripts (piece of cake)

Problem summary: after a while, I cannot connect the other internal machines in the same LAN.

At the first minutes when I reboot the router, I can see and connect all the other machines in my home, within the same LAN network. However, after some time, I cannot see them anymore. I am sure these machines are not sleeping. And I can see them in the "Associated Stations" section. But ping failed:
$ ping 192.168.1.211
PING 192.168.1.211 (192.168.1.211): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3

Did I make some wrong configurations? Any comment or suggestion is much appreciated!

#2

Just to confirm -- are you talking about wired or wireless machines?

#3

Thanks very much! I am talking about wireless network.

Some update:
a. SSH to Router, and I can always get the correct route:
traceroute to 192.168.1.211 (192.168.1.211), 30 hops max, 38 byte packets
1 first-pi.lan (192.168.1.211) 5.633 ms 2.293 ms 2.249 ms

b. From my computer, I might get the right route or:
$ traceroute 192.168.1.211
traceroute to 192.168.1.211 (192.168.1.211), 64 hops max, 52 byte packets
1 * * *
2 * * *
3 * * *
......

#4

AFAIK it's a known issue. Installing the newer mwlwifi driver from here: https://github.com/eduperez/mwlwifi_LEDE/releases might help.

#5

Suddenly I can access that device, but I still cannot access the others. Here is the route table from my local computer.

192.168.1 link#9 UCS 2 0 en0
192.168.1.1/32 link#9 UCS 1 0 en0
192.168.1.1 MAC_ADDRESS UHLWIir 36 2730 en0 1065
192.168.1.153 MAC_ADDRESS UHLWI 0 0 en0 195
192.168.1.172/32 link#9 UCS 0 0 en0
192.168.1.211 MAC_ADDRESS UHLWI 0 162 en0 1191

Do you know the bug tracker for the known issue? Much appreciate!

#6

There are several issues open here: https://github.com/kaloz/mwlwifi/issues.
But as @stangri mentioned, I would update the drivers first.

#7

Thanks!

I've updated to the latest driver 10.3.4.0-20171214-5955f5e. And I will come back with the new running result.

However, I am not sure if the later driver would fix the issue or not, because I switched to 2.4G wireless network and the issue persists.

#8

Thanks @stangri and @eduperez! After upgrading to 10.3.4.0-20171214-5955f5e driver, it works well now.

1 Like