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.] Blocking OGMs from a node for testing purpose
Date: Mon, 17 May 2010 06:53:01 +0800 [thread overview]
Message-ID: <201005170653.01657.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20100516212754.GB2364@ritirata.org>
On Monday 17 May 2010 05:27:55 Antonio Quartulli wrote:
> It is what i described just a few rows before..the problem is that
> adding wlan0 interface to a eth-bridge (using cfg80211 driver) is not
> possible (due to operation not permitted error, probably because devs
> don't want to do that :P) either with iwlagn or rt2x00
Ok, I did not quite get that the first time but it seems you are right: The wifi
stack sets IFF_DONT_BRIDGE on any wifi interface in adhoc or station mode to
keep it from being added to a bridge. Normally, this would be a very correct
behaviour ..
Then we have to add ebtables support by calling some ebtables hooks that will
tell us whether or not to drop the packet ? Is that possible (I'm not the
ebtables expert here) ? :-)
Cheers,
Marek
next prev parent reply other threads:[~2010-05-16 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-08 17:07 [B.A.T.M.A.N.] Blocking OGMs from a node for testing purpose Antonio Quartulli
2010-05-09 17:47 ` Marek Lindner
2010-05-10 11:57 ` Antonio Quartulli
2010-05-12 21:02 ` Linus Lüssing
2010-05-13 16:38 ` Antonio Quartulli
2010-05-16 19:37 ` Marek Lindner
2010-05-16 21:27 ` Antonio Quartulli
2010-05-16 22:53 ` Marek Lindner [this message]
2010-05-17 7:20 ` Antonio Quartulli
2010-05-19 1:25 ` [B.A.T.M.A.N.] [PATCH] batman-adv: Adding netfilter-bridge hooks Linus Lüssing
2010-05-21 8:21 ` Antonio Quartulli
2010-05-21 10:17 ` Linus Lüssing
2010-05-21 18:45 ` Antonio Quartulli
2010-05-22 10:51 ` Marek Lindner
2010-05-25 23:56 ` Linus Lüssing
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=201005170653.01657.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