From: Herve Eychenne <rv@wallfire.org>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Netfilter development mailing list
<netfilter-devel@lists.netfilter.org>
Subject: Re: [PATCH] MASQUERADE handling of device events
Date: Wed, 24 Nov 2004 16:39:02 +0100 [thread overview]
Message-ID: <20041124153902.GM2417@eychenne.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0411241018270.15946@filer.marasystems.com>
On Wed, Nov 24, 2004 at 10:24:34AM +0100, Henrik Nordstrom wrote:
> On Wed, 24 Nov 2004, Rusty Russell wrote:
> >Drawing a link between point-to-point and addresses being static is
> >wrong, IMHO.
> Agreed.
> This discussion is equally important on Ethernet with dynamic IP
> assignment. Here the interface name is defenitely static.
> As already discussed very many times MASQUERADE is a best effort to handle
> the common "dial up like" with dynamic Internet IP assignment scenarios in
> an easy manner. A multiple PPP situation is more of an exception than
> rule to this, and in addition userspace has the option of using statically
> reserved PPP devices for the connections in question to make the proposed
> MASQUERADE fully predictable in such situations.
Being the guy who proposed the original change to Rusty during the
workshop 2003, I eventually step up to support this view. :-)
IMHO, the goal of the MASQUERADE target is trying to deal as
nicely as possible with the common cases.
I think it should be kept that way, no matter it may have some side effect
for uncommon or obscur setups, as long as the potential corner cases are
clearly documented.
The more complex scenarios should always be able to use something
else than MASQUERADE.
Herve
--
_
(°= Hervé Eychenne
//)
v_/_ WallFire project: http://www.wallfire.org/
prev parent reply other threads:[~2004-11-24 15:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-07 18:18 [PATCH] MASQUERADE handling of device events Phil Oester
2004-11-08 1:06 ` Henrik Nordstrom
2004-11-08 13:50 ` Harald Welte
2004-11-11 22:58 ` David S. Miller
2004-11-08 16:05 ` Patrick McHardy
2004-11-08 16:15 ` Phil Oester
2004-11-08 16:24 ` Patrick McHardy
2004-11-08 16:34 ` Phil Oester
2004-11-08 21:55 ` Phil Oester
2004-11-09 11:04 ` Patrick McHardy
2004-11-09 16:53 ` Phil Oester
2004-11-09 17:44 ` Patrick McHardy
2004-11-21 2:58 ` Rusty Russell
2004-11-23 21:16 ` Phil Oester
2004-11-24 3:37 ` Rusty Russell
2004-11-24 9:24 ` Henrik Nordstrom
2004-11-24 15:39 ` Herve Eychenne [this message]
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=20041124153902.GM2417@eychenne.org \
--to=rv@wallfire.org \
--cc=hno@marasystems.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=rusty@rustcorp.com.au \
/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.