Amazon Sells Out of Echo Speakers in Midst of Holiday Rush

Re:Amazon Sells Out of Echo Speakers in Midst of Holiday Rush by r1ch on Thursday December 22, 2016 @12:49PM (#13238930)

They have recently introduced centralized AP management called "Capsman" but it's still a little rough around the edges to set up. Their wiki has a lot of good info though, eg http://wiki.mikrotik.com/wiki/Manual:CAPsMAN

Roaming is very tough to get right unfortunately. Only the client devices can make a decision to roam, so without ugly hacks such as using a single channel / MAC / SSID to create a giant interfering WLAN, your options are limited. What you can do with Mikrotik is set up access rules to kick a client off an AP if the signal strength falls below a threshold, but as this is not client-initiated, there is a longer re-association time which could interrupt VoIP etc.

[ Parent | on HN ]

Re:Amazon Sells Out of Echo Speakers in Midst of Holiday Rush by ajford on Thursday December 22, 2016 @01:01PM (#13239029)

So how do you handle roaming in your situation? Do you use different SSIDs between APs? Currently I have the same SSID shared between the two Asus routers (one configured as AP only).

[ Parent | on HN ]

Re:Amazon Sells Out of Echo Speakers in Midst of Holiday Rush by r1ch on Thursday December 22, 2016 @01:55PM (#13239439)

Right now my apartment is small enough that I only need a single AP, I have it wall mounted high up in a central location so it has good coverage of the whole building.

There are options such as 3rd party roaming clients for (eg https://play.google.com/store/apps/details?id=com.heleron.wi... for Android) which I'd consider. For laptops, most drivers have a "roaming aggressiveness" setting which can be tweaked. In general almost all devices should handle transient connectivity glitches fairly well, so kicking low signal clients off an AP shouldn't interrupt too much.

[ Parent | on HN ]