From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: PPPoE on a bridge, nat sees bridge as incoming interface
Date: Fri, 07 Mar 2008 02:13:55 +0100 [thread overview]
Message-ID: <47D096D3.8090208@plouf.fr.eu.org> (raw)
In-Reply-To: <20080307004918.GB31248@possum.gg3.net>
Georgi Georgiev wrote :
>
> I thought the bridge was supposed to behave like a switching
> hub. And it probably does, but I had misconfigured it.
Yes it does. Originally, i.e. in the vanilla 2.4 kernel, this is exactly
and only what it does. Then people thought it would be cool to add some
filtering capabilities so you could build a filtering bridge. So here
came ebtables. But it had some limitations, so people thougt it would be
cool that netfilter/iptables could be used on bridged IP packets,
although it would be an ugly hack. So here came bridge-nf. Then people
thought it would be cool that netfilter/iptables could also be used on
IP packets encapsulated in bridged VLAN tagged frames, and finally in
bridged PPPoE frames. So far so good. But IMHO the problem is that those
features should have been disabled by default so the original behaviour
expected by most people would have been preserved.
next prev parent reply other threads:[~2008-03-07 1:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 17:22 PPPoE on a bridge, nat sees bridge as incoming interface Georgi Georgiev
2008-03-06 22:01 ` Grant Taylor
2008-03-06 22:05 ` Jan Engelhardt
2008-03-07 0:49 ` Georgi Georgiev
2008-03-07 1:13 ` Pascal Hambourg [this message]
2008-03-07 5:16 ` Grant Taylor
2008-03-11 11:08 ` [SOLVED] " Georgi Georgiev
2008-03-11 12:05 ` Jan Engelhardt
2008-03-11 14:32 ` Pascal Hambourg
2008-03-11 15:49 ` Jan Engelhardt
2008-03-06 22:36 ` Pascal Hambourg
2008-03-07 0:43 ` Georgi Georgiev
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=47D096D3.8090208@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@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