OpenWrt 21.02.0 - First Stable Release

How do I verify the 21.02 signature file? According to I need to do gpg --receive-keys 88CA59E88F681580 but I get gpg: error reading key: No public key, I tried gpg --keyserver --receive-keys 88CA59E88F681580 but I get

gpg: key 88CA59E88F681580: no user ID
gpg: Total number processed: 1

If I then try gpg --status-fd 1 --with-fingerprint --verify sha256sums.asc sha256sums I get

gpg: Signature made Чт 02 сен 2021 09:44:11 MSK
gpg:                using RSA key 667205E379BAF348863A5C6688CA59E88F681580
[GNUPG:] ERRSIG 88CA59E88F681580 1 10 00 1630565051 9
[GNUPG:] NO_PUBKEY 88CA59E88F681580
gpg: Can't check signature: No public key

in LuCi firmware menu, upload the sysupgrade file to the router. Before you confirm the actual flash upgrade process via mouse click, LuCi calculates and shows the signature.


Actually that only shows the signature of the file. It doesn’t verify it.

The OpenWRT trust management is based on the gpg signature of the sha256 file. Once that is verified you can use the sha256 data in that file to verify the actual firmware file.


Ok, I did it by just manually downloading this file;a=blob_plain;f=gpg/88CA59E8.asc and then doing gpg --import ~/Downloads/gpg_88CA59E8.asc For some reason the key at is different than the one at
Edit: After some digging, it looks like strips down identity information from public keys if an email is not verified, and gpg doesn't allow importing such keys.

1 Like

I don't know if anyone got this error.
I was trying to upgrade my WRT1900ACv1 to 21.02 first stable release. I thought upgrading from 19.07.8 to 21.02 is supported. Do I have to wipe out the whole partition and reinstall the image?
I got the image from firmware selector. I appreciate any tips.

1 Like

Like the error message says, you need to use the "factory image" instead of the sysupgrade image. You should be able to flash it by selecting the "force upgrade" there. And unselect the "keep settings".

The underlying reason is explained in that error message that you see: Linksys had defined too small partition for the new kernel versions (used in 21.02 and master) for WRT1900ACv1 (mamba) and WRT32X (venom). So, the kernel partition has been enlarged for those two, but that prevents using the sysupgrade, and you need to use the "factory" image to start fresh.;a=commitdiff;h=8458ebe18b84702039020c523018e39f564ccf6c;hp=7939d4a1b13b0c44dbfa4cd03180fe4cd5b2fe6b

At the same time you also get the switch config change from swconfig to the new DSA, so you should not restore your old config from backup...


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.


Yes, that fixes the problem.


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


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.


What are the differences between rc4 and stable?