Re: [B.A.T.M.A.N.] How to test the non-mesh client roaming feature?

[Antonio Quartulli <antonio@meshcoding.com>]

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

Liu,

On 21/08/14 09:20, liu wrote:
> Hello, everyone. I want to test the non-mesh client roaming feature. And
> I have connected my notebook to the mesh node A via the access point on
> node A. What should I do next? When the notebook move to the mesh node
> B, should I connect it to the access point on node B manually?How to
> make the non-mesh client move to another mesh node automatically? Thanks.
> 

this behaviour depends on the client OS (each OS implements a different
logic), but in general, if all the APs have the same ESSID, the client
should just switch from one to the other without any user intervention.

The client should switch when the signal from the new AP gets much
better than the old one (at least in principle...then each OS may apply
more robust/smart rules).

Keep in mind that this has nothing to do with batman-adv but is more
about the lower layers (wifi stack/driver) and their implementations.


Cheers,

-- 
Antonio Quartulli


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]