From: Grant Taylor <gtaylor@riverviewtech.net>
To: Mail List - Netfilter <netfilter@lists.netfilter.org>
Subject: Re: how to configure a router/firewall with no nat
Date: Sun, 14 Jan 2007 22:27:46 -0600 [thread overview]
Message-ID: <45AB02C2.30107@riverviewtech.net> (raw)
In-Reply-To: <45A95397.9040808@plouf.fr.eu.org>
On 01/13/07 15:48, Pascal Hambourg wrote:
> I really do not understand why one would use NAT when they do not have
> to. NAT is a necessary evil, and when it is not necessary, it is just
> evil. NAT does not provide security, or only through obscurity.
I believe it is the obscurity that some people seek when using NAT. The
only other reason (at the moment) I can thing off for wanting to NAT
inbound traffic is so that the advertised IP address can serve multiple
resources, even if one machine can not. I.e. direct HTTP to the web
server(s), SMTP to the exchange servers or the sendmail server, or VPN
traffic to an internal VPN concentrator, etc. This allows a company to
minimize the number of IPs that are directly accessible on the net.
Grant. . . .
prev parent reply other threads:[~2007-01-15 4:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-13 17:40 how to configure a router/firewall with no nat Carlos Rotenberg
2007-01-13 18:34 ` Pascal Hambourg
2007-01-13 21:13 ` Elvir Kuric
2007-01-13 21:48 ` Pascal Hambourg
2007-01-15 4:27 ` Grant Taylor [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=45AB02C2.30107@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--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 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.