OpenWrt 25.12.0-rc5 - Release Candidate

Release and security announcements
171

It was to Optional. I tried Disabled but still it wont connect.

172

My magic 8-ball says soon.

11 Likes
173

I'm hoping the STA+AP fixes are included in 25.12.0.

3 Likes
174

https://downloads.openwrt.org/releases/25.12.0/targets/ - 1-2-3-Run!

2 Likes
175

There are a few.

and yes, ap+sta is included.

4 Likes
176

I have an MR8300 and the qca4019 and qca9888 non-CT drivers are now marked version 20251125-r1 which presumably means they are a relatively new release.

Anyone have any information on what may be new or changed?

177

Why hasn't the OpenWrt firmware selector been added yet, and 25.12.0 been officially released yet?

178

Why hasn't the OpenWrt firmware selector been added yet, and 25.12.0 been officially released yet?

Because after a release has been tagged, it still needs to be built for all devices, and what has been built needs to at least be looked over and cursorily tested.
That takes a while.

See also:

7 Likes
179

Curiosity killed the cat, but 25.12.0 seems to be running fine on my NanoPi R3S with some packages installed :slight_smile:

1 Like
180

This is an issue I just noticed today: Watchcat is not recognizing ping responses if the ping transverses through a mesh network. Using the diagnostic tool on the same router, ping responses are coming in normally. When Watchcat pings the same address, Watchcat sees no response. This issue was not present with 25.10.X.

Diagnostic Ping:
64 bytes from 192.168.1.12: seq=2 ttl=64 time=1.353 ms

Watchcat Ping:
watchcat[4123]: Could not reach 192.168.1.12 for 1500. Rebooting after reaching 3600

181

Have you set the correct interface in watchcat?

182

Netgear R7800 running as main router with Adblock, https-dns-proxy, DDNS and watchcat.
Upgrade from 24.10 snapshot to 25.12 snapshot of yesterday (=25.12.0)
Phones, tablets, smart TV and IoT stuff and wired PC's
Running fine, excellent wireless range and speed comparable to 24.10.

1 Like
183

Aww bless :slight_smile:

I’ll wait for the official announcement, mostly hyped for the AP+STA fixes. I think I installed the wrong version that’s been running (mostly) fine, but had the AP on the STA radio crash once. Hopefully that was just me being dumb and not following proper instructions though (I installed the snapshot via the firmware builder instead of the 25.12-snapshot branch - thought the two were the same), so I’m hoping the snapshot version I installed didn’t actually have the aforementioned fix included :smiley:

There’s also MLO, but I had my hopes and dreams shattered the other day in regards to that as well, so if it just runs stable as-is, I’ll be one happy camper.

Thanks for the good news! :slight_smile:

1 Like
184

Thanks to all devs for the grate work!

I am running 25.12-rc5 on all my devices without issues, except for the luci-app-lldpd package:
Luci just states “Collecting data...” on Discovered Neighbors status page (also for Interface Statistics), while lldpcli show neighbors on the cli shows the correct info as expected, so lldp in general is working.
I had running rc3 before and there it still worked in Luci if I recall it correctly.

185

Thanks for the report @fireburner - fix pushed in luci repo, also to 25.12.

3 Likes
186

@systemcrash can you also push the newer mt76 driver set https://github.com/openwrt/openwrt/pull/22007/commits so they are in 25.12.1?

Some good wifi fixes in there especially for sync station power save state. TIA.

5 Likes
187

It’s in main already IIUC, so that needs a pick to 25.12 which will happen a bit further down the road once those changes have had a chance to shake out any regressions.

2 Likes
188

Upgraded Zyxel T-56 into 25.12 stable with ASU, everything went fine

only i needed rename eth1 —> wan but that is expected

root@OpenWrt:~# ubus call system board
{
        "kernel": "6.12.71",
        "hostname": "OpenWrt",
        "system": "ARMv8 Processor rev 4",
        "model": "Zyxel EX5601-T0 ubootmod",
        "board_name": "zyxel,ex5601-t0-ubootmod",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "25.12.0",
                "firmware_url": "https://downloads.openwrt.org/",
                "revision": "r32713-f919e7899d",
                "target": "mediatek/filogic",
                "description": "OpenWrt 25.12.0 r32713-f919e7899d",
                "builddate": "1772496855"
        }
}
189

Is there some logic that can / will be built into future firmware updates to automatically rename interfaces when there are changes like this? I am guessing that this is only an issue when there is an upgrade to a device retaining previous settings, but would not happen on a fresh install?

190

So in the absence of an official release thread I’ll comment here that I just upgraded my devices via ASU:

  • Linksys WRT3200ACM: 24.10.5 → 25.12.0
  • D-Link DIR-825 B2: 24.10.5 → 25.12.0
  • ZyXEL NWA50AX Pro: 25.12.0-rc5 → 25.12.0

Can’t immediately spot any issues, logs seem clean to me on all three devices.

Thank you devs & everyone else making this possible, again!

2 Likes