From: Thomas Jacob <jacob@internet24.de>
To: Andrew Clayton <andrew@digital-domain.net>
Cc: netfilter@vger.kernel.org
Subject: Re: Local to Local via firewall
Date: Sat, 1 Aug 2009 13:52:53 +0200 [thread overview]
Message-ID: <20090801115253.GA29918@internet24.de> (raw)
In-Reply-To: <20090731215235.06a83d26@digital-domain.net>
> Thanks again, but after trying this and numerous variations I still
> can't make this work, and I've read plenty of other stuff that says to
> do what you say, but no cigar :(
Well there is no fundamental reason why it shouldn't work along those lines,
most likely your other rules get in the way. I'd start by reducing
the ruleset to the basics and then I'd readd rules till I'd find
the culprit.
> It's annoying and I'd like to get it working at the firewall. But for
> now I think I'm going to take Robby's advice and have a look at split
> views with Bind. This also does seem to be the recommended way to do it.
NAT routers always hide some source addresses from at least one machine,
otherwise they wouldn't be NAT routers ;)
But sure, if you have a 1000 people behind your NAT router, NATing local
requests to local services just for the sole reason of not having to use
different names for services from the inside or a split DNS server
might not be such a good idea.
next prev parent reply other threads:[~2009-08-01 11:52 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 [this message]
2009-08-01 12:25 ` Andrew Clayton
2009-07-31 18:22 ` /dev/rob0
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=20090801115253.GA29918@internet24.de \
--to=jacob@internet24.de \
--cc=andrew@digital-domain.net \
--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.