OpenWrt 24.10.5 - Service Release

It appears that DAWN is functioning and communicating .-.

The problem is that it's not displaying any data in the Luci interface.

root@OpenWrt:~# ps | grep dawn
12520 root 3556 S /usr/sbin/dawn
12966 root 1328 S grep dawn
root@OpenWrt:~# ubus call dawn get_network
{
{
"AA:AA:AA:AA:AA:01": {
"channel": 6,
"freq": 2437,
"channel_utilization": 43,
"num_sta": 4,
"ht_support": true,
"vht_support": false,
"op_class": 81,
"local": true,
"neighbor_report": "REDACTED_HEX_STRING",
"iface": "phy0-ap0",
"hostname": "ROUTER_PRINCIPAL",
"CC:CC:CC:CC:CC:01": {
"ht": true,
"vht": false,
"rrm-caps": "........",
"signal": -76,
"rcpi": -1,
"rsni": -1
},
"CC:CC:CC:CC:CC:02": {
"ht": true,
"vht": false,
"rrm-caps": "........",
"signal": -65,
"rcpi": -1,
"rsni": -1
},
"CC:CC:CC:CC:CC:03": {
"ht": true,
"vht": false,
"rrm-caps": "........",
"signal": -81,
"rcpi": -1,
"rsni": -1
},
"CC:CC:CC:CC:CC:04": {
"ht": true,
"vht": false,
"rrm-caps": "........",
"signal": -52,
"rcpi": -1,
"rsni": -1
}
},
"AA:AA:AA:AA:AA:02": {
"channel": 36,
"freq": 5180,
"channel_utilization": 12,
"num_sta": 2,
"ht_support": true,
"vht_support": true,
"op_class": 128,
"local": true,
"neighbor_report": "REDACTED_HEX_STRING",
"iface": "phy1-ap0",
"hostname": "ROUTER_PRINCIPAL",
"CC:CC:CC:CC:CC:05": {
"signature": "wifi4|probe:REDACTED|assoc:REDACTED",
"ht": true,
"vht": true,
"rrm-caps": ".TAP..NL",
"signal": -68,
"rcpi": -1,
"rsni": -1
},
"CC:CC:CC:CC:CC:06": {
"signature": "wifi4|probe:REDACTED|assoc:

No it isn't, unless you're doing band steering between the 2.4ghz and 5ghz on “ROUTER_PRINCIPAL" , your ubus call dawn show_network should show you all the routers that have dawn running no matter which router you run that command on. Yes dawn will " appear” to be running but it's not connected to another instance nor is it doing any steering for you. If you had to adjust your power levels on your access points to get your devices to roam then your devices are making their decision without any influence. I have all my radios on full power and my devices don't stick and thanks to the settings I have I can be sure that they are connected to the optimal access point. For reference I get a score of A/A+ on waveform's bufferbloat test on wifi anywhere in my three story townhouse. "no related RPC reply” means dawn has crashed due to most likely not being able to parse your /etc/config/dawn file. Run “uci show dawn" and show the result.

Check if you have anything like this in the logs:

Wed Dec 31 16:30:56 2025 daemon.notice hostapd: handle_probe_req: send failed

I solved the problem by adding the code below to the router's initialization.

I believe they will fix this in future versions.

Everyone was affected.

sleep 3
sed '/^ssid2="([^"])"/{h;s//&\nssid=\1/}' /var/run/hostapd-phy0.conf -i
sed '/^ssid2="([^"]
)"/{h;s//&\nssid=\1/}' /var/run/hostapd-phy1.conf -i
/etc/init.d/dawn restart

CAME HERE TO SAY THIS! I encountered the same problem after changing some wifi settings over the new year. I don’t know what fix they are implementing but it’s definitely a problem with dawn, according to the official hostapd conf info found here: https://web.mit.edu/freebsd/head/contrib/wpa/hostapd/hostapd.conf?ref=dzombak.com

hostapd can use ssid=yourwifiname without quotes to define your wifi ssid, or it can use ssid2=”yourwifiname” to define your wifi ssid in /var/run/hostapd directory that dawn uses to get neighbour reports from, but dawn crashes all instances when it encounters ssid2 on just one.

I went a little further and added a script in /etc/hotplug.d/iface/99-dawn-ssid-fix like this:

if [ "$ACTION" = "ifup" ] || [ "$ACTION" = "setup" ]; then
  sleep 3
  sed -i 's/^ssid2="\([^"]*\)"/ssid=\1/' /var/run/hostapd-phy*.conf
  /etc/init.d/dawn restart
fi

I figure since in the official hostapd documentation it says that either ssid2 or ssid can be used, I just replace ssid2 with ssid whenever I make changes to wifi settings or on boot. It doesn’t seem to break anything. But the dawn developer should update dawn to handle both ssid2 and ssid correctly so that it doesn’t crash. I thought I found some magic solution to getting dawn working with the server ip thing, but I was just lucky that both my routers’ hostapd daemon happened to use ssid= and not ssid2= and it worked so well for days, and then I go to change a channel and bam it stopped. I reflashed, re-configured, and reset everything back to the way it was and nothing, what a nightmare hahahaha. Then googling around led me to the same github post as you, I think, found here: https://github.com/openwrt/luci/issues/7974#issuecomment-3694252512

BTW I’m using configuration settings found on this reddit post: https://www.reddit.com/r/openwrt/comments/15y9sqs/dawn_the_bss_transition_controller_and_tips_on/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

those work really well because it rapidly affects the score of the access point you’re connected to compared to a neighbour you’re getting closer to, for me that means that within about 30 seconds of moving from upstairs bedroom to the living room my phone will switch to the living room router and within 10 secs be gone from the report of the upstairs one. This makes sure that if I happen to go down to get something quickly and come back up I don’t needlessly disconnect and reconnect multiple times.

Although I’m still not sure what caused this but I promoted one of the other devices to gateway with roughly the same configuration and it has been running fine for a few days now.

Bananapi BPI-R4 4GB
No issues upgrading from 24.10.4 using the attended sysupgrade. I had to exclude luci-nginx and my installed themes but that’s pretty much it. I reinstalled them after and no problems.

I seem to have more radio issues after the upgrade. TP-Link Archer C7 V2.

I see some logs like:
”ath10k_pci 0000:00:00.0: WARNING: failed to wait for beacon tx callback for vdev X”
”daemon.notice hostapd: nl80211: Failed to remove interface phy0-ap1 from bridge br-lan: No such device”

Summary: 2 routers working on 23.05.6 upgraded to 24.10.4 - with 24.10 each router uses the same 2.4 and 5g radio channels.

I'll add my experience upgrading a netgear 6700 and archer A7 - retained working configurations from 23.05 - both routers in one location, maybe 2m apart. Wireless channel config options both set to ‘auto’, country to ‘US’. These routers and configurations worked well for some time and I thought I'd try 24.10

The overall problem was both routers were using the same 2.4g and 5g channels, some clients would see one router or another; one client would get maybe 1mbit bandwidth - and I noticed because thru-put had worsened.

There is no competition from outside routers. Luci used for all config changes - and I tried explicitly assigning 1 channel and then reset to auto in case my wireless config was glumped.

Many router reboots, radio resets tried … both routers reliably grabbed ch1 and ch30. Were channel numbers hard-coded somewhere for test !? Doubt it, but that's how they behaved. All good on reversion to 23.05.

Mmmv.

Could you send me your Wavlink WL-WN572HG3 (manually compiled) file? Thank you.

1 Like

Hi @Netofera! Welcome to Openwrt Forum!
Here you can find all the files that need to be modified in order to get the image compiled correctly:

https://github.com/openwrt/openwrt/pull/15179/files

This way you are independent and can proceed with the compilation independently. To proceed with the compilation, follow this guide:

https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem

If you prefer I can send you the initramfs and sysupgrade files directly to the cloud but you have to wait, because I'm currently working, I don't have the firmwares with me...

I thank @ianchi again for his work, without him it would not have been possible to have OpenWrt on the Wavlink WL-WN572HG3 device

1 Like

Please send the initramfs and sysupgrade files; that would help me a lot. Thank you.

1 Like

@Netofera
I sent you a PM with the link

1 Like