OpenWrt 19.07.7 service release

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

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 19.07.7, r11306-c4a6851c72
 -----------------------------------------------------

Main changes from OpenWrt 19.07.6

Only the main changes are listed below. See changelog-19.07.7 for the full changelog.

Security fixes

Note: security fixes for most packages can also be applied by upgrading only the affected packages on running devices, without the need for a full firmware upgrade. This can be done with opkg update; opkg upgrade the_package_name or through the LuCI web interface.

Nevertheless, we encourage all users to upgrade their devices to OpenWrt 19.07.7 or later versions whenever possible.

Major bug fixes

  • Fix dnsmasq error messages such as failed to send packet: Network unreachable or failed to send packet: Address family not supported by protocol that could be filling up logs. This was a regression caused by the dnsmasq update in 19.07.6.
  • Fix opkg so that it purges obsolete packages from its local cache. This fixes a long-standing issue in the ImageBuilder where a manual cleanup was needed before rebuilding: FS#2690

Device support

  • Improve stability of mediatek Ethernet switch (affects many mt7621 devices): FS#2628
  • Fix Wi-Fi band detection on some Broadcom-based devices
  • Fix poor 2.4 GHz Wi-Fi performance on TP-Link Archer C50 v4 due to a missing EEPROM chip ID: FS#2781
  • Make initramfs image usable out-of-the-box on Turris Omnia
  • Use full flash size on Nucom R5010UN v2
  • Fix support for TP-Link TL-WR810N v1 in ath79: FS#3522
  • Remove broken factory image for TP-Link Archer C2 v1
  • Fix unintended failsafe mode during boot on Netgear EX6150: FS#3590

Various fixes and improvements

  • The ImageBuilder no longer requires compilers (gcc, g++) and libncurses-dev. This was partially implemented in 19.07.6 but one part was missing to make it actually work.
  • Update to a new major version of ksmbd to fix several bugs. This breaks compatibility with previous versions of OpenWrt (19.07.0 to 19.07.6): it is no longer possible to install a working version of ksmbd-tools on previous versions of OpenWrt. Existing installations will keep working, but ksmbd-tools should not be upgraded with opkg. PR#14647

See addressed_bugs for a complete list of bug fixes.

LuCI web interface

Core components

  • Update Linux kernel from 4.14.215 to 4.14.221
  • Update wolfssl from 4.5.0 to 4.6.0

Regressions

  • kmod-fs-ksmbd has a dependency to the not existing package kmod-crypto-arc4. Installing kmod-fs-ksmbd returns this:
    satisfy_dependencies_for: Cannot satisfy the following dependencies for kmod-fs-ksmbd: * kmod-crypto-arc4 * opkg_install_cmd: Cannot install package kmod-fs-ksmbd.
    • Run this to force the installation: GH#14771
      opkg install --force-depends kmod-fs-ksmbd
      to force the installation.

Known issues

  • Transition to ath79: some devices that are supported in ar71xx are not yet supported in ath79: this is a community effort. Helping to port devices to ath79 to make them available in future releases is very welcome.
  • Device support: images for some device became too big to support a persistent overlay, causing such devices to lose configuration after a reboot. If you experience this problem, please report the affected device in the forum and consider downgrading to OpenWrt 18.06 or using the Image Builder to pack a smaller custom image
  • Device support: conversely, certain images for devices with small flash (4 MB) are no longer built for the release

See also: active bug reports for openwrt-19.07

Upgrading to OpenWrt 19.07.7

Upgrading from previous OpenWrt 19.07 versions is straightforward thanks to the sysupgrade utility: sysupgrade from web interface or sysupgrade from command-line.

An upgrade from OpenWrt 18.06 to OpenWrt 19.07 is supported in many cases, including preserving configuration. A configuration backup is advised nonetheless when upgrading from OpenWrt 18.06.

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

Have fun!

The OpenWrt Community

24 Likes

sysupgrade from 19.07.6 ran smoothly on tp-link archer c6 v2 eu.

Wifi up and running again, family is satisfied, good job, developers :+1:t2:

Sysupgrade from 19.07.07 on xiaomi r3g v1
Wifi working stable again and bug of dnsmasq solved.
Thanks for working dev's

ER-X upgraded from 19.07.6 to 19.07.7 - all is well after ~2 days of run time. Zero issues.

Hi, after upgrading to 19.7.7 from 19.7.6 on GL.iNet GL-B1300 my DNS (that is simply configured on lan interface and active) is now my isp dns. I mean the DNS I setup there is ignored.
Nothing changed, just upgraded configuration.
Any idea about how to enforce that, without installing other components I want to keep it simple and update to latest versions without reconfigure everything..
Thnaks

