From: Antonio Quartulli <antonio@meshcoding.com>
To: locborgtus@gmail.com, "Linus Lüssing" <linus.luessing@web.de>
Cc: 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, 01 Jul 2014 13:26:55 +0200 [thread overview]
Message-ID: <53B29AFF.2070405@meshcoding.com> (raw)
In-Reply-To: <20140701085027.GA2341@Linus-Debian>
[-- Attachment #1: Type: text/plain, Size: 1412 bytes --]
On 01/07/14 10:50, Linus Lüssing wrote:
> 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.
>
Hey Linus,
I agree that the problem is probably in the bridge, but how can it be an
inconsistency in the table given that the bridge is receiving the Echo
requests from client 2 through bat0?
Shouldn't this immediately update the bridge table to reflect the client
movement (client2 --is-behind--> bat0)?
@Simon: are you sure that the client is not associated anymore with node
A at that moment (maybe it was jumping here and there)? You said that
you can fix situation this by deleting the station entry, but is this
station entry obsolete at that point? (meaning: is the inactivity time
high? - you can see this through the "iw dev wlan0 station get <client2
mac>" command before deleting it)
If not, it can be that something wrong is happening at the wifi layer
and given the driver you are using (ath5k) it would not be totally
unexpected.
I am asking this because I expect the station to disappear immediately
in case of roaming (the client usually deauthenticates itself before
associating with the new AP). Still, we can have cases when this does
not happen, but the AP should be able to react properly.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-07-01 11:26 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
2014-07-01 11:26 ` Antonio Quartulli [this message]
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=53B29AFF.2070405@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=linus.luessing@web.de \
--cc=locborgtus@gmail.com \
/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