Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: Netfilter Mailing List <netfilter@lists.netfilter.org>
Subject: Re: iptables bridge filter question
Date: Thu, 18 Mar 2004 23:16:47 +0000	[thread overview]
Message-ID: <200403182316.47015.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <ILECICAFAJIIMPBBLMEAGELNCPAA.gerryw@objectivedomain.com>

On Thursday 18 March 2004 11:09 pm, Gerry Weaver wrote:

> Hi,
>
> I understand what your suggesting. Perhaps I still didn't explain well
> enough. Here's an example:
>
> [NodeA 10.10.10.1]<==>[Firewall 10.10.10.2]<==>[Router 10.10.10.254]
>
> If the router is setup as the default gateway for NodeA then wouldn't it be
> sending packets with a source address on the 10.10.10.0 network through the
> external interface of the bridge.

No, I don't think so.

I assume three things here (please let me know if I'm wrong):

1. The router IS performing source nat on outbound packets (so that packets 
which end up on the Internet have a public routable source address rather 
than something within 10.10.10.0/24).

2. The router is NOT performing source nat on inbound packets coming from the 
Internet (so that packets arriving on your local network have the correct 
source address of the machine they came from, out in the Big Wide World).

3. You have no great interest in talking to your router from local network 
machines - they want to talk to the Rest Of The World, which is on the other 
side of the router.

Now, if all the above assumptions are true, then valid packets arriving at 
your network through the router from the Internet will have the source 
addresses of the machines they came from, not the internal address of the 
router.

If, for some rather obscure reason, your router is performing source nat on 
incoming packets, then yes, they will have 10.10.10.254 as their source 
address, but I really can't think why this would be the case.

Regards,

Antony.

-- 
One good tern deserves another.
                                                     Please reply to the list;
                                                           please don't CC me.



  reply	other threads:[~2004-03-18 23:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-18  8:28 iptables bridge filter question Gerry Weaver
2004-03-18 15:24 ` Antony Stone
2004-03-18 15:33   ` Antony Stone
2004-03-18 19:28     ` Vincent Haverlant
2004-03-18 20:12 ` Gerry Weaver
2004-03-18 20:40   ` Antony Stone
2004-03-18 23:09     ` Gerry Weaver
2004-03-18 23:16       ` Antony Stone [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-03-18 15:02 Steve Jones

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=200403182316.47015.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --cc=netfilter@lists.netfilter.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