No issue with WNDR4300v1 by sysupgrade.

Backed up config files from 19.07.6 to archive config files. Rebooted to alt-OEM partition using Advanced Reboot package.

Installed 19.07.7 fresh from alt-OEM partition on MR8300 using EA8300 factory release (not sysupgrade), reinstalled needed optional packages "as is" and without further config, Wi-Fi was left disabled and unconfigured.

Restored backup, without "reset to defaults" (as this is a fresh factory install) and voilà ! All works fine, took a few minutes and no headache.

Average load is higher than 19.07.6 (which was drastically reduced from .5), but still way lower than 19.07.5.

RAM use is lower than 19.07.6 (which was drastically increased by 10 to 20 MB from .5), now back to more in line with 19.07.5.

There now seems to be a better balance between average load and RAM use.

Many thanks to Devs, you guys are definitely working very hard fixing issues !

1 Like

I think you need to define DNS servers for your WAN interface, not your LAN interface.

Undo the settings you changed on your LAN interface, and under Network>Interfaces> in luci, try Editing WAN settings on your Gateway router under the "Advanced Settings" tab and define the DNS servers you want to use (e.g., 1.1.1.2 and 9.9.9.9) under "Use custom DNS servers" and uncheck "Use DNS servers advertised by peer". Same thing for WAN6, except use IPv6 servers of course (e.g., 2606:4700:4700::1112 and 2620:fe::fe).

This works fine for me on 19.07.7 (and has also worked fine on any other version for that matter).

Similar path for my WRT3200ACM.

Luci feels way faster. Wifi is slower, but with the mess that is mwlwifi I'm just happy it works at all :rofl:
That being said, I'm having far less drop-outs of the 5GHz band, so...

Upgraded from 19.07.6->.7 just fine on TP-Link Archer C2600 and WDR4300. Thanks for all the hard work!

Fritzbox 4040 upgraded from .6, looks good, thanks.

Running great on my WRT32X thanks

Correction, this is NOT in .7, the fix was committed on 2/15/2021, but the .7 build pulls MT76 from 2/1/2021

Proof: a ZBT WE3525 (MT7621 / 7603)running 19.0.7.7 shows this when queried via ethtool:

tcp-segmentation-offload: on
	tx-tcp-segmentation: on
	tx-tcp-ecn-segmentation: off [fixed]
	tx-tcp-mangleid-segmentation: on
	tx-tcp6-segmentation: on

And we see the infamous

6856.868079] NETDEV WATCHDOG: eth0 (mtk_soc_eth): transmit queue 0 timed out

in the logs.

After doing this: ethtool -K eth0 tso off
no more errors. So anyone affected can add that to a script that runs on startup.

1 Like

It is included in .7 :slight_smile: mt76 is the wireless driver, it has nothing to do with it.

The transmit queue timeout can still happen, but crashes should happen less frequently. It's a workaround, not a real fix (the fix will probably never happen).

