OpenWrt 19.07.7 - 服务版本 - 2021年2月18日

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

OpenWrt社区在此非常自豪地宣布OpenWrt 19.07服务版本的发布。本版本包括了安全更新、提升了设备支持并修复了一些Bug。

OpenWrt是一个为嵌入式设备设计的一款Linux操作系统,它可以用于替换庞大数量的无线路由器 以及非网络设备的原厂固件。查看硬件支持表格获取更多 关于硬件支持的信息。如果您想知道更多关于OpenWrt项目的细节,可查看 关于OpenWrt的页面


我们现在提供了一个名叫固件挑选器(Firmware Selector)的工具,以便让您更快为您的设备找到合适固件。您可以访问 使用。


您想收到关于新版本和安全修复等重要变更通知吗? 我们有一个新的邮件列表,支持RSS订阅,详见重要变更和公告


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.

  • 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
  • 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
  • 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.

  • Update Linux kernel from 4.14.215 to 4.14.221
  • Update wolfssl from 4.5.0 to 4.6.0
  • 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.

  • 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 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.

With the 19.07 major release, the OpenWrt project brings all supported targets back to a single common kernel version and further refines and broadens existing device support. It also introduces a new ath79 target and brings support for WPA3.

The 19.07 major release provides initial support for the new ath79 target, the future device tree based successor of the popular ar71xx target. For 19.07, both targets are still built, but it is recommended to switch to the ath79 target whenever possible: future releases of OpenWrt will drop support for the ar71xx target. See the ath79 technical reference for rationale about the transition.

To perform the upgrade, please follow the instructions from Upgrading from ar71xx to ath79. Functionality for a given device should be equivalent between the two targets: if this is not the case, please report the issue and revert back to ar71xx if needed.

The 19.07 major release brings initial support for WPA3. However, WPA3 is not enabled by default and requires installing specific packages: to run WPA3 as an access point, hostapd-openssl is needed. For use as a Wi-Fi station, you need either wpa-supplicant-openssl (station support only) or wpad-openssl (AP + station). Due to their large size, these packages are not installed by default, and it is impossible to install them on devices with less than 8MB flash.

It should also be noted that many existing client devices will never support WPA3, and that there are client devices that support WPA2 but cannot connect to an AP configured with WPA2+WPA3 mixed mode. Please only file bugs if you are sure the problem is not client related.

To configure your device as a WPA3 access point, see wpa_modes

The new version of LuCI, the integrated web interface for OpenWrt, implements client-side rendering of views. This improves performance by offloading some work that was done on the device (Lua code) to the client browser (Javascript code)

The LuCI ecosystem is large, and not all LuCI apps have been adapted to this change, which may result in crashes involving cbi.lua. In that case, install the luci-compat package.

If LuCI is loading slowly, consider installing uhttpd-mod-ubus, close and reopen the browser tab to start a new LuCI session.

With this step, Lua usage in LuCI is reduced and LuCI effectively comes closer to the goals of the experimental LuCI2 without having to rewrite everything from scratch.

This website uses cookies. By using the website, you agree with storing cookies on your computer. Also you acknowledge that you have read and understand our Privacy Policy. If you do not agree leave the website.More information about cookies
  • Last modified: 2021/05/28 14:14
  • by lujimmy