From: Radu Oprisan <radu@securesystems.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Disable netfilter for bridged traffic
Date: Wed, 31 Jan 2007 23:22:43 +0000 [thread overview]
Message-ID: <45C124C3.8070003@securesystems.ro> (raw)
In-Reply-To: <4588D088.3050702@multitech.co.in>
Luciano Ruete wrote:
> On Saturday 06 January 2007 15:30, Radu Oprisan wrote:
>> senthil wrote:
>>> Hi All,
>>> Can anybody suggests how can I disable netfilter for bridged traffic in
>>> linux-2.4.27 kernel ?
>> If i understand the question, then you just need to ignore the
>> interfaces for the bridge.
>
> this is not necesary cause bridged traffic is "layer 2" traffic, and there is
> not a chance that netfiter(layer 3) saw it.
>
> There is ebtables and iptables "physdev" in 2.6, to filter bridged traffic.
I'm sorry. I missed the part about 2.4.27 in the first message.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2007-01-31 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 5:53 [LARTC] Disable netfilter for bridged traffic senthil
2007-01-06 18:30 ` Radu Oprisan
2007-01-09 13:43 ` Luciano Ruete
2007-01-31 23:22 ` Radu Oprisan [this message]
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=45C124C3.8070003@securesystems.ro \
--to=radu@securesystems.ro \
--cc=lartc@vger.kernel.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