From: Marek Lindner <lindner_marek@yahoo.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.] ap_isolation issue
Date: Fri, 27 Jan 2012 04:45:49 +0800 [thread overview]
Message-ID: <201201270445.50388.lindner_marek@yahoo.de> (raw)
In-Reply-To: <53319420-548B-407C-94EA-AD8BA1B3F73C@net-forces.com>
On Friday, January 27, 2012 04:39:24 Andre Courchesne wrote:
> Sorry for the reply on the other post, getting tired I guess...
>
>
> So...
>
> Ok, disabling loop avoidance has no effect.
>
> Has ap_isolation been tested in this type of scenario?
Antonio is the real expert on the AP isolation but judging your debug output
I'd say the AP isolation has nothing to do with your problem. Also, the
disable/enable action seems to point into the same direction.
The AP isolation only drops packets from wireless clients. You should see a
"W" in the flags section of the "batctl tg" dump:
02:69:fe:45:a3:cf ( 1) via ae:86:74:01:b4:94 ( 2) [...]
Try connecting with a wireless device and you will see it. Unless we have a
bug the traffic from the linux firewall should not be dropped (I see no W).
You could get packet dumps to find out where the pings are dropped. Maybe that
brings us closer to understanding what is going on.
Regards,
Marek
next prev parent reply other threads:[~2012-01-26 20:45 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 [this message]
2012-01-26 21:46 ` Andre Courchesne
2012-01-27 13:36 ` Antonio Quartulli
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=201201270445.50388.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.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