From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: How to Get a DMZ hosts's trafic routed via a particular IP address on a firewall?
Date: Fri, 6 May 2005 10:40:27 -0400 [thread overview]
Message-ID: <20050506144027.GA27512@bender.817west.com> (raw)
In-Reply-To: <c0e9781f05050607362e5d644e@mail.gmail.com>
On Fri, May 06, 2005 at 03:36:04PM +0100, Greg Cope wrote:
> Ah - tried this:
>
> iptables -t nat -A POSTROUTING -o eth0 -s 192.168.254.2 -p tcp --dport
> 25 -j SNAT --to-source 217.154.55.250
looks good.
> Or variants there off.
>
> No Joy...
not even...bill joy?
> I could scream......
mmm...ice cream...
> Anyone any ideas
yeah.
> Greg
>
> mail.e-dba.net = 192.168.254.3 the DMZ / private address
> $ iptables -t nat -L
> Chain PREROUTING (policy ACCEPT)
> target prot opt source destination
> DNAT tcp -- anywhere mail.e-dba.net tcp
> dpt:smtp to:192.168.254.2
>
> Chain POSTROUTING (policy ACCEPT)
> target prot opt source destination
> MASQUERADE all -- 192.168.0.0/16 anywhere
> SNAT tcp -- mail.e-dba.net anywhere to:217.154.55.250
remember the part where i said, "make sure the 2nd rule comes *before*
any outbound SNAT/MASQ rule that is less specific"...i do--man, those
were good times.
anyways, since you match all 192.168.0.0/16 traffic with the MASQ rule,
the SNAT rule for 192.168.254.3 will never be matched.
translation: put the dang SNAT rule for the mail server first.
-j
--
"Lois: I'll be just like Hillary Clinton, only you know, without the
penis."
--Family Guy
next prev parent reply other threads:[~2005-05-06 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 16:31 How to Get a DMZ hosts's trafic routed via a particular IP address on a firewall? Greg Cope
2005-05-05 21:34 ` Jason Opperisano
2005-05-06 14:36 ` Greg Cope
2005-05-06 14:40 ` Jason Opperisano [this message]
2005-05-06 14:57 ` How to Get a DMZ hosts's trafic routed via a particular IP address on a firewall - NOW solved Greg Cope
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=20050506144027.GA27512@bender.817west.com \
--to=opie@817west.com \
--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 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.