From: Emmanuel Fuste efuste@pulp-solutions.com
To: lartc@vger.kernel.org
Subject: [LARTC] Backup Route
Date: Fri, 17 Nov 2000 11:03:58 +0000 [thread overview]
Message-ID: <marc-lartc-98373938216940@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373938216930@msgid-missing>
<PRE>Mike Fedyk wrote:
><i>
</I>><i> bert hubert wrote:
</I>><i> >
</I>><i> > On Thu, Nov 16, 2000 at 02:49:33PM -0800, Andrew wrote:
</I>><i> >
</I>><i> > > > I wan't to do a backup connection with the ADSL link.
</I>><i> > > > With what tools I can do this?
</I>><i> > > > ipchains, iptables, a third party tool?
</I>><i> > > >
</I>><i> > > I'm in the middle of doing something very similar. I don't know how often they
</I>><i> > > update the archives on this list but the subject on the thread for what I'm
</I>><i> > > working on
</I>><i> >
</I>><i> > Linux has a thing called 'dead gateway detection', which might work for you.
</I>><i> > Just make two routes with a different metric, should work I think.
</I>><i> >
</I>><i> > Existing sessions will die however because their source IP address is
</I>><i> > unroutable.
</I>><i>
</I>><i> I'm not sure that is working correctly. I have two DSLs to the internet with
</I>><i> different IP addresses, speeds and ISPs.
</I>><i>
</I>><i> DSL1: 63.194.. 384Kb/sec X 1.5-6Mb/sec ADSL on eth1 via pacbell
</I>><i> DSL2: 64.63.. is 768Kb/sec SDSL on eth2 via lmki
</I>><i>
</I>><i> Test:
</I>><i> ping yahoo site through DSL1
</I>><i> unplug phone line from bridge on DSL1
</I>><i> ip route flush table cache
</I>><i> ping yahoo site --- No response
</I>><i> tracepath yahoo site --- Still trying to use DSL1
</I>><i>
</I>><i> That isn't working.
</I>><i>
</I>><i> Here's my setup:
</I>><i> $ ip route
</I>><i> 10.1.1.1 dev eth2 scope link src 10.1.1.2
</I>><i> 10.0.0.0/24 dev eth0 scope link src 10.0.0.1
</I>><i> 127.0.0.0/8 dev lo scope link
</I>><i> default
</I>><i> nexthop via 63.194.239.201 dev eth1 weight 99
</I>><i> nexthop via 10.1.1.1 dev eth2 weight 1
</I>><i>
</I>For the default route, try:
ip route add default via 63.194.239.201 dev eth1
ip route add default via 10.1.1.1 dev eth2 metric 10
But you will loose the load balancing behaviour.
Emmanuel.
</PRE>
next prev parent reply other threads:[~2000-11-17 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-16 21:10 [LARTC] Backup Route Michel
2000-11-16 22:49 ` Andrew
2000-11-17 1:34 ` bert
2000-11-17 4:33 ` Guy
2000-11-17 10:41 ` Mike
2000-11-17 11:03 ` Emmanuel [this message]
2000-11-17 11:56 ` Mike
2003-03-19 15:19 ` [LARTC] backup route Marijus Spakovskis
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-98373938216940@msgid-missing \
--to=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.