netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Hamill <gdh@acentral.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Redirecting outgoing SMTP from LAN to another LAN server
Date: Thu, 13 May 2004 13:46:12 +0100	[thread overview]
Message-ID: <200405131346.12621.gdh@acentral.co.uk> (raw)
In-Reply-To: <20040429144757.GA6534@zion.homelinux.com>

On Thursday 29 April 2004 15:47, Sven Schuster wrote:

>So you will additionally need a SNAT rule on
> your firewall, something like
>
> iptables -t nat -A POSTROUTING -p tcp -i eth1 -s 10.0.0.0/8 \
>    -d 10.0.0.253 --dport 25 -j SNAT --to 10.0.0.xx:25
>
> where xx would be the ip of your firewall. Now both the packets
> from the client to the server and the returning packets from the
> server to the client will travel through your firewall.

This is just a final followup to say thanks for the advice, and to report on 
the final solution.

eth0 is the 0utside, and eth1 is the 1nside (that's what I use to stop 
confusing myself...) and 10.0.0.254 is the firewall and default gateway for 
all LAN machines 

$ iptables -t nat -A PREROUTING -p tcp -i eth1 -s ! 10.0.0.253 --dport 25 -j 
DNAT --to 10.0.0.253:25
$ iptables -t nat -A POSTROUTING -p tcp -s 10.0.0.0/24 -d 10.0.0.253 --dport 
25 -j SNAT --to 10.0.0.254

This way, LAN users trying to connect directly to an external mail server get 
sent to the MTA on 10.0.0.253, and 10.0.0.253 itself still has full access to 
'real' port 25 in order that it can deliver mails! :)

Cheers,
Gavin.


  parent reply	other threads:[~2004-05-13 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-29  9:59 Redirecting outgoing SMTP from LAN to another LAN server Gavin Hamill
2004-04-29 13:37 ` Alexander Samad
2004-04-29 14:47   ` Sven Schuster
2004-04-29 22:23     ` Alexander Samad
2004-04-30 12:28     ` Gavin Hamill
2004-05-13 12:46     ` Gavin Hamill [this message]
2004-05-13 13:42       ` Antony Stone
2004-05-15 11:42         ` Micha Silver
2004-05-15 12:27           ` Gavin Hamill

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=200405131346.12621.gdh@acentral.co.uk \
    --to=gdh@acentral.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).