From: Antonio Quartulli <ordex@autistici.org>
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.] ap_isolation issue
Date: Fri, 27 Jan 2012 14:36:08 +0100 [thread overview]
Message-ID: <20120127133529.GA7367@ritirata.org> (raw)
In-Reply-To: <4210BF92-C0BC-4862-9711-6F8214494082@net-forces.com>
Hello Andre,
On Thu, Jan 26, 2012 at 04:46:44 -0500, Andre Courchesne wrote:
> Ok, did a bit of tcpdump and my test was the following:
[cut]
>
>
Thank you for reporting this issue and sending us the dumps.
Actually it is very hard to link the ap isolation mechanism to this problem.
First of all I would like to make a simple test. Please, could you use dump
packets received on T003 and see if the ARP request (the first one that receives no reply)
reaches the node (T003)?
In particular I would
suggest you to use wireshark (it can parse batman packets) and to sniff at the
same time packets either from the physical interface used by the mesh (I'd say wlan0)
and bat0.
Then tell us if you see the ARP request on both interfaces, on wlan0 only or on none
of them.
Another question, why are you using the bridge loop avoidance? If possible I
would like you to disable any optional feature you have in order to have the
cleanest testbed possible. I know that you already tried to disable it without
effect, but it is better to perform test without any other "noise".
Cheers,
--
Antonio Quartulli
..each of us alone is worth nothing..
Ernesto "Che" Guevara
next prev parent reply other threads:[~2012-01-27 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 17:27 [B.A.T.M.A.N.] ap_isolation issue Andre Courchesne
2012-01-26 19:13 ` Marek Lindner
2012-01-26 19:44 ` Andre Courchesne
2012-01-26 20:39 ` Andre Courchesne
2012-01-26 20:45 ` Marek Lindner
2012-01-26 21:46 ` Andre Courchesne
2012-01-27 13:36 ` Antonio Quartulli [this message]
2012-01-27 14:30 ` Andre Courchesne
2012-01-27 14:45 ` Antonio Quartulli
2012-01-31 21:37 ` Andre Courchesne
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=20120127133529.GA7367@ritirata.org \
--to=ordex@autistici.org \
--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