From: Martijn Lievaart <m@rtij.nl>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: netfilter-devel@lists.netfilter.org, azez@ufomechanic.net
Subject: Re: snat bridge routes reply packets
Date: Fri, 30 Sep 2005 07:27:46 +0200 [thread overview]
Message-ID: <433CCCD2.9030504@rtij.nl> (raw)
In-Reply-To: <Pine.LNX.4.61.0509291817370.4714@filer.marasystems.com>
Henrik Nordstrom wrote:
> On Thu, 29 Sep 2005, Martijn Lievaart wrote:
>
>> so I think I'm still missing something.
>
>
> Simplest setup explaining the case as I understood it:
>
> unknown network mesh -> Bridge running SNAT -> Internet
>
> and you want the bridge to SNAT whatever is seen from the internal
> network, no matter what address is being used. The bridge does not
> have full knowledge of how the internal network mesh looks like, only
> that packets coming in on that interface is from the internal network.
>
>
Ah, now I see. The unknown network mesh uses multiple routers which are
unknown to the bridge, so the bridge does not know where to route the
return packets, although it could know if it saved the mac the original
packet came from. Right?
M4
next prev parent reply other threads:[~2005-09-30 5:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 16:05 snat bridge routes reply packets Amin Azez
2005-09-28 19:56 ` Henrik Nordstrom
2005-09-29 8:42 ` Amin Azez
2005-09-29 10:11 ` Henrik Nordstrom
2005-09-29 12:19 ` Amin Azez
2005-09-29 12:49 ` Martijn Lievaart
2005-09-29 13:12 ` Amin Azez
2005-09-29 15:20 ` Martijn Lievaart
2005-09-29 16:33 ` Henrik Nordstrom
2005-09-30 5:27 ` Martijn Lievaart [this message]
2005-09-30 11:24 ` Henrik Nordstrom
2005-10-03 10:48 ` Amin Azez
2005-10-03 12:24 ` Henrik Nordstrom
2005-10-04 10:58 ` Amin Azez
2005-09-30 9:28 ` Amin Azez
2005-09-29 14:35 ` Henrik Nordstrom
2005-09-30 9:56 ` Amin Azez
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=433CCCD2.9030504@rtij.nl \
--to=m@rtij.nl \
--cc=azez@ufomechanic.net \
--cc=hno@marasystems.com \
--cc=netfilter-devel@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 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.