From: "Seth J. Blank" <sblank@cms-forex.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Redundant Internet connections
Date: Mon, 13 Oct 2003 15:45:47 +0000 [thread overview]
Message-ID: <marc-lartc-106606026832542@msgid-missing> (raw)
I have a firewall with two redundant internet connections coming in
(eth0 and eth1) and an intranet behind eth2.
What I am trying to do is have data off of eth2 split evenly between
eth0 and eth1, and if one interface goes down, to fully utilize the other.
What I'm trying to do is have all data from eth0 be passed on to eth2
(unless it's stopped by the firewall), same with eth1, and all data from
eth2 be split evenly between eth0 and eth1.
currently I have the following routes and rules to accomplish this:
ip route add 10.0.0.0/8 via GATEWAY0 table 1 proto static
ip route add 10.0.0.0/8 via GATEWAY1 table 2 proto static
ip route add default table default scope global nexthop via GATEWAY0 dev
eth0 weight 1 nexthop via GATEWAY1 dev eth1 weight 1
ip rule add pref 1500 iif eth0 table 1
ip rule add pref 1501 iif eth1 table 2
ip rule add pref 100 iif eth2 table default
This does NOT work properly.
From localhost, everything works perfectly. I can bring up and down
interfaces and everything works properly and transparently.
But, from the intranet, everything stops. With a different default route:
ip route add default via GATEWAY0 dev eth0 table default
everything is fine from both localhost and the intranet. Same with
GATEWAY1 eth1.
Can anyone offer advice on how to resolve this problem?
The only way I can think of so far is a remarkably simple but stupid
hack, where I just ping -I eth0 GATEWAY0 and ping -I eth1 GATEWAY1 every
thirty seconds or so and switch default routes if an interface is down.
This obviously does not solve the problem, nor allow bandwidth to be
shared across both lines.
Any help would be greatly appreciated.
Seth J. Blank
Systems Operations
Capital Market Services, LLC
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2003-10-13 15:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-13 15:45 Seth J. Blank [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-21 7:05 [LARTC] Redundant internet connections Grant Taylor
2007-06-21 7:46 ` Salim S I
2007-06-21 14:46 ` Grant Taylor
2007-06-21 15:35 ` Peter Rabbitson
2007-06-21 15:52 ` Grant Taylor
2007-06-21 16:00 ` Peter Rabbitson
2007-06-21 16:23 ` Grant Taylor
2007-06-21 16:47 ` Peter Rabbitson
2007-06-21 17:02 ` Grant Taylor
2007-06-21 17:37 ` Peter Rabbitson
2007-06-21 18:27 ` Grant Taylor
2007-06-21 21:01 ` Alex Samad
2007-06-21 21:24 ` Grant Taylor
2007-06-21 22:18 ` Alex Samad
2007-06-21 22:23 ` Grant Taylor
2007-06-21 22:30 ` Alex Samad
2007-06-21 22:35 ` Grant Taylor
2007-06-21 22:39 ` Grant Taylor
2007-06-22 11:54 ` Gustavo Homem
2007-06-22 14:22 ` Grant Taylor
2007-06-22 14:57 ` Gustavo Homem
2007-06-22 15:59 ` Grant Taylor
2007-06-22 18:57 ` 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=marc-lartc-106606026832542@msgid-missing \
--to=sblank@cms-forex.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 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.