From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Georgi Georgiev <chutz@gg3.net>
Cc: netfilter@vger.kernel.org
Subject: Re: PPPoE on a bridge, nat sees bridge as incoming interface
Date: Thu, 06 Mar 2008 23:36:53 +0100 [thread overview]
Message-ID: <47D07205.10906@plouf.fr.eu.org> (raw)
In-Reply-To: <20080306172218.GA14566@possum.gg3.net>
Hello,
Georgi Georgiev wrote :
>
> I am having trouble understaning how bridging and iptables fit together.
> The situation that bugs me is: if I do a PPPoE connection over a bridge
> with a single physical port, my nat table will see any incoming packet
> as coming from the bridge interface, and not the ppp interface. Why?
I guess you have a kernel 2.6.22 or above.
From ChangeLog-2.6.22 :
[NETFILTER]: bridge-nf: filter bridged IPv4/IPv6 encapsulated in
pppoe traffic
The attached patch by Michael Milner adds support for using iptables
and ip6tables on bridged traffic encapsulated in pppoe frames,
similar to what's already supported for vlan.
Setting the net.bridge.bridge-nf-filter-pppoe-tagged sysctl
(/proc/sys/net/bridge/bridge-nf-filter-pppoe-tagged) to 0 should disable it.
From <kernelsourcedir>/Documentation/networking/ip-sysctl.txt :
bridge-nf-filter-pppoe-tagged - BOOLEAN
1 : pass bridged pppoe-tagged IP/IPv6 traffic to {ip,ip6}tables.
0 : disable this.
Default: 1
next prev parent reply other threads:[~2008-03-06 22:36 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
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 [this message]
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=47D07205.10906@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=chutz@gg3.net \
--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