From: "/dev/rob0" <rob0@gmx.co.uk>
To: netfilter@vger.kernel.org
Subject: Re: Local to Local via firewall
Date: Fri, 31 Jul 2009 13:22:05 -0500 [thread overview]
Message-ID: <200907311322.05834.rob0@gmx.co.uk> (raw)
In-Reply-To: <20090731172419.669eb256@zeus.int.pccl>
On Friday 31 July 2009 11:24:19 Andrew Clayton wrote:
> On Fri, 31 Jul 2009 18:06:21 +0200, Thomas Jacob wrote:
> > On Fri, 2009-07-31 at 14:42 +0100, Andrew Clayton wrote:
> > [.. accessing outside IPs on a NAT router from
> > the inside network ...]
> But I do think the firewall is the proper place to do this.
To elaborate a bit on *why* Robby is right in his not-so-humble
opinion: the SNAT+DNAT solution makes your logs meaningless. There's
really no way to tell who's doing what, and from where.
I've seen cases in which people put too many eggs in a single DNS RR
basket ... like http://foo.example.com/ being SNAT'ed to LAN host
web.example.lan, and smtp:foo.example.com being SNAT'ed to a different
LAN host, mail.example.lan.
In a case like that, the SNAT+DNAT solution is the only one that will
keep foo.example.com working for clients behind the NAT. But there,
your real fix would be to use more names ... www.example.com and
mail.example.com in the above. If your DNS provider is charging you
extra for adding more names, find a reasonable DNS provider!
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
prev parent reply other threads:[~2009-07-31 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 13:42 Local to Local via firewall Andrew Clayton
2009-07-31 16:06 ` Thomas Jacob
2009-07-31 16:24 ` Andrew Clayton
2009-07-31 16:42 ` Robby Workman
2009-07-31 17:49 ` Thomas Jacob
2009-07-31 20:52 ` Andrew Clayton
2009-08-01 3:24 ` /dev/rob0
2009-08-01 11:52 ` Thomas Jacob
2009-08-01 12:25 ` Andrew Clayton
2009-07-31 18:22 ` /dev/rob0 [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=200907311322.05834.rob0@gmx.co.uk \
--to=rob0@gmx.co.uk \
--cc=netfilter@vger.kernel.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.