Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Radek 'Goblin' Pieczonka" <goblin@pentex.pl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] PAT HOW to - IPTABLES
Date: Mon, 10 Dec 2007 23:19:22 +0000	[thread overview]
Message-ID: <475DC97A.50102@pentex.pl> (raw)
In-Reply-To: <7ed6b0aa0712100220n57ea0e54x628d539621cb6b35@mail.gmail.com>


>> Suppose, I have 3  mail servers @ DMZ zone with one real ip. the situation
>> as before?
>>
>> in that case, What can I do?
>>     
> your could use exim/postfix and route the mail to the right server, but I guess 
> you are trying to find out how to have port 25 on the real ip nat'ed to one of 
> the 3 dmz'ed ip based upon the destination mail address
>
> short answer you can't as far as I know, iptables only looks at src ip / src 
> port & dest ip/dest port.  You could write your own plugin module to look into 
> the tcp stream.
>   

based upon destination email address/domain could be done by postfix and 
transports for selected mail/domain to selected server. but there is 
also a possibility of load balancing and failover for set of domains 
with all servers working with all the domains for HA and flexibility of 
computing power, then id say take a look at keepalived for both those 
features. for http traffic its actually the same, and also you can 
consider apache reverse proxy feature.

-- 
Radek aka Goblin
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-12-10 23:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 10:32 [LARTC] PAT HOW to - IPTABLES Indunil Jayasooriya
2007-12-10 10:33 ` Alexandre J. Correa - Onda Internet
2007-12-10 10:51 ` Indunil Jayasooriya
2007-12-10 21:29 ` Alex Samad
2007-12-10 23:19 ` Radek 'Goblin' Pieczonka [this message]
2007-12-11  8:16 ` Alex Samad
2007-12-11 15:31 ` Grant Taylor

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=475DC97A.50102@pentex.pl \
    --to=goblin@pentex.pl \
    --cc=lartc@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