Earlier quoted context omitted.
For Omada devices, you need a "Controller". You can run the Omada Controller software on an existing computer, get one of their controller devices, or use their cloud-based service, which should be free at your scale.
The Omada device* I researched also supports standalone mode and hosts the web UI like any other consumer router. * https://www.omadanetworks.com/us/business-networking/omada-r...
Indoor Wi-Fi Roaming with OpenWRT
21–30 of 130 posts
Re: Indoor Wi-Fi Roaming with OpenWRT
#22Earlier quoted context omitted.
To be fair, I don't require my 85" TV to roam, as it's not as portable as my iPhone.
Until it gets stuck on a far away AP because it was the first AP to come online the last time the network rebooted. Not sure if roaming is actually the fix for this problem. For whatever reason my Ring cameras just love connecting to the worst and most far away AP in my house.
I had to solve a similar issue for some crap IoT lights that would join the incorrect AP after a power cut every time.
> https://community.ui.com/questions/Lock-Client-to-Specific-A...
Re: Indoor Wi-Fi Roaming with OpenWRT
#23Earlier quoted context omitted.
I run a single ssid dual band network ... what tends to happen is 5Ghz is effectively ignored. 2.4Ghz has better coverage, so everything wants to live there. At least wifi 6 brought improved encoding to 2.4Ghz. I haven't had luck with the roaming extensions; when I run them, some of my devices won't connect or won't stay connected and it's a pain to monitor. I guess I could run a different SSID with roaming enhanceme…
You can turn down the power on the 2.4GHz radio so it's not as overpowering.
Re: Indoor Wi-Fi Roaming with OpenWRT
#24You can stick to 802.11r only by lowering the transmission power and have all the APs on the same channel, in my tests it ended up switching much faster than K/V. (~75ms) On iOS, equal channel with correct ESS will switch liberally. On Android 14+ with Broadcom chip it will start conservative, then switch liberally after the first poor signal switch-over event, up until disconnection. Android (Pixel/Moto) will never…
With 802.11r on, things would disconnect for 60+ seconds before reconnecting. It was a constant frustration of "arrrrrrrggghhhh fucking connect damnit I'm standing a meter in front of the AP can't you fucking see it fuck fuck fuck just connect, it's right THERE, connect NOW, arghhh" and then it would completely disconnect (no wifi found) and then reconnect a minute later.
With 802.11r off things just roam smoothly. I guess the people who inventned the tech didn't test it thoroughly enough.
Re: Indoor Wi-Fi Roaming with OpenWRT
#25You can stick to 802.11r only by lowering the transmission power and have all the APs on the same channel, in my tests it ended up switching much faster than K/V. (~75ms) On iOS, equal channel with correct ESS will switch liberally. On Android 14+ with Broadcom chip it will start conservative, then switch liberally after the first poor signal switch-over event, up until disconnection. Android (Pixel/Moto) will never…
Re: Indoor Wi-Fi Roaming with OpenWRT
#26I don't quite understand the benefit of the setup. If there are legacy IoT devices that need unique named 2.4G network, just broadcast another SSID for them. So each router broadcasts main 5G (common name, fast roam etc), main 2.4G (same as above) and legacy IoT 2.4G (with a different name for each AP, and possibly worse encryption and maybe even TKIP). That wouldn't hold back the network for legacy devices.
Re: Indoor Wi-Fi Roaming with OpenWRT
#27> The obvious advice for roaming is “use one SSID everywhere”, and that is often correct if you’re running Wi-Fi in an office, a public venue, or generally somewhere where you don’t have (or care about) legacy devices. What difference does the presence of legacy devices make? Is the intent to isolate them from modern devices from a network perspective? Then create a separate SSID on both 2.4 and 5 GHz for modern devi…
Re: Indoor Wi-Fi Roaming with OpenWRT
#28> The obvious advice for roaming is “use one SSID everywhere”, and that is often correct if you’re running Wi-Fi in an office, a public venue, or generally somewhere where you don’t have (or care about) legacy devices. What difference does the presence of legacy devices make? Is the intent to isolate them from modern devices from a network perspective? Then create a separate SSID on both 2.4 and 5 GHz for modern devi…
There is zero benefit to using 2.4 for me, really, since it's crowded as heck. I'd rather skip it altogether.
Re: Indoor Wi-Fi Roaming with OpenWRT
#29Earlier quoted context omitted.
There is zero benefit to using 2.4 for me, really, since it's crowded as heck. I'd rather skip it altogether.
If you don't need it, of course, you might as well deactivate it. But if you do, I don't see the point of having two different SSIDs if you don't need them for another reason anyway.
Re: Indoor Wi-Fi Roaming with OpenWRT
#30You can also "just" set the 802.11k entries manually. Add 802.11r and you should be mostly good. Usteer makes it slightly better by moving clients to the best AP when they stay stationary for longer whiles.