STA+AP on same radio fails on DFS channel 25.12.0-rc1

Installing and Using OpenWrt Network and Wireless Configuration
21

I have just encountered very similar, but with AP plus Mesh on the same radio.
I then tried AP plus STA and AP plus AnotherAP, all with the same results.

I have found that the first virtual interface comes up, but the second, third, etc fail, regardless of the types of interface.

In my case this is a GL-AXT1800.
I had a master/snapshot from somewhere around July/Aug 2025 (I did not take a note of exactly when) and it worked fine.
I reflashed today with shiny-new master/snapshot and the problem shows up.
For reference, here is the output of wifi-chipset-detect:

{
  "System@94:83:c4:5c:25:6d": {
    "Distribution": "OpenWrt",
    "Release": "SNAPSHOT",
    "Revision": "r32947-e3be4654a1",
    "Target": "qualcommax/ipq60xx",
    "Architecture": "aarch64_cortex-a53",
    "Description": "OpenWrt SNAPSHOT r32947-e3be4654a1",
    "Device": "GL.iNet GL-AXT1800",
    "phy": {
      "phy0": {
        "Chipset": "Qualcomm QCN9074",
        "Bands": [
          "5GHz"
        ],
        "Standards": [
          "802.11ac",
          "802.11ax",
          "802.11n"
        ],
        "MeshPoint": "802.11s",
        "Wi-FiGeneration": "Wi-Fi 6",
        "MIMO": "2x2",
        "MaxChannelWidth": "160 MHz",
        "ChannelWidthCap": false,
        "Antennas": "2x2",
        "TheoreticalMaxMbps": "2400",
        "TXQS": true,
        "AIRTIME_FAIRNESS": false,
        "AQL_Extended": false,
        "AQL_Runtime": true,
        "Driver": "ath11k"
      },
      "phy1": {
        "Chipset": "Qualcomm QCN9074",
        "Bands": [
          "2.4GHz"
        ],
        "Standards": [
          "802.11ax",
          "802.11n"
        ],
        "MeshPoint": "802.11s",
        "Wi-FiGeneration": "Wi-Fi 6",
        "MIMO": "2x2",
        "MaxChannelWidth": "40 MHz",
        "ChannelWidthCap": false,
        "Antennas": "2x2",
        "TheoreticalMaxMbps": "600",
        "TXQS": true,
        "AIRTIME_FAIRNESS": false,
        "AQL_Extended": false,
        "AQL_Runtime": true,
        "Driver": "ath11k"
      }
    }
  }
}

I have the meshnode working with the workaround of limiting to a single VI per radio.

I do know that the old working master/snapshot predated the change to ucode wifi-scripts.

Could this be the problem here?

Ref:

22

@lleachii

A log snippet - or is it a smoking gun?

Fri Feb  6 21:07:54 2026 daemon.notice netifd: radio1 (18048): wifi-scripts: Starting
Fri Feb  6 21:07:55 2026 daemon.notice netifd: radio1 (18048): command failed: Not supported (-95)
Fri Feb  6 21:07:55 2026 daemon.notice netifd: radio1 (18048): command failed: Not supported (-95)

I was trying to start mesh, ap1 and ap2 on radio1. (this was fine on the old master/snapshot from last summer).

23

Yes, SNAPSHOT works.

OpenWrt SNAPSHOT r32968-50e7e5c80d / LuCI Master 26.037.46796~e6ad9db

I think another use had that in thier logs, not me (as I recall).

24

Unfortunately it doesn't work for me. But then my device in question is ath11k so maybe some drivers are fixed and some not, which implies some sort of compatibility/interaction somewhere.

25

I have come across some possibly related recent commits:

2 Likes
26

@lleachii I've finally gotten around to bisecting my issue, see

for the detailed bugreport.

While I'm not sure if my issue is the same as yours, it would probably make sense to test/ bisect it similarly.

1 Like
27

Still broken in 25.12.0-rc5. SNAPSHOT works.

28

25.12.0 with AP+STA+DFS works on Netgear WA202.

1 Like
29

Spoke too soon. After some uptime, DAWN tries to move the phone to the new (more appropriate) AP, but this only results in a disconnection. The log is flooded with:

daemon.notice: hostapd: handle_probe_req: send failed

SNAPSHOT works.