Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit@transpect.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Simplest method for 2 external lines?
Date: Tue, 30 Oct 2001 01:59:12 +0000	[thread overview]
Message-ID: <marc-lartc-100440728300709@msgid-missing> (raw)

Apologies for asking this from naive perspective.

For a system with two external DSL connections (different providers) I'm
trying to work up a solution that combines dynamic DNS round robin
(described by Leghart in the Nov. Sys Admin) with ip route on a 2.2.19
kernel with ipchains. The system runs DNS, Apache, and masqs an internal
network. Since the DNS round robin should take care of bringing, for
instance, http requests in on whichever line is up - or both if both lines
are - what I want ip route to do is send the response back out on the same
interface the request came in on. What's the easiest way to do that?

Also, port forwarding is being used to an internal NT mail server. I'd like
to handle redundancy to that by having a secondary MX on the second public
interface, and also forwarding that to the server. Again, when the server
comes back through the masq in negotiations I'd like it to connect out
through whichever interface/IP it was connected to from.

I've looked at the Linux 2.4 Advanced Routing HOWTO and Alexey's docs, and
am having trouble identifying which capabilities I need to wrap my mind
around - there's obviously a whole lot of stuff I don't need to learn, if I
could only sort it out without learning it all first! The solution might be
easier with 2.4 iptables, but I've got a complex set of ipchains rules and
would prefer not having to translate it.

Thanks for any advice. Some things in computing come easily to me - routing
isn't one of them. But it seems like this might be reasonably simple: mark
incoming traffic according to the interface it comes in on, route it out
according to the mark.

(Once this setup is working, I'll be working to add heartbeat so a backup
server is ready to step in. If this all seems like a generically useful
setup, I'd be happy to try to document it after it comes together - the hope
is for reasonably good redundancy on the cheap.)

Whit
@transpect.com

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

             reply	other threads:[~2001-10-30  1:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-30  1:59 Whit Blauvelt [this message]
2001-10-30 18:05 ` [LARTC] Simplest method for 2 external lines? Adrian Chung
2001-11-01  0:33 ` Whit Blauvelt
2001-11-02 18:09 ` Adrian Chung

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=marc-lartc-100440728300709@msgid-missing \
    --to=whit@transpect.com \
    --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