Upgrading my WRT1900ACS from 21.02.7 to Snapshot (r22755) resulted in a non-functional guest network.
So I wiped the config and started from configuring scratch (about a 1-2 hour job).
This resulted in a working system.
One odd thing, I couldn't setup the guest network from the wireless config screen. It used to be I could enter a new network name (guest) in the custom field and then setup the guest network.
I tried Snapshot 22746 (and earlier versions), but I found issues with routing (or maybe firewall?) across different LANs. Connections could not be established, but I could not find anything wrong with the configuration so I reverted back to OpenWRT 22.
I think it was the firewall, as I could ping the targets but web pages would not load. Upgrading to the snapshot without config save and then setting up from scratch resulted in a working system. My configs probably date back to version 20, or even earlier, so it was time to start fresh anyway.
I confirm that I could ping the target, but web pages failed to load.
I will try again setting up the configuration from scratch, but given the complexity of my installation it is going to take a long time. I would be nice if the developers tried to maintain compatibility or a working migration of the configuration
Smells like an MTU issue. Could you please post MTUs of all links involved?
For me the MTU on all interfaces is 1500 except for eth0 which is 1508. I am running VLANs. I'm thinking that something about the VLAN configuration didn't migrate well from version 21 to 22 to Snapshot.
If software flow offloading is enabled in firewall, try unchecking that box. I can reliably break my setup by enabling that option with the snapshot.
Same, software flow offloading has been broken for quite some time. I enable packet steering and sqm that's about it.
1 Like
Thanks for the confirmation, I haven't seen any threads that mention it is broken, but perhaps that is because it worked in versions 21 and 22? I've had software flow offloading enabled for quite sometime, but it is clearly busted in the snapshot I loaded.
Last known issue on the mvebu 5.15 switch.
2 Likes
Awesome, thanks for that, hopefully I can figure out when a fix is included in a future snapshot.
The MTU is set to 1492 for all interfaces, but the WAN port (WAN connects to a modem, pppoe-wan sets MTU automatically to 1492 ).
Did you already try a new build? I just updated to r23104, and am now testing it. Let's see how it fares. Divested reverted to previous mwlwifi, as the new changes seemed to introduce some ping issues.
How did it go? Btw, 23.05 branch release candidate is getting close.
Working fine for now. Re-enabled AMSDU, otherwise same settings as previous build. Packet steering also enabled.
Edit: on WRT32X
Yea my last build hit 50-day uptime (since kernel 5.15.105) and was basically flawless during that time other than wifi. Just moved up to a new build this weekend (5.15.112). Going to test out the mwlwifi driver, many of my wireless devices are on a U6-Lite wifi 6 AP now which is connected to my WRT32X that handles everything else.
1 Like
So, it seems that we can update from 19.7? Which version do you guys recommend? But Wi-Fi still is sucky if you go beyond 19.7?
Yes, you can upgrade from 19.07. For some people, even 21.x worked fine. The various bugs didn't impact everyone. But at this point, you should just wait until 23.x comes out (which is soon).
1 Like
So, no weird Wi-Fi break ups and the likes anymore? Sounds good!
A few people have said so, but all you can do is test the latest 23.05 branch snapshot for yourself and see. Otherwise, just wait for the release candidates or the official release, when a lot more people will likely be chiming in.
1 Like