From: Martijn Lievaart <m@rtij.nl>
To: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
Cc: netfilter@lists.netfilter.org
Subject: Re: Can't get access to local servers using external IP
Date: Sun, 15 Oct 2006 20:05:07 +0200 [thread overview]
Message-ID: <45327853.4070101@rtij.nl> (raw)
In-Reply-To: <45322F80.3090502@plouf.fr.eu.org>
Pascal Hambourg wrote:
> Hello,
>
> Martijn Lievaart a écrit :
>
>>
>> There are several ways you can make this work.
>>
>> 1) When packets from $local_lan arrive destined for the webserver,
>> not only DNAT them, but SNAT them as well to an ip of the firewall.
>> The disadvantage is that the webserverlogs will not acurately report
>> the source address for these connections. This is probably what the
>> linksys did.
>
>
> Hint : using NETMAP to do the source NAT, you can do a 1:1 mapping so
> you can retrieve the original source address.
I thought about this, but the documentation on NETMAP is actually pretty
bad, so I decided I would not advertise this route.
>
> [...]
>
>> 6) Probably lots of other solutions I didn't think about.
>
>
> If you access the server by name instead of by IP address :
>
> 7) Put the private address and the name in the /etc/hosts file of your
> workstations. Quick and dirty, does not scale.
>
> 8) Set up a "split DNS" server so the internal requests receive the
> private address and the external request receive the public address.
>
I do that too, it may actually be the best advice from this list. A
bitch to set up[1], but once it's working it works like a charm.
M4
[1] I don't exactly recall my troubles setting it up, it may have been
just my situation.
next prev parent reply other threads:[~2006-10-15 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 3:08 Can't get access to local servers using external IP Patrick Cummings
2006-10-14 16:34 ` Martijn Lievaart
2006-10-15 3:08 ` Patrick Cummings
2006-10-15 12:54 ` Pascal Hambourg
2006-10-15 18:05 ` Martijn Lievaart [this message]
2006-10-15 18:21 ` Pascal Hambourg
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=45327853.4070101@rtij.nl \
--to=m@rtij.nl \
--cc=netfilter@lists.netfilter.org \
--cc=pascal.mail@plouf.fr.eu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox