From: "Christopher Friesen" <cfriesen@nortelnetworks.com>
To: Jean-Sebastien Morisset <jsmoriss@mvlan.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: iproute2 routing problem.
Date: Tue, 28 Aug 2001 11:06:12 -0400 [thread overview]
Message-ID: <3B8BB364.47CFD3CF@nortelnetworks.com> (raw)
In-Reply-To: <20010828104118.C26589@marvin.mvlan.net>
Jean-Sebastien Morisset wrote:
> I have an ADSL modem on ppp0, and a CableModem on eth1. The plan is to
> make all services available on the ADSL, and use the CableModem as my
> default route (load balancing and fail-over are planned). Unfortunately,
> Linux gets confused if a public IP comes in on ppp0 since it's default
> route is eth1.
Assuming that you have cable already set up as the default route, why not do
something like this:
ip rule add to 10.1.1.0/24 lookup main pref 500
ip rule add from 64.39.178.10 lookup adsl pref 1000
ip route add default via 64.39.160.16 dev ppp0 table adsl
This way anything local gets routed over eth1, and anything nonlocal coming from
your DSL address (as it would if someone connects to your services over that
address) gets sent out over the DSL connection.
You should be able to set up some kind of variation of this for failover/load
balancing. I've done some custom work in this area for work and a local
failover takes about 5ms after detection of a problem.
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
prev parent reply other threads:[~2001-08-28 19:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-28 14:41 iproute2 routing problem Jean-Sebastien Morisset
2001-08-28 15:06 ` Christopher Friesen [this message]
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=3B8BB364.47CFD3CF@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=jsmoriss@mvlan.net \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).