Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: Bradley Kite <bradley.kite@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: NAT for multiple non-directly connected subnets
Date: Sat, 10 Nov 2007 00:08:17 +0100	[thread overview]
Message-ID: <4734E861.3030106@plouf.fr.eu.org> (raw)
In-Reply-To: <e97f32c10711090742h45794a40me7207df8d0d98473@mail.gmail.com>

Hello,

Bradley Kite a écrit :
> 
> the connection-tracking needs to be turned off on the bridges in order
> to make this work:
> 
> iptables --table raw -A PREROUTING -i [BRIDGE] -j NOTRACK

This may have undesirable side effects unless you add "-m physdev 
--physdev-is-bridged" to ensure that this rule matches only bridged 
traffic and not forwarded traffic received on the bridge interface.
If you just don't want Netfilter (including the conntrack and iptables) 
to see the bridged IP traffic, you can do this by setting the sysctl 
net.bridge.bridge-nf-call-iptables to 0.

echo 0 > /proc/sys/net/bridge/bridge-nf-call-iptables
or
sysctl -w net.bridge.bridge-nf-call-iptables=0

Add the following line in /etc/sysctl.conf to make it persistent across 
reboots :

net.bridge.bridge-nf-call-iptables=0

-- 


  parent reply	other threads:[~2007-11-09 23:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 21:53 NAT for multiple non-directly connected subnets Bradley Kite
2007-11-08 22:04 ` Matt Zagrabelny
2007-11-08 22:17   ` Bradley Kite
2007-11-08 22:23     ` Grant Taylor
2007-11-08 22:25     ` Matt Zagrabelny
2007-11-08 22:34       ` Bradley Kite
2007-11-08 22:37         ` Grant Taylor
2007-11-09 10:43         ` Bradley Kite
2007-11-09 15:42           ` Bradley Kite
2007-11-09 16:47             ` Grant Taylor
2007-11-09 23:08             ` Pascal Hambourg [this message]
2007-11-10  8:29               ` Bradley Kite

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=4734E861.3030106@plouf.fr.eu.org \
    --to=pascal.mail@plouf.fr.eu.org \
    --cc=bradley.kite@gmail.com \
    --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