Possible 22.03 issue on Linksys 3200ACM

All,

Wondering if someone has seen this issue.

For the last couple of months since upgrading to 22.03.x I have been getting drop outs constantly. It will last for about 5 to 10 seconds on average, but some times could be up to about 30 seconds.

I have collectd running with a ping capture and it is very noticble, and working from home my VDI just freezes up until it comes back. I even see the same thing with my thinkbroadband BQM going.

I thought it was SQM, but I disabled that and it has almost made it worse to be honest. The drop outs last longer when SQM is disabled as opposed to having it enabled.

Is there an issue with 22.03 that I am unaware of for this router?

I am thinking of reverting back to 21.02.5 as that seemed to be the most stable for me as the timing of me moving to 22.03 seems to tally up with the issues I am having

Thanks

Yes, the switch has a driver fault and it is actually a hub.
No hope of fix.

Move to master with kernel 5.15 or branch 21.02.

1 Like

Can you please explain what you mean that it is actually a hub? Does the driver turn the switch ports to act like a hub?

ya mon

1 Like

I read that the snapshot has 5.15 kernel and that is the version I am running, which apparently fixes that issue you mention

Not what you stated in the OP, but yes resolved with 5.15 kernel.

1 Like

Apologies for that, only read now about the issue, but had not thought to mention if that would be a possible cause. Either way I have the snapshot but seeing these weird timeouts. Just thought if anyone has seen this type of issue before.

I contacted my service provider in the meantime to see if this could be on their network. So they are going to look into it.

Just odd that these issue started round the same time I had upgraded to 22.03.x. I update to the snapshot last week Friday thinking that may help, but it did not.

Running master here on a rango and have not noticed anything untoward (flowoffload be borked though).

A few of us running on 5.15 via the Divested build are seeing client isolation (peer to peer reachability) issues on wifi (without isolation enabled) between all wifi clients and wired clients on same vlan/network. Occasionally the first ping out of the 3/4 ping sequence goes through, the rest fail... and then all continually fail for some random but longtime, when the same thing repeats.

I am seeing ping timeouts to the internet occur every hour without fail .... Also had an issue this morning, could not connect to the router at all. Rebooted it, and checked the collectd graphs and most things were still working including the ping checks I had in place. Really does not seem very stable at all.

How easy is it reverting to an older version ? would I get the sysupgrade firmware or the factory one ?
I also assume I would have to reset all settings and configure the whole thing all over again (real pain).

Are you running master snapshot with kernel 5.15 or branch 22.03 with kernel 5.10?
You will never find kernel 5.15 in branch 22.03 if you run a real supported OpenWrt image.

This is what I have:
Firmware Version - OpenWrt SNAPSHOT r21843-539b52068a / LuCI Master git-23.013.73089-9634086
Kernel Version - 5.15.88

at about 46/47 minutes passed the hour every hour all internet traffic stalls.

I have rebooted the router and the time does not change with the reboot.

During these drop out I see this in the logs:

Tue Jan 31 18:45:49 2023 daemon.notice netifd: Network device 'wan' link is down
Tue Jan 31 18:45:49 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Jan 31 18:45:49 2023 kern.info kernel: [840036.088610] mv88e6085 f1072004.mdio-mii:00 wan: Link is Down
Tue Jan 31 18:45:55 2023 daemon.notice netifd: Network device 'wan' link is up
Tue Jan 31 18:45:55 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Jan 31 18:45:55 2023 kern.info kernel: [840042.396416] mv88e6085 f1072004.mdio-mii:00 wan: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Jan 31 18:46:29 2023 daemon.notice netifd: Network device 'wan' link is down
Tue Jan 31 18:46:29 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Jan 31 18:46:29 2023 kern.info kernel: [840075.489723] mv88e6085 f1072004.mdio-mii:00 wan: Link is Down
Tue Jan 31 18:46:43 2023 daemon.notice netifd: Network device 'wan' link is up
Tue Jan 31 18:46:43 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Jan 31 18:46:43 2023 kern.info kernel: [840089.774266] mv88e6085 f1072004.mdio-mii:00 wan: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Jan 31 18:46:43 2023 user.info : luci: accepted login on /admin/statistics/graphs for root from 192.168.0.196
Tue Jan 31 18:46:57 2023 daemon.notice netifd: Network device 'wan' link is down
Tue Jan 31 18:46:57 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Jan 31 18:46:57 2023 kern.info kernel: [840104.121526] mv88e6085 f1072004.mdio-mii:00 wan: Link is Down
Tue Jan 31 18:47:01 2023 daemon.notice netifd: Network device 'wan' link is up
Tue Jan 31 18:47:01 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Jan 31 18:47:01 2023 kern.info kernel: [840107.638171] mv88e6085 f1072004.mdio-mii:00 wan: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Jan 31 18:47:04 2023 daemon.notice netifd: Network device 'wan' link is down
Tue Jan 31 18:47:04 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Jan 31 18:47:04 2023 kern.info kernel: [840110.833595] mv88e6085 f1072004.mdio-mii:00 wan: Link is Down
Tue Jan 31 18:47:11 2023 daemon.notice netifd: Network device 'wan' link is up
Tue Jan 31 18:47:11 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Jan 31 18:47:11 2023 kern.info kernel: [840117.763722] mv88e6085 f1072004.mdio-mii:00 wan: Link is Up - 1Gbps/Full - flow control rx/tx
Tue Jan 31 18:47:23 2023 daemon.notice netifd: Network device 'wan' link is down
Tue Jan 31 18:47:23 2023 daemon.notice netifd: Interface 'wan' has link connectivity loss
Tue Jan 31 18:47:23 2023 kern.info kernel: [840129.867889] mv88e6085 f1072004.mdio-mii:00 wan: Link is Down
Tue Jan 31 18:47:31 2023 daemon.notice netifd: Network device 'wan' link is up
Tue Jan 31 18:47:31 2023 daemon.notice netifd: Interface 'wan' has link connectivity
Tue Jan 31 18:47:31 2023 kern.info kernel: [840137.680292] mv88e6085 f1072004.mdio-mii:00 wan: Link is Up - 1Gbps/Full - flow control rx/tx

Does this look like something familiar ? Could this be driver related or would this be the VM Hub in Modem mode (which I just got replaced today and it is doing the same thing)

I reverted the router to 21.02.5 also about 2 weeks ago, and the issue is still persisting.

EEE issue? use ethtool to change,

I'm facing the exact same problem on my wrt3200acm. Currently on Divested build, kernel 5.15.103.
Did you ever found a solution to it?

So the problem actually ended up being an issue with the Virgin Media Hub. I think some update came out a few months back that completely messed it up. When putting the Hub in normal mode was getting drops as seen in the BQM. After months of complaining and posting on the forum, 3 engineers, replacement Hub and Virgin technical support saying there was nothing wrong, it magically started working about 2 weeks ago.

I did numerous snapshot updates on the Linksys and none of that seemed fix the issue, and hence whittled it down to being the Hub.

Not sure if that helps you, but I would keep up with the snapshot updates even though they are a pain to do.