I recently installed OpenWRT 19.07.3 on my TP-Link Archer C60 v1, but ever since I did so, I started running into trouble with packages dropping like crazy – we’re talking in the 70-80% range of packet loss. When the packages do get through, it’s quite speedy though.
I can replicate this problem both on WiFi (both on 2.4 and 5 GHz) and cable. I can even replicate this problem pinging from the router itself.
If I use the same cable and port that goes from the modem into the router and connect it directly into a laptop, there is no packet loss, so I assume the problem is not in the cable or the modem either.
Any help would be greatly appreciated, as this is affecting me quite a bit.
System log: https://pastebin.com/5ZeG8Ua
Kernel log: https://pastebin.com/T35TgZXX
The following issues seem to me like they might be related, but then again, I’m not a network engineer by any stretch of imagination:
opened 08:20PM - 01 Apr 19 UTC
closed 05:01AM - 11 Oct 20 UTC
flyspray
*Spider-Vice:*
I've built the latest version of OpenWRT with stock packages and… configuration, however, after random amounts of time, all clients lose connectivity because the eth0 link speed drops from the regular 100 Mbps Full Duplex to 10 Mbps Half Duplex, only to reconnect again after a couple of minutes (seconds to mintes, it depends), and do it again at another random time.
<code>[18580.106696] eth0: link up (100Mbps/Full duplex)
[19014.825937] eth0: link up (10Mbps/Half duplex)
[19055.384105] eth0: link up (100Mbps/Full duplex)
[21927.853366] eth0: link up (10Mbps/Half duplex)
[22003.771999] eth0: link up (100Mbps/Full duplex)
[23743.685216] eth0: link down
[23744.723679] eth0: link up (100Mbps/Full duplex)
[23756.242265] eth0: link down
[23757.283590] eth0: link up (100Mbps/Full duplex)
[24075.522397] eth0: link up (10Mbps/Half duplex)
[24090.081802] eth0: link up (100Mbps/Full duplex)
[24100.481809] eth0: link up (10Mbps/Half duplex)
[24166.001178] eth0: link up (100Mbps/Full duplex)
[24500.880989] eth0: link up (10Mbps/Half duplex)</code>
The logs aren't very useful, it seems. Both syslog and dmesg show the same.
I suspect this started happening after this series of commits (ending with this one) where there were driver changes to the switch, as it didn't happen before I recompiled a new build with all those newer changes:
https://github.com/openwrt/openwrt/commit/3d93b35f039de86830565420968715b300066475
opened 04:28PM - 12 Jan 20 UTC
closed 05:30PM - 19 Dec 20 UTC
flyspray
*levin41:*
Probably related to https://bugs.openwrt.org/index.php?do=details&ta… sk_id=2216 which was reported almost a year ago. The bug is still not fixed though.
Are there any plans to fix it or will 18.06 be the last stable version for this and probably other devices?
[8451.981464] eth1: link up (100Mbps/Full duplex)
[37071.909045] eth1: link down
[37072.988861] eth1: link up (100Mbps/Full duplex)
[48492.291332] eth1: link up (10Mbps/Half duplex)
[48632.691559] eth1: link up (100Mbps/Full duplex)
[55697.449886] eth1: link down
[55698.491082] eth1: link up (100Mbps/Full duplex)
[62395.095374] eth1: link up (10Mbps/Half duplex)
[62507.411488] eth1: link up (100Mbps/Full duplex)
[62726.853998] eth1: link up (10Mbps/Half duplex)
[62732.053093] eth1: link up (100Mbps/Full duplex)
[71071.460663] eth1: link down
[71072.618285] eth1: link up (100Mbps/Full duplex)
[73435.556373] eth1: link down
[73436.597169] eth1: link up (100Mbps/Full duplex)
[73547.879987] eth1: link up (10Mbps/Half duplex)
[73558.277169] eth1: link up (100Mbps/Full duplex)
[74438.121970] eth1: link down
[74439.162824] eth1: link up (100Mbps/Full duplex)
[75341.889076] eth1: link up (10Mbps/Half duplex)
[75352.290230] eth1: link up (100Mbps/Full duplex)
[76274.772404] eth1: link down
[76275.813134] eth1: link up (100Mbps/Full duplex)
I installed the ath79 image and it does weird things. The WiFi or Internet connection is restarted or cut off.
In rc1 eth0 was very unstable but it is stable now in final 19.07.
There's now a problem with eth1 (WAN) though.
[ 8450.943196] eth1: link down
[ 8451.981464] eth1: link up (100Mbps/Full duplex)
[37071.909045] eth1: link down
[37072.988861] eth1: link up (100Mbps/Full duplex)
[48492.291332] eth1: link up (10Mbps/Half duplex)
[48632.691559] eth1: link up (100Mbps/Full duplex)
[55697.449886] eth1: link down
[55698.491082] eth1: link up (100Mbps/Full duplex)
Here's the report for the eth0 issue …
False alarm. It turned out the TP-Link was battling for the same IP as the telco’s modem/router (i.e. WAN from the OpenWrt PoV).
I’m closing this thread and will rename it accordingly.
Massive thanks go to the #openwrt IRC channel , especially PaulFertser there, for walking me through this issue.
As a side-note, it might be cool if LuCI would warn when issues like this show up.
1 Like
From what I can tell, this is what happened:
telco’s modem/router was (by default) set to have its IP as 192.168.1.1
OpenWrt router was (by default) set to have its IP as 192.168.1.1
telco’s modem/router issued the OpenWrt router the IP 192.168.1.2
As a result, it seems that when I connected to the OpenWrt router, it thought it’s IP is 192.168.1.1, but when the packet got from the OpenWrt router to the modem/router that box thought it’s IP was 192.168.1.1.
It sounds like your OpenWrt LAN and WAN are both improperly numbered 192.168.1 .0/24. Traffic won't pass since the router thinks it's the same network.
1 Like
Yes, that was the problem. I managed to fix it by simply changing the LAN on OpenWrt to 192.168.0.1/24. I apologise, that I forgot to mention that in my first reply.
2 Likes
system
Closed
August 1, 2020, 9:10am
7
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.