From: Jan Humme <jan.humme@xs4all.nl>
To: Antony Stone <Antony@Soft-Solutions.co.uk>, Ben <bench@silentmedia.com>
Cc: NetFilter <netfilter@lists.samba.org>
Subject: Re: simple nat question
Date: Tue, 2 Jul 2002 22:47:30 +0200 [thread overview]
Message-ID: <02070222473004.03048@Lms> (raw)
In-Reply-To: <20020702201814.NUXP16050.mta01-svc.ntlworld.com@there>
On Tuesday 02 July 2002 22:18, Antony Stone wrote:
> On Tuesday 02 July 2002 9:13 pm, Jan Humme wrote:
> > Ain't this what masquerading is all about?
> >
> > # iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
>
> Are you asking about the difference between MASQUERADE and SNAT ?
No, I just wanted to point out that masquerading provides an easy way to get
the desired results.
> If so, the answer's not a lot, except:
>
> 1. MASQUERADE checks the address of the interface for each packet it
> translates, therefore it's better for interfaces with dynamic addresses.
>
> 2. MASQUERADE checks the address of the interface for each packet it
> translates, therefore it's slightly less efficient for interfaces with
> static addresses.
Hey! I didn't realize that, thank you.
On the other hand, taking into consideration the elegance of a one-line
masquerading rule (one test) vs. your 4-line solution (more tests), would you
still argue that a masquerading solution is less efficient?
Jan Humme.
next prev parent reply other threads:[~2002-07-02 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 19:34 simple nat question Ben
2002-07-02 19:55 ` Antony Stone
2002-07-02 20:13 ` Jan Humme
2002-07-02 20:18 ` Antony Stone
2002-07-02 20:47 ` Jan Humme [this message]
2002-07-02 20:51 ` Ben
2002-07-02 20:58 ` Antony Stone
2002-07-02 21:08 ` Jan Humme
2002-07-02 20:53 ` Antony Stone
2002-07-02 20:37 ` Ben
2002-07-02 20:18 ` Aldo S. Lagana
2002-07-03 7:00 ` Raymond Leach
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=02070222473004.03048@Lms \
--to=jan.humme@xs4all.nl \
--cc=Antony@Soft-Solutions.co.uk \
--cc=bench@silentmedia.com \
--cc=netfilter@lists.samba.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.