OpenWrt 19.07.8 service release

Hi,

The OpenWrt community is proud to announce the eighth service release of OpenWrt 19.07. It fixes security issues, improves device support, and brings a few bug fixes.

The main changes from OpenWrt 19.07.7 are:

Security fixes

Major bug fixes

  • Minor bugfixes to support GCC 11 as host compiler

Device support

  • TP-Link C7v5 allow flashing from vendor firmware bigger than v1.1
  • FRIZZ!Box 7320 Activate power supply to USB ports.

Various fixes and improvements

  • Only pack the signing keys for OpenWrt 19.07 and 21.02 and not the personal keys any more.

Core components

  • Update Linux kernel from 4.14.221 to 4.14.241
  • Update mac80211 from 4.19.161-1 to 4.19.193-1
  • Update ath10k-ct 4.19 driver from 2019-09-09 to 2021-06-03
  • Update OpenVPN from 2.4.7 to 2.4.11
  • Update openssl from 1.1.1i to 1.1.1k
  • Update mbedtls from 2.16.9 to 2.16.10
  • Update wolfssl from 4.6.0 to 4.7.0

Full release notes and upgrade instructions are available at
https://openwrt.org/releases/19.07/notes-19.07.8

In particular, make sure to read the regressions and known issues before upgrading:
https://openwrt.org/releases/19.07/notes-19.07.8#regressions

For a very detailed list of all changes since 19.07.7, refer to
https://openwrt.org/releases/19.07/changelog-19.07.8

For latest information about the 19.07 series, refer to the wiki at:
https://openwrt.org/releases/19.07/

To download a OpenWrt 19.07.8 firmware image for your device, head to the Table of Hardware:
https://openwrt.org/toh/start

Or use the new firmware selector:
https://firmware-selector.openwrt.org/

You can also navigate directly in the list of firmware images:
https://downloads.openwrt.org/releases/19.07.8/targets/

As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters.

Have fun!

The OpenWrt Community


To stay informed of new OpenWrt releases and security advisories, there
are new channels available:

21 Likes

Thank you for reducing e-waste by keeping our legacy devices alive using this version! :heart:

Note that RSS feeds are already available, we have them hooked up in the Matrix room as well:

1 Like

FYI
ar71xx NAND devices not there
https://downloads.openwrt.org/releases/19.07.7/targets/ar71xx/nand/
https://downloads.openwrt.org/releases/19.07.8/targets/ar71xx/

comes with DSA?

This is a service release to fix security in the old stuff. If you want a new release with features like DSA you should try a 21 release candidate

2 Likes

many thanks to the developers. I have upgraded without any problems.

I especially like the documentation in the wiki. Very clearly a user sees what has changed.

Even software regression are documented, great.

thanks again and have a nice sunday

2 Likes

Thx all. Installed without issues on 2x R7800 and a E4200v2. I will upgrade to 21.02 when there is a stable release!

The builds for ar71xx/nand and lantiq/falcon failed because of some network problems in the initial build, I retriggered builds for these two targets yesterday and the new images are available now.

4 Likes

Thanks for the new release. But I can't download it for my ath79/generic device, because it's missing the sha256sums.asc file needed to verify it.

sha256sums.asc is present in the directory for 19.07.7, but not for 19.07.8

As with every release, a big thank you for your ongoing efforts, it's highly appreciated!

A bit off-topic: I just wanted to donate (with mastercard), but it requires my full address, why?

1 Like

In the past on 19.x I used ath10k because of the better stability for my Android LOS devices but it seems that with this release ath10k-ct is as good (or better) as the aforementioned. Perhaps coincidence or some neural misconception ;- ) Anyway...a big thank you to the involved developers!

One usually provides their cc billing address, etc for anti-fraud detection by the ecommerce company processing the transaction.

1 Like

For the 21.02 release preparation we did bigger changes to the build bot infrastructure like upgrading build bot and this also affected the 19.07 build bots. Probably something went wrong and the sha256sums.asc files were not generated or coped any more.

We will have a look want went wrong.

5 Likes

That's my experience too.

Normally I have to announce an update to my family and am "forced" to reinstall the non-CT drivers mainly because of Xbox connection and some other issues.

A few days ago I did a "silent" update (R7800 router and R7800 AP) and keeping the standard CT drivers on both devices. No complaints for a few days now.

Big thanks to the developers.

2 Likes

Upgrade done within minutes on a tplink archer c6 v2. Wifi performance of 19.07.8 increased by at least 10 - 20% on both bands compared to 19.07.7.

Good job!

1 Like

Just to be clear, are you saying that an upgrade like this normally necessities re-doing a non-CT configuration, if that's what someone had and wants? If so, I guess I should have known, since they're packages like anything else you might have installed that would need re-installing, but I thought of these more as drivers, I guess.

After an update (sysupgrade or factory) it is necessary to reinstall any package but the standard ones. This also applies to the non-CT drivers (CT drivers are the standard; since 19.07?).
I don't know if there are any exceptions on this.
There are probably more ways to manage an upgrade of a non standard configuration but that question is better answered by an expert.

1 Like

Exactly. This is also described on

I have done my own shell-script and added it to the files that are backed, so after an upgrade that keeps the configuration I just need to execute that script and it installs me all packages again, another reboot, and the system is (hopefully) back withe the upgraded openwrt and the according packages.

It starts like

opkg update;                                                            
opkg remove wpad-basic;                                              
opkg install luci-ssl-openssl;
...
1 Like

The 19.07.8 release is now signed with GPG and the signature was uploaded.
@jow added the missing signatures and uploaded them.
The signing key for OpenWrt 19.07 had expired and then gpg just did not created a signature.

8 Likes