From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: NAT for multiple non-directly connected subnets
Date: Fri, 09 Nov 2007 10:47:19 -0600 [thread overview]
Message-ID: <47348F17.3000408@riverviewtech.net> (raw)
In-Reply-To: <e97f32c10711090742h45794a40me7207df8d0d98473@mail.gmail.com>
On 11/09/07 09:42, Bradley Kite wrote:
> the connection-tracking needs to be turned off on the bridges in
> order to make this work:
Oh, you are running bridging (NOTHING at all wrong with that) but it
does change things a bit. Had I known that you were running bridging I
would have asked about the Bridged NetFilter configuration in your kernel.
Based on the fact that you are running bridging and the fact that you
have to touch IPTables for bridged traffic tells me that you are using
Bridged NetFilter code. This makes it even more important to know what
your IPTables configuration is to help solve your problem as it was.
Seeing as how you have worked around your problem, we no longer need to
see the output of iptables-save.
I don't think you solved your real problem, rather worked around it.
But hay, if that works for you and packets are moving like they need to,
so be it and good for you. ;)
Grant. . . .
next prev parent reply other threads:[~2007-11-09 16:47 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 [this message]
2007-11-09 23:08 ` Pascal Hambourg
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=47348F17.3000408@riverviewtech.net \
--to=gtaylor@riverviewtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.