On 2nd thought, Im actually guessing that it may be just a counter showing how many roams happened from or to the AP where you are looking at the overview. If i add up 2.4 and 5GHz then it more or less matches from my one AP to my other AP. I guess also the reason why they are all zero for "This AP".
Then band steering should be shown at least in my opinion. As roaming between the hostap threads. Does somebody see any roams on this AP?
I agree, it should then also show roaming from band to band, but apparently it does not
usteer has some serious bugs in its core functionality that will definitely prevent the actual roaming from happening. I tried sending patches like https://lists.openwrt.org/pipermail/openwrt-devel/2024-May/042785.html, but they haven't been picked up at all.
Until these obvious bugs in core logic are fixed I wouldn't bother spending any time setting it up.
Really depends of what you expect.
For me, usteer works good (better than DAWN or without any of that services).
I will share my config:
config usteer
option network 'lan'
option syslog '1'
option local_mode '0'
option ipv6 '0'
option debug_level '2'
option roam_scan_snr '-70'
option roam_trigger_snr '-75'
option min_snr '-85'
option roam_scan_tries '0'
option max_neighbor_reports '6'
How do you measure that it works?
By walking around the apartment and at least looking to see if wificalling/pings interrupts.
1 Like
I doubt that's the doing of usteer.
Does a roam request appear in the log to check if it is send? Can see BSS-TM-RESP messages and from reading through all the post and this is mentioned everytime.
I don't know why but after using usteer for a long time, now it seems to not start correctly. I've two nodes, one working perfectly, but the other seems to not start:
root@router-comedor:/etc/config# ubus call usteer local_info
{
}
As you can see, the local_info command does not show anything. The other one works perfectly and shows this information.
Some idea of what has broken this?
The logread does not show any error.
I answer myself... it seems some kind of bug in the openwrt snapshot of two weeks ago. Updated to latest snapshot of openwrt and seems to be fixed... the strange is that it only affected one of the two nodes.
Where to report bugs...is this the correct location as nobody answered: Issues · openwrt/usteer (github.com)
1 Like
Yes, it seems the correct location, but nobody seems to care about it.
3 Likes
I don't know since when, but it seems something is broken in current master about roaming... the devices didn't roam with fast transition, like they did before.
Someone here has noted the same?
Answer to myself: it seems something were wrong with usteer. The ubus call usteer local_info command didn't show the rrm_nr block, so without this info, it was not able to make any device roam with fast transition.
Why this part was missing? Who knows, a restart of the usteer service fixed the issue. I suppose some kind of bug.
I did not spotted such issue. In main/master branch, only that can affect is updated hostapd to newer version.
When I was testing that change - everything was working normally. Could you share your config?
I can, but the issue is not reproducible, it only happens from time to time.
What config file do you need?