on kirkwood there seems to be a network problem downloading additional packages:
I've seen the same on several zyxel wsm20, software invoked reboot does not complete.
Upgraded Hasivo S1100W-8XGT-SE from a 24.10 snapshot to 25.10.0-RC1, no issues so far. Also upgraded a Zyxel XGS1250-12 A1 from 24.10.4 to 25.10.0-RC1, no issues there either. Thanks!
hi,
thanks for the new release. as being an rc1 let me report something is not ok with docker on x86. after doing owut upgrade or apk add, the same problem after a service dockerd start:
Mon Dec 22 18:46:45 2025 daemon.err modprobe: failed to find a module named aufs
Mon Dec 22 18:46:46 2025 daemon.err dockerd[7389]: time="2025-12-22T17:46:46.501019290Z" level=warning msg="Could not load necessary modules for IPSEC rules: protocol not supported"
Mon Dec 22 18:46:46 2025 daemon.info modprobe: nf_conntrack is already loaded
Mon Dec 22 18:46:46 2025 daemon.err modprobe: failed to find a module named nf_conntrack_netlink
Mon Dec 22 18:46:46 2025 daemon.err dockerd[7389]: time="2025-12-22T17:46:46.607978009Z" level=warning msg="could not create bridge network for id 1781331791c5396ab962e643539799038d4530b5ea19188f2a8f2c42cef7ce78 bridge name docker0 while booting up from persistent state: Failed to Setup IP tables: Unable to enable NAT rule: (iptables failed: iptables --wait -t nat -I POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE: iptables v1.8.10 (nf_tables): CHAIN_ADD failed (No such file or directory): chain POSTROUTING\n (exit status 4))"
Mon Dec 22 18:46:46 2025 daemon.err dockerd[7389]: time="2025-12-22T17:46:46.677659666Z" level=warning msg="could not create bridge network for id c673bf8f4619ee461e6f4b5ffd9f5eed5ae40301e111fdde64965d22ad6618b3 bridge name br-c673bf8f4619 while booting up from persistent state: Failed to Setup IP tables: Unable to enable NAT rule: (iptables failed: iptables --wait -t nat -I POSTROUTING -s 172.18.0.0/16 ! -o br-c673bf8f4619 -j MASQUERADE: iptables v1.8.10 (nf_tables): CHAIN_ADD failed (No such file or directory): chain POSTROUTING\n (exit status 4))"
Mon Dec 22 18:46:47 2025 daemon.err dockerd[7389]: failed to start daemon: Error initializing network controller: error creating default "bridge" network: Failed to Setup IP tables: Unable to enable NAT rule: (iptables failed: iptables --wait -t nat -I POSTROUTING -s 172.17.0.0/16 ! -o docker0 -j MASQUERADE: iptables v1.8.10 (nf_tables): CHAIN_ADD failed (No such file or directory): chain POSTROUTING
Mon Dec 22 18:46:47 2025 daemon.err dockerd[7389]: (exit status 4))
# iptables -tnat -L
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain PREROUTING (policy ACCEPT)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain POSTROUTING (policy ACCEPT)
target prot opt source destination
Chain DOCKER (0 references)
target prot opt source destination
cat /etc/config/dockerd
# The following settings require a restart of docker to take full effect, A reload will only have partial or no effect:
# log_driver
# bip
# blocked_interfaces
# extra_iptables_args
# device
config globals 'globals'
# option alt_config_file '/etc/docker/daemon.json'
option data_root '/storage/opt/docker/'
option log_driver 'syslog'
#option log_opts 'udp://127.0.0.1:514'
option log_level 'warn'
option iptables '1'
# list hosts 'unix:///var/run/docker.sock'
# option bip '172.18.0.1/24'
# option fixed_cidr '172.17.0.0/16'
# option fixed_cidr_v6 'fc00:1::/80'
# option ipv6 '1'
# option ip '::ffff:0.0.0.0'
# list dns '172.17.0.1'
# list registry_mirrors 'https://<my-docker-mirror-host>'
# list registry_mirrors 'https://hub.docker.com'
# If your organization uses a proxy server to connect to the internet, you may need to configure the proxy.
# See https://docs.docker.com/engine/daemon/proxy/ for more details
config proxies 'proxies'
# option http_proxy 'http://proxy.example.com:3128'
# option https_proxy 'https://proxy.example.com:3129'
# option no_proxy '*.test.example.com,.example.org,127.0.0.0/8'
# Docker doesn't work well out of the box with fw4. This is because Docker relies on a compatibility layer that
# naively translates iptables rules. For the best compatibility replace the following dependencies:
# `firewall4` -> `firewall`
# `iptables-nft` -> `iptables-legacy`
# `ip6tables-nft` -> `ip6tables-legacy`
# Docker undermines the fw3 rules. By default all external source IPs are allowed to connect to the Docker host.
# See https://docs.docker.com/network/iptables/ for more details.
# firewall config changes are only additive i.e firewall will need to be restarted first to clear old changes,
# then docker restarted to load in new changes.
config firewall 'firewall'
option device 'docker0'
list blocked_interfaces 'wan'
option extra_iptables_args '--match conntrack ! --ctstate RELATED,ESTABLISHED' # allow outbound connections
# ubus call system board
{
"kernel": "6.12.62",
"hostname": "vOpenWrt",
"system": "AMD Ryzen 5 3600 6-Core Processor",
"model": "VMware, Inc. VMware Virtual Platform",
"board_name": "vmware-inc-vmware-virtual-platform",
"rootfs_type": "ext4",
"release": {
"distribution": "OpenWrt",
"version": "25.12.0-rc1",
"firmware_url": "https://downloads.openwrt.org/",
"revision": "r32353-9e9b05130c",
"target": "x86/64",
"description": "OpenWrt 25.12.0-rc1 r32353-9e9b05130c",
"builddate": "1766089549"
}
}
First notes from doing my Monday updates/upgrades:
Archer C7 v4, ran df -h before and after:
24.10.4 /dev/root 7.8M 7.8M 0 100% /rom
25.12.0-rc1 /dev/root 8.3M 8.3M 0 100% /rom
Apropos OpenWrt 25.12.0-rc1 - Release Candidate - #7 by dave14305, the device got a new duid on wan6, and since this is a physical subnet device, I had to change the dhcp settings on the upstream router.
On the Archer after reboot:
$ uci get network.globals.dhcp_default_duid
000450d97252ab37450aa5208ac072982345
Then on the main router (where the host[index] identifies that specific entry):
$ uci set dhcp.@host[1].duid="000450d97252ab37450aa5208ac072982345"
$ uci commit
Then back on the Archer, I restarted wan6...
OpenWrt 25.12.0-rc1 fixed the wan MAC address assignment problem in Linksys EA8500. Now the wan’s MAC address is assigned with (lan’s MAC address - 1) like other Linksys routers (MR8300 for example). In 24.10 releases, the wan’s MAC address is assigned with (lan’s MAC address + 1) which conflicts with the 2.4GHz wifi radio’s MAC address (both has the same MAC address) and causes 2.4GHz wifi not-working problem. Thanks, developers.
2 Likes
Well, today I was moving a lot of wifi devices to a new vlan and I needed to restart my router a lot. As I saw Ipv6 not working - I disabled it. However, after my last restart I got the following message from ban-ip:
[12/22/2025-22:20:16] banIP-1.6.0-r1[4085]: start banIP processing (boot, 1.6.0-r1)
[12/22/2025-22:20:26] banIP-1.6.0-r1[4085]: no wan interface 'wan6'
[12/22/2025-22:30:37] banIP-1.6.0-r1[11151]: start banIP processing (reload, 1.6.0-r1)
[12/22/2025-22:30:47] banIP-1.6.0-r1[11151]: no wan interface 'wan6'
[12/22/2025-22:32:37] banIP-1.6.0-r1[12436]: start banIP processing (restart, 1.6.0-r1)
[12/22/2025-22:32:47] banIP-1.6.0-r1[12436]: no wan interface 'wan6'
[12/22/2025-22:34:34] banIP-1.6.0-r1[14631]: start banIP processing (reload, 1.6.0-r1)
[12/22/2025-22:34:35] banIP-1.6.0-r1[14631]: add uplink 'xxxxxx' to local allowlist
[12/22/2025-22:34:35] banIP-1.6.0-r1[14631]: add uplink 'xxxxxx' to local allowlist
[12/22/2025-22:34:35] banIP-1.6.0-r1[14631]: initialize banIP nftables namespace
[12/22/2025-22:34:35] banIP-1.6.0-r1[14631]: start banIP download processes
[12/22/2025-22:34:38] banIP-1.6.0-r1[14631]: skip empty feed 'pallebone.v4'
[12/22/2025-22:34:42] banIP-1.6.0-r1[14631]: start banIP domain lookup
[12/22/2025-22:34:44] banIP-1.6.0-r1[14631]: finish banIP processing
[12/22/2025-22:34:44] banIP-1.6.0-r1[14631]: start detached banIP log service (/sbin/logread)
I reenabled wan6 dhcp and now I am getting IPv6-PD.
I am not sure, how it corelates, but I feel I need to report it.
Btw- when changing from eth1 to wan - SQM’s interface name didn’t changed automatically to wan.
Kr
K
The jansson one was a bug in owut now fixed.
The banip (also adblock) is due to a change in packaging, specifically the luci-app-x version numbers now follow the package it wraps rather than the luci releases, and will cause an unavoidable --force for owut users going from 24 -> 25...
@developers This release candidate has been officially announced in this forum thread and on the openwrt-announce mailing list, but not yet on the OpenWrt.org front page. I guess someone forgot?
2 Likes
Hello,
Installed OpenWrt 25.12.0 RC1 on my setup (Raspberry Pi CM5 + Waveshare CM5 Dual Ethernet Mini Board).
The system has been running for almost 2 days now without any issues. Everything works smoothly.
Having the kmod-r8169 driver built into the firmware makes things much easier on this platform.
Big thanks to everyone involved in the development!
Cheers!
1 Like
Successfully upgraded the following:
BTHH5 configured as a VDSL modem/router, was on 24.10.5;
BTHH5, and BPI-R4, both configured as Dumb APs, were on SNAPSHOT.
Many Thanks.
2 Likes
apk invoked without parameters says "This apk has coffee making abilities. For more information: man 8 apk". Probably should be removed because there is no man in default installation. BTW, do we still need /etc/opkg directory if apk is now default package manager?
2 Likes
Nice, unfortunately python3-greenlet and python3-pillow fail to build and are therefore missing for ramips/mt76x8. Any chance of getting that fixed at some point? (also missing in v24)
2 Likes
updated my Xiaomi AX3000T (Global version) from 24.10.4 to 25.12.0-rc1 via firmware upgrade file
Update went smoothly, and I was able to restore all settings from the previous 24.10.4 without any issues by replacing config files via WinSCP.
Thanks to the developers for the release!
2 Likes
Thank you for all the hardwork
succesfully updated ONTi ONT-S508CL-8S aka XikeStor SKS8300-8X
1 Like
I've began looking at that a couple days ago and it appears that the keys stored there are used by non-opkg/non-apk code in certain places. So, yes?
$ grep -r opkg/keys /lib
/lib/apk/db/installed:F:etc/opkg/keys
/lib/apk/packages/attendedsysupgrade-common.list:/etc/opkg/keys/8a11255d14aef6c8
/lib/upgrade/fwtool.sh: ucert -V -m - -c "/tmp/sysupgrade.ucert" -P /etc/opkg/keys
Hi Everyone, can anyone assist with the below , FreeRADIUS is not working on the rc build . I even generated new pem ca and server certificates but the issue persists, Is it the FreeRADIUS package itself that fneeds to be upgraded to work on the rc build?s , the same configuration works when I downgrade back to 24.10.5
1 Like
Upgraded my two Xiaomi AX3600 with Attended Sysupgrade and keep settings.
Now the both wireless are not working.
Systemlog stated: wifi-scripts: log_level: 5 is larger than the maximum value
Looked up the wiki which states log_level only from 0 to 4. So definitly an error in my config. But it seems the 24.10 was more tolerable.
(Don’t ask my why it was in the config in the first place)
It appears twice.
[franco@pc ~]$ ssh root@rt-ax52.lan
root@rt-ax52.lan's password:
BusyBox v1.37.0 (2025-12-17 22:40:38 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 25.12.0-rc1, r32353-9e9b05130c
-----------------------------------------------------
OpenWrt recently switched to the "apk" package manager!
OPKG Command APK Equivalent Description
------------------------------------------------------------------
opkg install <pkg> apk add <pkg> Install a package
opkg remove <pkg> apk del <pkg> Remove a package
opkg upgrade apk upgrade Upgrade all packages
opkg files <pkg> apk info -L <pkg> List package contents
opkg list-installed apk info List installed packages
opkg update apk update Update package lists
opkg search <pkg> apk search <pkg> Search for packages
------------------------------------------------------------------
For more information visit:
https://openwrt.org/docs/guide-user/additional-software/opkg-to-apk-cheatsheet
OpenWrt recently switched to the "apk" package manager!
OPKG Command APK Equivalent Description
------------------------------------------------------------------
opkg install <pkg> apk add <pkg> Install a package
opkg remove <pkg> apk del <pkg> Remove a package
opkg upgrade apk upgrade Upgrade all packages
opkg files <pkg> apk info -L <pkg> List package contents
opkg list-installed apk info List installed packages
opkg update apk update Update package lists
opkg search <pkg> apk search <pkg> Search for packages
------------------------------------------------------------------
For more https://openwrt.org/docs/guide-user/additional-software/opkg-to-apk-cheatsheet
root@rt-ax52:~#
Your /etc/profile is probably modified somehow. Look at
and see if you can simply copy that to your device, or if you need to merge changes from yours into the current one.
With the new profile handling of the profile.d contents, you can suppress showing that message with
touch /etc/profile.d/apk-cheatsheet.hush