On the turris omnia WAN is (by default) on a physically different interface not part of the switch, so no no leakage to the WAN interface, no idea about the other mvebu platforms though.
Accoding to:
https://www.mail-archive.com/search?l=openwrt-devel@lists.openwrt.org&q=subject:"Re\%3A+Re\%3A+\[PATCH+22.03\]+mvebu\%3A+cortexa9\%3A+disable+devices+using+broken+mv88e6176+switch"&o=newest
the fixes might already be identified:
https://bugzilla.kernel.org/show_bug.cgi?id=209487
Seems like this belongs in the "known issues" in the release notes page (https://openwrt.org/releases/22.03/notes-22.03.3#known_issues)
Seems like this belongs in the "known issues" in the release notes
Once the fix is committed, the bind packages should reappear in a few days.
Not worthwhile to put into permanent "known issues".
(Build errors surface every now and then. And this is not directly related to 22.03.3)
EDIT:
I pushed the proposed fix to both master and 22.03.
Buildbot will churn new "bind" packages in 1-3 days (for all target architectures).
it would be unfortunate if wrt-mvebu series supprt were dropped by openwrt. this fix was first reported for linux almost a year ago. i hope that openwrt will catch up....
I doubt they drop it. But from what I read this is a serious problem in the current version. An advice on what to do for the owners of affected devices would be highly appreciated.
Also, it seems this is not a generall issue and only occuring in some configurations. So a how-to to describe how to find out if a device is affected would be helpfull.
I will try to set up a AVM Fritzbox 4040 this evening as a spare device to replace my WRT3200ACM if neccessary.
Disappointing not to see all the MT76 bugfixes from November and December in this release.
Congrats on the release. Using master snapshots with kernel 5.15 on my WRT32X for obvious reasons, running fast and stable and switch is fixed from my testing. @ne20002 use a master snapshot since it's fixed on kernel 5.15, 3 week uptime on mine.
OpenWrt has always been stable on my WRT3200ACM.
I'm confused. What does this mean for the WRT3200? That the latest update cannot be applied?
@waynea i would assume that the bugfix from 5.15 would be backported and then a new 22.03 release would be created.
I've noticed with 22.03.3 that ingress latency has greatly increased with SQM. Can others please check as well?
Regarding the mvebu
switch issue for clarity:
-
If a user only used wireless connections with nothing plugged into LAN ports, would the issue cause any negative affects?
-
If a user used mostly wireless connections, but has only 1 device plugged into a LAN port, would there be any negative affects in this scenario?
-
Or would there only be negative affects for users who have multiple devices plugged into LAN ports?
-
Is there any negative affect on WAN port?
This issue is clearly above my level of understanding and I think that some clarification would benefit the users who are affected by this. Thank you.
Will Linksys WRT3200ACM be ever supported again by OpenWRT or is it death sentence?
Issue is already addressed by 5.15, so no, not the death knell.
So it looks pretty much that the mvebu "lock-out" will only be transient, as kernel 5.15 does not appear to have that issue. So either wait for 5.15 to hit stable, or:
a) switch to main snapshots of openwrt, which IIRC already use 5.15 kernels
b) help testing and back-porting the patches required to make mvebu work as expected under 5.10 kernels.
Thanks a lot for the hope good man!
I take that to mean ping times during downloads? If so, I think they do jump higher than before, but I'm not absolutely sure. Starting at about 28, they get up into the upper 70s for a while, where I think before it would have been 50 at the highest. Uploads stay low.
yup - just moved to snapshot 5.15, working. i'm sure my backporting skill is minimal but i'd be happy to test for others. thanks.
No
No (edit: well, probably not)
Yes
No
tl;dr either use 22.03.2 where the switch is acting as a hub, not good but won't kill your network. Or move up to master snapshot where it's fixed, kernel 5.15 is rock solid been running it on my WRT32X for weeks.
Where is that "master snapshot" that one might install it? Please advise.