From: Ralf Spenneberg <lists@spenneberg.org>
To: TN <tnuro@yahoo.com.au>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: accessing a internal port fowarded email server from the internal network
Date: 08 Dec 2003 07:39:32 +0100 [thread overview]
Message-ID: <1070865572.1705.9.camel@kermit> (raw)
In-Reply-To: <3FD3D65E.7000405@yahoo.com.au>
Am Mon, 2003-12-08 um 02.39 schrieb TN:
> Currently, laptop users internal to the network need to then become
> external when they work external to the LAN, and they have to either
> setup 2 different email accounts (one using the internal email server IP
> address, and one using the external IP address), or they have to
> remember to change their server settings each time they move from
> internal to external and vice-versa. Both of these are a pain for them.
> It doesn't work, the email client just times out, as if I'm still
> blocking some part of the data stream.
> What am I doing wrong ?
>
The client can reach the mailserver alright, but the mailserver tries to
respond directly to the client using the wrong IP-Address.
Easiest solution:
Apply both DNAT and SNAT at the same time. Add the following rule:
iptables -t nat -A POSTROUTING -p tcp -m multiport --dport 25,110,143 -d
192.168.10.12 -s 192.168.10.0/24 -j SNAT --to <firewall-ip>
Cheers,
Ralf
--
Ralf Spenneberg
RHCE, RHCX
Book: VPN mit Linux
Book: Intrusion Detection für Linux Server http://www.spenneberg.com
IPsec-Howto http://www.ipsec-howto.org
Honeynet Project Mirror: http://honeynet.spenneberg.org
next prev parent reply other threads:[~2003-12-08 6:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 1:39 accessing a internal port fowarded email server from the internal network TN
2003-12-08 1:57 ` Antony Stone
2003-12-08 6:39 ` Ralf Spenneberg [this message]
2003-12-09 13:13 ` Jamie Pratt
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=1070865572.1705.9.camel@kermit \
--to=lists@spenneberg.org \
--cc=netfilter@lists.netfilter.org \
--cc=tnuro@yahoo.com.au \
/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