All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Georgalis <georgw@galis.org>
To: netfilter@lists.samba.org
Subject: not loadbalancing but 2 ISPs
Date: Mon, 17 Jun 2002 23:27:00 -0400	[thread overview]
Message-ID: <20020617232700.A3401@trot> (raw)

I'm going to be migrating some servers from one ISP to another at the
same location.

Does this scenario hold water (simplified syntax for clarity). The idea
is for the server to respond (all the way to the client) regardless of
whether the request went to the IP on ISP1 or ISP2.

T1a_host01=host ip on ISP 1
T1b_host01=host ip on ISP 2
DMZ_host01=host ip on DMZ
EXT_T1a=external interface for ISP 1
EXT_T1b=external interface for ISP 2
INT_DMZ=internal interface for DMZ

nat PREROUTING --dst $T1a_host01 DNAT $DMZ_host01
nat PREROUTING --dst $T1b_host01 DNAT $DMZ_host01

INPUT -i $EXT_T1a -d $DMZ_host01 -j ACCEPT
INPUT -i $EXT_T1b -d $DMZ_host01 -j ACCEPT

nat -A POSTROUTING -s $DMZ_host01 -o $EXT_T1a -j SNAT --to-source $T1a_host01
nat -A POSTROUTING -s $DMZ_host01 -o $EXT_T1b -j SNAT --to-source $T1b_host01

FORWARD -i $INT_DMZ -o $EXT_T1a -m state --state ESTABLISHED,RELATED -j ACCEPT
FORWARD -i $INT_DMZ -o $EXT_T1b -m state --state ESTABLISHED,RELATED -j ACCEPT

If this wouldn't work, why? I'm concerned about those POSTROUTING
lines, is there a workaround?  Would the system also work for high
availability, if I could get DNS to behave?

// George






-- 
GEORGE GEORGALIS, System Admin/Architect    cell: 347-451-8229 
Security Services, Web, Mail,            mailto:george@galis.org 
File, Print, DB and DNS Servers.       http://www.galis.org/george 



             reply	other threads:[~2002-06-18  3:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18  3:27 George Georgalis [this message]
2002-06-18  8:16 ` not loadbalancing but 2 ISPs Antony Stone

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=20020617232700.A3401@trot \
    --to=georgw@galis.org \
    --cc=netfilter@lists.samba.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.