I’ve found that a lot of clients just don’t roam well, they hang on to even unusable weak signals.
On my Unifi setup I’ve ended up turning on minimum RSSI on the APs so they force kick off any devices with a signal that is too low. You end up with a delay of like 5-10 seconds while the client reconnects, but it does work.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
selfh.st Newsletter and index of selfhosted software and apps
I’ve found that a lot of clients just don’t roam well, they hang on to even unusable weak signals.
On my Unifi setup I’ve ended up turning on minimum RSSI on the APs so they force kick off any devices with a signal that is too low. You end up with a delay of like 5-10 seconds while the client reconnects, but it does work.
This is what I do with my Asus AX mesh setup, running a Merlin fork (gnuton).
This is really smart!
Kicking low-signal devices didn’t occur to me, and should be easy to implement on the OpenWrt one, thanks!
Yeah give it a try, I use -75dBm as my setting. Currently only on the 5ghz band, but you can try on all of them, 2.4ghz might want more like -80dBm.