Could some check my steps I have done to set dawn up?
Maybe someone will also be confused by those two different instructions in wiki and github readme.
Or someone from the wiki and github can add missing steps.
Set up two Wireless Networks with same SSID and same Password. One in 5GHz and one in 2,4 GHz radio.
Changed option broadcast_ip the ip to my subnets IP (#change1) and option duration from 0 toi 100 (#change2)
and deleted all 'config metric' and 'config times' sections (#deleted).
New dawn config:
You mean in config metric 'global'?
That is original. Ok, I will change my configuration (and my post) to option duration '100'
Thank you! Anything else?
Another Question. What about option time_zone 'GMT0'
in WiFi Config? Must I change this to the TimeZone of my Router (which I have left on UTC as default) or to my Smartphone Device (Which is GMT+1)?
I removed the ht_support/vht_support from 5 to 0 because that is currently broken between access points
I lowered the 2.4Ghz band starting score to 10, because I want the 5Ghz to be highly preferred
I set the rssi additional score of 15 to 0 so that it would not give the 2.4Ghz band an extra boost in score
I set the rssi weight to 4, so only an rssi difference of 5 will cause a move
That combined with bandwidth_threshold '200', set_hostapd_nr '2', min_number_to_kick '2', kicking '1' under global settings.
For the first time ever, OpenWRT roams all my devices at the drop of a hat! Occasionally I'll find after a device roams around 4 or 5 times, it will stop roaming for a few minutes.
It might also be worth noting that if you are using layer 2 security, such as DAI/DHCP snooping (dynamic arp inspection), you will have to disable 802.11r or it will roam and then not be able to communicate. I'm using DAWN with WiFi routers hooked to an active directory radius server on the backend with dynamic VLAN tagging, and it is working!
You are amazing. Tried you configuation and it works instantly! Why are the instructions mentioning to remove just the metrics part? It feels now stupid that I removed it, but the both different instruction are very confusing.
One more question, what do you mean by
How can that be broken? Should I keep it to 5? This is my actual dawn configuration:
i have scoured this thread and have condensed the suggestions to the following uci commands:
uci set dawn.@network[0].broadcast_ip='192.168.1.255' # modify for your wlan subnet
uci set dawn.802_11g.initial_score='10'
uci set dawn.802_11g.rssi_weight='4'
uci set dawn.802_11g.ht_support='0'
uci set dawn.802_11g.rssi='0'
uci set dawn.global.bandwidth_threshold='200'
uci set dawn.global.set_hostapd_nr='2'
uci set dawn.global.kicking='1'
uci set dawn.global.min_number_to_kick='2'
uci set dawn.global.duration='100'
uci commit dawn
/etc/init.d/dawn restart
please correct and amend these commands if i have misrepresented.
thx
Fast Roaming with DAWN is working very well here across 3 AX6S dumb APs and an AX3600 router all running snapshot - with log showing FT for devices that support it (Apple household).
Given the number of APs, I'ver chosen to go more agressive with my DAWN settings.
In addition, I found that it's important to:
Drop the signal strength at each AP as much as possible to help the devices choose to roam
Turn off 2.4ghz on most APs except at the 2 furthest points. I did this to help devices choose to get on the 5.4ghz band instead of 2.4ghz which has longer range.
Each setup is different, so have to play with signal strength, rssi values in the DAWN config that best suits your case/needs.
Also, I have option mbo '1' set on my wifi-ifaces (multiple RT3200 'dumb APs'). I can't remember exactly where I read about enabling it, but the description of it is here: What exactly is MBO for?
Ah! Interesting about mbo…. Will read a bit and likely add that.
In terms of dtim, although most devices are apple, I have a few iot devices. If I recall correctly back when I was running an r7000 on tomato, a couple of the cheap iot devices started acting weird when I raised dtim…
It’s been a while so my memory is foggy on that…. Might try it again.
Great point, though I can say confidently I have multiple IoT devices as well and haven’t considered the dtim interval with them to-date. Everything has been running smoothly here. But definitely a YMMV situation, no doubt.
Hello,
I just setup Dawn and followed all the recommended changes to the config file.
I do seem to have a problem with Android devices that are in sleep mode. They are connected to the AP and show in the list of connected devices, however I do get these messages in the log every 5 seconds for each Android device:
Thu Mar 2 22:12:44 2023 daemon.notice hostapd: Beacon request: xx:xx:xx:xx:xx:xx is not connected
Thu Mar 2 22:12:44 2023 daemon.warn dawn: Client / BSSID = xx:xx:xx:xx:xx:xx / yy:yy:yy:yy:yy:yy: BEACON REQUEST failed
Any idea what's going on? I suspect the kicks are not actually sent because hostapd thinks the STA is not authenticated/connected for some reason.
This is on the latest stable with wpad-wolfssl.
Thanks!
My logs are also flooded with this and from what I gathered, this might not be directly related to DAWN but seems to be a bug in the cfg80211 kernel module (driver) related to 802.11r. Some forum threads suggest that it's a regression that happened after OpenWRT 19. Unfortunately, I can't downgrade to verify because my devices (TOTOLINK X5000R) only got support since OpenWRT 21. There's a patch online (not upstream, unfortunately) and rumor has it that it could mitigate the bug.
At least, that's my initial impression, at least. I've been googling so much that I don't remember how I came up with the connection to that forum thread, though. Maybe somebody like @PolynomialDivision would be able to give better pointers...
I've not really confirmed if this is related to Dawn or 802.11k/v in general, but after some time my (Android) devices just "supposedly" lose internet connectivity. They drop off of WiFi, and attempting to reconnect seems to throw "Connected, no internet access" and then they drop again.
What's odd is that in the short amount of time they are connected, they are able to be pinged, and also themselves seem to be able to ping (and use DNS) addresses.
I'm currently re-trying with 802.11k/v and Dawn disabled. There's nothing obvious in logs. Devices are the Xiaomi R3G and Redmi 2100, so both ramips/mt7621
I'm running self-compiled Snapshots from the same git HEAD on both devices.
I haven't seen anything super obvious on either my OpenWrt devices, nor my Android logs. Just basic auth, DHCP and then disassociation after a few seconds. Only restarting seems to reliably make it work for a bit again
I've been seeing something that feels similar. TOTOLINK X5000R also has ramips/mt7621. One example was an iPad that seemed to have stopped getting the packets through WiFi while still showing it as connected on the device. Also, some DNS-related queries seem to be stuck+timeout from time to time. I wasn't able to track this down. It is happening on 21.03 and I think on 22.03 too.
One of my issues was that the mt76 upstream sets the same mac address for the 5G radio: https://github.com/openwrt/openwrt/issues/8861. This is bad since I had 3 identical APs that advertised 5G network with the same BSSID — according to my googling, this usually causes a lot of problem with AP confusion where one AP authenticates an STA but others send deauth since they also hear traffic addressed to the same BSSID. It was an interesting experience since 2.4G radios with the same SSID have different BSSID, as they should. So I applied https://github.com/openwrt/openwrt/pull/4738 for now, as a workaround.
Still, I'm seeing the bug I described in the previous post too.
Note that I've tried the lastest OpenWRT snapshots while debugging my issues and WiFi seemed much less stable but I haven't checked why.
The logs I've seen don't reveal if the problems I'm seeing are DAWN-related on lower level too...