From: "Linus Lüssing" <linus.luessing@web.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Roaming issues in basic network
Date: Tue, 1 Jul 2014 10:50:28 +0200 [thread overview]
Message-ID: <20140701085027.GA2341@Linus-Debian> (raw)
In-Reply-To: <CAHxBzxWTprWsPASmNNGXQqj58LRuAHUkNVtXcWHc1PdoD_4+KA@mail.gmail.com>
Hi Simon,
On Mon, Jun 30, 2014 at 07:22:51PM -0700, Simon Wong wrote:
> Let there be 2 wifi clients, client 1 and 2. Initially, both clients
> are wirelessly attached to node A. Client 2 can ping 1 and the nodes.
> Client 2 can also Telnet into node A and B, so all is fine.
>
> I take client 2 and roam to node B. Client 2 can no longer ping client
> 1 and that is the issue.
At the Wireless Battle Mesh a few months ago we've been discussing
just such a (until now?) hypothetical problem. Maybe it applies here,
maybe it doesn't:
It could be a problem with a not yet updated MAC address table in
the bridge, therefore the bridge on node A not forwarding ICMP
requests from client 1 towards client 2.
Questions: Are your clients using IPv4, IPv6 or both? Are your
clients issuing gratuitous ARP replies or ICMPv6 unsolicited
Neighbor Advertisements upon roaming? Is this a permanent problem
or are clients 1 and 2 able to reach each other again after a
while? In your tests, did client 1 ping client 2 or the other way
round?
What you could try to check whether it is a problem with the
learning of the bridge is transforming them to stupid hubs on node
A and node B:
$ brctl setageing br0 0
Cheers, Linus
next prev parent reply other threads:[~2014-07-01 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-01 2:22 [B.A.T.M.A.N.] Roaming issues in basic network Simon Wong
2014-07-01 8:50 ` Linus Lüssing [this message]
2014-07-01 11:26 ` Antonio Quartulli
2014-07-02 1:24 ` Simon Wong
2014-07-02 5:58 ` Antonio Quartulli
2014-07-02 6:22 ` Antonio Quartulli
2014-07-04 7:36 ` Simon Wong
2014-07-04 8:13 ` Antonio Quartulli
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=20140701085027.GA2341@Linus-Debian \
--to=linus.luessing@web.de \
--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