From: John Madden <jmadden@ivytech.edu>
To: gtaylor+reply@riverviewtech.net
Cc: Mail List - Netfilter <netfilter@vger.kernel.org>
Subject: Re: "DNAT" w/o changing source address?
Date: Thu, 04 Oct 2007 10:19:42 -0400 [thread overview]
Message-ID: <1191507582.13379.45.camel@localhost.localdomain> (raw)
In-Reply-To: <4704F430.4070907@riverviewtech.net>
> That is very odd. Do you have other rules in place that could be
> interfering with what you are doing?
I have a dozen or so other rules that do the same thing for different
IP's (this is a load balancer).
> Normally with a server behind a NAT all I need to do is DNAT the traffic
> and allow the returning traffic to pass back out through the same NATing
> system and allow it's outbound MASQUERADEing / SNAT to hide the internal
> source IP address.
Well I thought that's what I was doing with that SNAT rule. =)
> If you do not have this type of scenario but rather both the redirecting
> IP and the real mail server's IP are both globally routable, then you
> may need to do something else. Is this possibly the case?
Yeah, both machines have globally routable IP's.
John
--
John Madden
Sr. UNIX Systems Engineer
Ivy Tech Community College of Indiana
jmadden@ivytech.edu
next prev parent reply other threads:[~2007-10-04 14:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 15:21 "DNAT" w/o changing source address? John Madden
2007-10-03 23:35 ` Grant Taylor
2007-10-03 23:50 ` Pascal Hambourg
2007-10-04 1:17 ` Grant Taylor
2007-10-04 13:14 ` John Madden
2007-10-04 13:14 ` John Madden
2007-10-04 14:09 ` Grant Taylor
2007-10-04 14:19 ` John Madden [this message]
2007-10-04 15:13 ` Grant Taylor
2007-10-04 14:17 ` Pascal Hambourg
2007-10-04 14:22 ` John Madden
2007-10-04 14:59 ` Pascal Hambourg
2007-10-04 15:13 ` John Madden
2007-10-04 15:29 ` Grant Taylor
2007-10-04 19:33 ` Grant Taylor
2007-10-04 16:01 ` Pascal Hambourg
2007-10-04 15:23 ` Grant Taylor
2007-10-04 15:52 ` Pascal Hambourg
2007-10-04 19:12 ` Grant Taylor
2007-10-04 19:25 ` John Madden
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=1191507582.13379.45.camel@localhost.localdomain \
--to=jmadden@ivytech.edu \
--cc=gtaylor+reply@riverviewtech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox