OpenWrt 21.02.0 - First Stable Release

I was reading some other post about WRT32X with too small partition but I did not see the WRT1900ACv1 one. That makes sense. Thank you so much for your help.

Congrats on this big release. Sticking with occational master snapshot updates on my WRT32X for now since it's stable and wifi is good with it. Great job to the devs thank you.

1 Like

Yeah, strangely in addition to the oldest device in the series (WRT1900ACv1) Linksys again caused the same problem to the newest device (WRT32x), although they had already used a larger kernel space for all the devices released in between, including the WRT3200ACM, the older twin sister of WRT32x.

1 Like

I wouldn't keep the settings, for sure. It is serial recovery if you forget.

1 Like

I usually keep the old setting when upgrading but in this case I guess it won't hurt setting up my routers as new again. I have some old backups so I just need to loop through them if needed.

2 Likes

Yes, that fixes the problem.
v1.5.0-2

v1.5.1-1

It can't even boost to full bandwith. Btw im ussing your script, that could be the problem too.

2 Likes

nice... I will check my end...

Just like RC4, this version has issues with Linksys WRT1900ACS v2. Clients loose connection to internet while connected to wifi. Can be fixed (temporarily) if you disconnect and reconnect wifi.

roughly how long does it take, before the clients loose Wifi again?

1 Like

Varies, but minutes. Doesn't seem like a lease renewal issue.

in LuCi advanced wifi settings of each radio there are 2 options:
Disable Inactivity Polling, default off
Disassociate On Low Acknowledgement, default on

Maybe try inverting these separately for a quick test, to see if it makes any difference.

You could also try current master image as well for a comparison - at least Wrt32x and Wrt3200 had ongoing issues and users claim the master works a lot better.

1 Like

Congrats to everyone involved in the development of this new stable version. It makes the already best even better.

For a 88W8864 device check post as to resolution.

4 Likes

What are the differences between rc4 and stable?

Read above, a few messages ago...

2 Likes

Would you consider opening an issue upstream? If there are regressions, they should know about it.

Unlikely, the run time cost of SQM is caused by the qdisc that are exercised, while most changes affect how SQM configures and starts these qdiscs... So not impossible, but rather unexpected. I would wonder more about the receive side scaling setting. What does:

for file in /sys/class/net/*
do
echo $file RX rps_cpus
cat $file"/queues/rx-0/rps_cpus"
echo $file TX xps_cpus
cat $file"/queues/tx-0/xps_cpus"
done

show?

Nope, that is IMHO solid release engineering, if a bug can be safely worked-around, but progress on fixing it has stalled it seems better to get the release out instead of waiting longer for Godot... Yes, unfortunate for users that use that functionality, and hopefully a fix can be found. But the alternative of delaying the release even further seems far worse. This is of course just my subjective opinion, others might disagree.

Well, the alternative is everybody "skipping"/not getting this release and actually testing it under real life conditions on a varied set of devices and configurations. IMHO the final steps of release maturation require a decent deployment, which for an opensource project like OpenWrt more or less means cutting a release to recruit sufficient many "testers". (Ideally everything with a release just works perfectly, but bugs happen)

9 Likes

There is already some described fix for offloading. If you want to speed up fix just test it yourself @Router and give feedback:
http://lists.openwrt.org/pipermail/openwrt-devel/2021-August/036223.html

4 Likes

Odd, none of the changes between https://github.com/tohojo/sqm-scripts/commit/bb064ad6065dcfb4966662bfab15b9fcdbb48e5f (1.5.0) and https://github.com/tohojo/sqm-scripts/commit/5d7e7977e14e147d5bcfa8a5f01636c7ab230fa4 (1.5.1) really should make any difference at run time...

Could you post the output of tc -s qdisc for both versions by any chance and if you are at it also the output of
SQM_DEBUG=1 SQM_VERBOSITY_MAX=8 /etc/init.d/sqm stop ; SQM_DEBUG=1 SQM_VERBOSITY_MAX=8 /etc/init.d/sqm start

That might help figuring out what is happening here.

1 Like