From: liu <liudows@aliyun.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] How to test the non-mesh client roaming feature?
Date: Thu, 21 Aug 2014 15:20:51 +0800 [thread overview]
Message-ID: <53F59DD3.7060703@aliyun.com> (raw)
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.
Best regards
liu
next reply other threads:[~2014-08-21 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 7:20 liu [this message]
2014-08-21 7:28 ` [B.A.T.M.A.N.] How to test the non-mesh client roaming feature? Antonio Quartulli
2014-08-27 12:57 ` Ufo
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=53F59DD3.7060703@aliyun.com \
--to=liudows@aliyun.com \
--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