Thu Feb 15, 2018 4:45 pm
Not knowing of 802.11r until yesterday, I have tried co-channel, same SSID & different channel SSID. Both attempts resulted in VoIP disconnect when moving from one AP coverage to another. My test mobile device is a Pixel-XL on undated and current firmware and Android OS, part of ProjectFi. If that pocket device is not ready to do roaming, what would be? It is supposed be a wifi enabled telephone, and it has a conventional telephone number and can do SMS. My test APP is Zoiper.
As a radio person I know I can set up this way: The same channel, SSID, and MAC address. Signals will interfere, but VoIP does not use much transmission capacity. As my APs have pretty nice coverage without too much overlap, it may work. If the radio frequency were in sync, and the encryption code in sync, interfering signals would look just like bounces off walls. If the speed is locked down to the lowest rate possible, that being 1 mb/s, then signal would be very robust against interference. (SEE Shanon's law). So I will try this. The problem is that if I do this, use of the signal for purposes requiring higher data rates will suffer and the scheme would fail in large places like schools and airports.
For better results I could turn off encryption, removing encryption sync as a problem. So I intend to try that, and use MAC access control. Then maybe run a second SSID overlay.
Mikrotik: Get with it. You are so good. 802.11r cannot be beyond your capacity. We should march forward to the future. Not back to a slow past.
I will try my home experiment. I will report back.
P.S. Maybe I should use my time trying to get my SDR up and running with an LTE signal on an empty cell channel, with just enough power to cover this property. And not waste it with this stuff of the past. Argh.