From: Ufo <ufo@rund.freifunk.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] How to test the non-mesh client roaming feature?
Date: Wed, 27 Aug 2014 14:57:52 +0200 [thread overview]
Message-ID: <53FDD5D0.4030302@rund.freifunk.net> (raw)
In-Reply-To: <53F59FA7.2040205@meshcoding.com>
Am 21.08.14 09:28, schrieb Antonio Quartulli:
> Liu,
>
> On 21/08/14 09:20, liu wrote:
>> Hello, everyone. I want to test the non-mesh client roaming feature.
> 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.
>
so practically within wifi-field i prefer two ways for testing:
* via wifi-client (Android Smartphone)
The nicest App i found is
https://play.google.com/store/apps/details?id=com.arubanetworks.arubautilities
there you can see the ping to your default gateway and all your APs.
That one you are connected to is marked, the client-switching too..
https://twitter.com/rundfreifunk/status/504611193324326912
* on your mesh-node, best used on your local dhcp-server (openwrt with
batman-adv)
-> cat /tmp/dhcp.leases; arp -a
get the mac-adress or ip-adress of your test-client (the smartphone) and
open two ssh windows:
-> ping <ip-adress>
-> batctl -m bat12 tr <that-adress>
that shows the batman-adv route to your client and all the actually
involved batman-nodes. unfortunatly that traceroute is only to the last
batman-node (that one, your smartphone is connected to) and NOT up to
your client. so maybe that batman-traceroute is working, but the ping
wont. and last but not least, dont get confused with all of these
mac-adresses!
https://twitter.com/rundfreifunk/status/429992988602032129
good luck and greetings
ufo
--
---
Freifunk Leipzig http://leipzig.freifunk.net
prev parent reply other threads:[~2014-08-27 12:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 7:20 [B.A.T.M.A.N.] How to test the non-mesh client roaming feature? liu
2014-08-21 7:28 ` Antonio Quartulli
2014-08-27 12:57 ` Ufo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53FDD5D0.4030302@rund.freifunk.net \
--to=ufo@rund.freifunk.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox