Just upgraded my NanoPi-R4S main router yesterday from 24.10 5 to 25.12.0-rc3 and to 25.12.0-rc5 today. Everything works fine, no major issue during the upgrade.
Great job, thanks a lot!
1 Like
It works on the rc4 release, and I don’t foresee my ISP making any changes to their IPv6 implementation. They use he.net for the tunnel. I have a public IP4 address, too.
Updated my fleet:
bpir4: needed power cycle to come back up. This one confuses me.
mt3000: no issues
remidax6s: no issues
ontic508: no issues
Dual stack configuration works on RC5 just as it was on RC4.
I used ASU to upgrade from rc4 to rc5 on a Linksys MR7350, this unit is set up as a repeater and all is working well. Thank yous!
Right, but is 6to4 perhaps broken in rc5, perhaps at the packaging level for certain platforms?
1 Like
I would like to know if nonresponsive lan port issue is fixed on the BT Homehub 5a, the changelog does mention something but it seems to be a bit unclear. To scared to install and end up with a unresponsive unit once again.
EDUP AX1800 ( SIMAX1800T equivalent ramips/mt7621), Attended Sysupgrade from rc4.
All tested. I note the WAN selection for adblocker didn't survive, needed the checkbox ticking again and a restart.
Thank you devs.
Hostname rax
Model EDUP EP-RT2960S
Architecture MediaTek MT7621 ver:1 eco:3
Target Platform ramips/mt7621
Firmware Version OpenWrt 25.12.0-rc5 r32673-482ba7230a / LuCI openwrt-25.12 branch 26.050.04191~355a432
Kernel Version 6.12.71
Local Time 20 Feb 2026, 16:02:34 UTC
Kindof qos drops on dsa master causes avalanche of pause frames on both invisible vlans quadrupling the grief
... or server infrastructure was retired.
3 dumb APs migrated no problems to -rc5 (from 24.10 stable)
although on main router it seems like firewall has not fully migrated?
root@zenek:~# apk info | grep firewall
firewall
luci-app-firewall
root@zenek:~# apk info | grep nft
ip6tables-nft
iptables-nft
kmod-nft-compat
kmod-nft-core
libiptext-nft0
libnftnl11
xtables-nft
root@zenek:~#
Package version changes:
firewall4 not-installed 2025.03.17~b6e51575-r1
1 packages are out-of-date
Automatic package replacements/removals:
Package Replaced-by
firewall firewall4
Details at https://sysupgrade.openwrt.org/json/v1/overview.json
Default package analysis:
Default Provided-by
kmod-nft-offload not installed
nftables not installed
wpad-basic-mbedtls not installed
had to install:
apk add firewall4 nftables kmod-nft-core kmod-nft-offload
apk del firewall
and restart firewall to get it back to work
firewall is replaced by firewall4 by asu since v23.05
you have to copy/paste package lists to selector or imagebuilder if you want otherwise.
it had to be since 23 then, but was not verbosed earlier (and I think I had nft working on 24.10)
Anyone else seeing issues with travelmate? I guess could be wpa_supplicant.
I have two MT7612U usb adaptors with travelmate (an AP and an upstream). These were/are playing great with rc4 but used "Attended Sysupgrade" to rc5 and now the AP is still working but no upstream connection.
I tried a build of rc5 and a clean install and restore from backup with the same result.
Anyone else seeing this or do I need to dig further into my setup.
Fri Feb 20 18:07:02 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: SME: Trying to authenticate with 26:5a:4c:df:a5:63 (SSID='ABC' freq=5785 MHz)
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 20.961449] phy2-sta0: authenticate with 26:5a:4c:df:a5:63 (local address=52:4f:1c:8b:f7:33)
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 20.969935] phy2-sta0: send auth to 26:5a:4c:df:a5:63 (try 1/3)
Fri Feb 20 18:07:02 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: SME: Trying to authenticate with 26:5a:4c:df:a5:63 (SSID='ABC' freq=5785 MHz)
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 21.093517] phy2-sta0: authenticate with 26:5a:4c:df:a5:63 (local address=52:4f:1c:8b:f7:33)
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 21.102006] phy2-sta0: send auth to 26:5a:4c:df:a5:63 (try 1/3)
Fri Feb 20 18:07:02 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: Trying to associate with 26:5a:4c:df:a5:63 (SSID='ABC' freq=5785 MHz)
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 21.133084] phy2-sta0: authenticated
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 21.143803] phy2-sta0: associate with 26:5a:4c:df:a5:63 (try 1/3)
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 21.152951] phy2-sta0: RX AssocResp from 26:5a:4c:df:a5:63 (capab=0x1111 status=0 aid=2)
Fri Feb 20 18:07:02 2026 daemon.notice netifd: Network device 'phy2-sta0' link is up
Fri Feb 20 18:07:02 2026 daemon.notice netifd: Interface 'trm_wwan' has link connectivity
Fri Feb 20 18:07:02 2026 daemon.notice netifd: Interface 'trm_wwan' is setting up now
Fri Feb 20 18:07:02 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: Associated with 26:5a:4c:df:a5:63
Fri Feb 20 18:07:02 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Fri Feb 20 18:07:02 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: Unknown event 37
Fri Feb 20 18:07:02 2026 kern.info kernel: [ 21.183424] phy2-sta0: associated
Fri Feb 20 18:07:02 2026 daemon.notice netifd: trm_wwan (4725): udhcpc: started, v1.37.0
Fri Feb 20 18:07:03 2026 daemon.notice netifd: trm_wwan (4725): udhcpc: broadcasting discover
Fri Feb 20 18:07:03 2026 kern.debug kernel: [ 21.235962] phy2-sta0: Limiting TX power to 23 (23 - 0) dBm as advertised by 26:5a:4c:df:a5:63
Fri Feb 20 18:07:03 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: WPA: Key negotiation completed with 26:5a:4c:df:a5:63 [PTK=CCMP GTK=CCMP]
Fri Feb 20 18:07:03 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: CTRL-EVENT-CONNECTED - Connection to 26:5a:4c:df:a5:63 completed [id=0 id_str=]
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Set MLD config: [ ]
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Reload all interfaces
Fri Feb 20 18:07:03 2026 daemon.notice wpa_supplicant[1397]: Set MLD config: [ ]
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Reloaded settings for phy phy1
Fri Feb 20 18:07:03 2026 daemon.notice netifd: radio2 (4956): wifi-scripts: Starting
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Set MLD config: [ ]
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Reload all interfaces
Fri Feb 20 18:07:03 2026 daemon.notice wpa_supplicant[1397]: Set MLD config: [ ]
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Reloaded settings for phy phy1
Fri Feb 20 18:07:03 2026 daemon.notice netifd: radio2 (4956): command failed: Not supported (-95)
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Set MLD config: [ ]
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Reload all interfaces
Fri Feb 20 18:07:03 2026 daemon.notice netifd: radio2 (4956): command failed: Not supported (-95)
Fri Feb 20 18:07:03 2026 daemon.notice hostapd: Reloaded settings for phy phy1
Fri Feb 20 18:07:03 2026 daemon.notice wpa_supplicant[1397]: Set new config for phy phy2
Fri Feb 20 18:07:03 2026 daemon.notice wpa_supplicant[1397]: Remove interface phy2-sta0
Fri Feb 20 18:07:03 2026 kern.info kernel: [ 22.099288] phy2-sta0: deauthenticating from 26:5a:4c:df:a5:63 by local choice (Reason: 3=DEAUTH_LEAVING)
Fri Feb 20 18:07:03 2026 daemon.notice netifd: Network device 'phy2-sta0' link is down
Fri Feb 20 18:07:03 2026 daemon.notice netifd: Interface 'trm_wwan' has link connectivity loss
Fri Feb 20 18:07:03 2026 daemon.notice netifd: trm_wwan (4725): udhcpc: received SIGTERM
Fri Feb 20 18:07:04 2026 daemon.notice netifd: trm_wwan (4725): udhcpc: entering released state
Fri Feb 20 18:07:04 2026 daemon.notice netifd: trm_wwan (4725): Command failed: ubus call network.interface notify_proto { "action": 0, "link-up": false, "keep": false, "interface": "trm_wwan" } (Permission denied)
Fri Feb 20 18:07:04 2026 daemon.notice netifd: Interface 'trm_wwan' is now down
Fri Feb 20 18:07:04 2026 authpriv.info dropbear[4995]: Child connection from 192.168.179.4:47018
Fri Feb 20 18:07:04 2026 daemon.notice wpa_supplicant[1397]: nl80211: send_event_marker failed: Source based routing not supported
Fri Feb 20 18:07:04 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: CTRL-EVENT-DISCONNECTED bssid=26:5a:4c:df:a5:63 reason=3 locally_generated=1
Fri Feb 20 18:07:04 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: CTRL-EVENT-DSCP-POLICY clear_all
Fri Feb 20 18:07:04 2026 daemon.notice wpa_supplicant[1397]: phy2-sta0: CTRL-EVENT-DSCP-POLICY clear_all
Fri Feb 20 18:07:04 2026 daemon.notice wpa_supplicant[1397]: nl80211: deinit ifname=phy2-sta0 disabled_11b_rates=0
Fri Feb 20 18:07:04 2026 daemon.err wpa_supplicant[1397]: rmdir[ctrl_interface=/var/run/wpa_supplicant]: Permission denied
Fri Feb 20 18:07:05 2026 daemon.notice netifd: Interface 'trm_wwan' is disabled
Fri Feb 20 18:07:05 2026 daemon.notice hostapd: Set new config for phy phy2:
Fri Feb 20 18:07:05 2026 daemon.notice netifd: radio2 (4956): wifi-scripts: Configuring 'phy2' txantenna: 4294967295, rxantenna: 4294967295 distance: 0
Fri Feb 20 18:07:05 2026 daemon.notice wpa_supplicant[1397]: Start pending MLD interfaces
Fri Feb 20 18:07:25 2026 daemon.err travelmate-service.sh[4455]: awk: bad regex '[': Missing ']'
Fri Feb 20 18:07:25 2026 daemon.err travelmate-service.sh[4455]: awk: bad regex '[': Missing ']'
Fri Feb 20 18:07:25 2026 daemon.err travelmate-service.sh[4455]: awk: bad regex '[': Missing ']'
Fri Feb 20 18:07:25 2026 daemon.err travelmate-service.sh[4455]: awk: bad regex '[': Missing ']'
Fri Feb 20 18:07:25 2026 daemon.err travelmate-service.sh[4455]: awk: bad regex '[': Missing ']'
I believe you still need to manually add kmod-dsa-gswip to the device if you do an ASU build (don't know if the pre-built images from download.openwrt.org include it, I would assume so).
There's a PR on ASU to do this automatically (https://github.com/openwrt/asu/pull/1579), but it has not been merged and deployed yet.
2 Likes
How could that be? It works when I flip back to rc4. ISP is CenturyLink/ Level3 fiber (USA).
As far as I remember the infrastructure of relays was largely supported by Microsoft and it is about to be retired. But I might be wrong...
Same here. On previous release candidates the client connection would disable after a reboot only, but was working fine once enabled manually after a reboot.
Now on rc5 the client connection seemingly randomly disables while the router is running, even if I set it up as a client via Network–>Wireless and not via Travelmate.
Also my 5/6GHz APs aren’t showing up at all until the 2.4Ghz client connects (and then it randomly hangs, regardless if I have 5/6GHz APs enabled or completely removed).
Also, any progress on the infamous AP+STA bug? (not related to DFS channels) - same behaviour even on 2.4GHz band.
Using Asus BT8.
You can get ip6 relay from huricane tunnel broker.
Maybe this fixes your AP+STA problems:
The change is included in the 25.12-SNAPSHOT, please try this and report back:
1 Like