Not sure why ethtool wouldn't report that, I haven't tested it (I'm not even sure that this NIC/switch can actually be controlled by ethtool).

1 Like

rock solid on unifiac-pro

I upgraded from 19.07.06 to this release on my Linksys WRT1900ACS, keeping the configuration. I then installed the additional packages that I had installed with the prior version and rebooted.

Awesome job with the timely release of security updates.

I have a crash on wireless 2.4ghz

Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.462957] ------------[ cut here ]------------
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.467643] WARNING: CPU: 3 PID: 0 at /builder/shared-workdir/build/build_dir/target-mipsel_24kc_musl/linux-ramips_mt7621/mt76-2021-02-15-5c768dec/mt7603/mac.c:204 0x8f364320 [mt7603e@8f360000+0x9100]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.485461] Modules linked in: pppoe ppp_async pppox ppp_generic nf_conntrack_ipv6 mt76x2e mt76x2_common mt76x02_lib mt7603e mt76 mac80211 iptable_nat ipt_REJECT ipt_MASQUERADE cfg80211 xt_time xt_tcpudp xt_tcpmss xt_statistic xt_state xt_recent xt_nat xt_multiport xt_mark xt_mac xt_limit xt_length xt_hl xt_helper xt_hashlimit xt_ecn xt_dscp xt_conntrack xt_connmark xt_connlimit xt_connbytes xt_comment xt_TCPMSS xt_REDIRECT xt_LOG xt_HL xt_FLOWOFFLOAD xt_DSCP xt_CT xt_CLASSIFY wireguard slhc nf_reject_ipv4 nf_nat_redirect nf_nat_masquerade_ipv4 nf_conntrack_ipv4 nf_nat_ipv4 nf_nat nf_log_ipv4 nf_flow_table_hw nf_flow_table nf_defrag_ipv6 nf_defrag_ipv4 nf_conntrack_rtcache nf_conntrack_netlink iptable_raw iptable_mangle iptable_filter ipt_ECN ip_tables crc_ccitt compat sch_cake nf_conntrack tcp_bbr
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.556246]  sch_tbf sch_ingress sch_htb sch_hfsc em_u32 cls_u32 cls_tcindex cls_route cls_matchall cls_fw cls_flow cls_basic act_skbedit act_mirred ledtrig_usbport xt_set ip_set_list_set ip_set_hash_netportnet ip_set_hash_netport ip_set_hash_netnet ip_set_hash_netiface ip_set_hash_net ip_set_hash_mac ip_set_hash_ipportnet ip_set_hash_ipportip ip_set_hash_ipport ip_set_hash_ipmark ip_set_hash_ip ip_set_bitmap_port ip_set_bitmap_ipmac ip_set_bitmap_ip ip_set nfnetlink nf_log_ipv6 nf_log_common ip6table_mangle ip6table_filter ip6_tables ip6t_REJECT x_tables nf_reject_ipv6 ifb ip6_udp_tunnel udp_tunnel sit tunnel4 ip_tunnel veth snd_rawmidi snd_seq_device snd_pcm_oss snd_pcm_dmaengine snd_pcm snd_timer snd_mixer_oss snd_hwdep snd_compress snd soundcore input_core uas usb_storage sd_mod scsi_mod ext4
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.626707]  mbcache jbd2 crc32c_generic leds_gpio xhci_plat_hcd xhci_pci xhci_mtk xhci_hcd gpio_button_hotplug usbcore nls_base usb_common
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.639235] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.14.221 #0
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.645300] Stack : 00000000 00000000 00000000 00000001 00000000 00000000 00000000 00000000
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.653633]         00000000 00000000 00000000 00000000 00000000 00000001 8fc0fc78 1cc2823d
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.661965]         8fc0fd10 00000000 00000000 00007358 00000038 8049e2b8 00000007 00000000
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.670300]         00000000 80550000 0009c103 00000000 8fc0fc58 00000000 00000000 8f368bc4
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.678636]         8f364320 000000cc 8f370000 00000001 00000000 802ae4c0 0000000c 806b000c
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.686971]         ...
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.689406] Call Trace:
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.689423] [<8049e2b8>] 0x8049e2b8
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.695330] [<8f364320>] 0x8f364320 [mt7603e@8f360000+0x9100]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.701107] [<802ae4c0>] 0x802ae4c0
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.704588] [<8000c1a0>] 0x8000c1a0
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.708058] [<8000c1a8>] 0x8000c1a8
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.711527] [<804870f4>] 0x804870f4
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.715002] [<8f364320>] 0x8f364320 [mt7603e@8f360000+0x9100]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.720717] [<80072dd4>] 0x80072dd4
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.724190] [<8002e798>] 0x8002e798
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.727676] [<8f364320>] 0x8f364320 [mt7603e@8f360000+0x9100]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.733399] [<8002e880>] 0x8002e880
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.736883] [<8034e308>] 0x8034e308
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.740364] [<8f364320>] 0x8f364320 [mt7603e@8f360000+0x9100]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.746082] [<80007488>] 0x80007488
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.749555] [<8f340274>] 0x8f340274 [mt76@8f340000+0x79e0]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.755071] [<8f364488>] 0x8f364488 [mt7603e@8f360000+0x9100]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.760787] [<80017f6c>] 0x80017f6c
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.764270] [<8f3442fc>] 0x8f3442fc [mt76@8f340000+0x79e0]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.769770] [<8f3618d4>] 0x8f3618d4 [mt7603e@8f360000+0x9100]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.775547] [<8f343b8c>] 0x8f343b8c [mt76@8f340000+0x79e0]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.781036] [<8f340dec>] 0x8f340dec [mt76@8f340000+0x79e0]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.786550] [<803657a8>] 0x803657a8
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.790030] [<804a50b8>] 0x804a50b8
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.793500] [<80033164>] 0x80033164
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.796971] [<8025b710>] 0x8025b710
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.800443] [<80007488>] 0x80007488
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.803912]
Wed Feb 24 22:35:15 2021 kern.warn kernel: [95134.805476] ---[ end trace b67f5be5eff963fb ]---

Consider opening an issue on Github, maybe!

Just interested. What target do you have? Do you use configs from previous version or new ones?