All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juri Haberland <haberland@altus.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] route with different metric
Date: Wed, 26 Sep 2001 13:45:24 +0000	[thread overview]
Message-ID: <marc-lartc-100151193623955@msgid-missing> (raw)
In-Reply-To: <marc-lartc-100150978014261@msgid-missing>

bert hubert wrote:
> 
> On Wed, Sep 26, 2001 at 03:10:35PM +0200, Christian Lox wrote:
> > Hi everyone!
> >
> > Sorry if this is a FAQ but I did not find a searchable archive.
> >
> > What I am planning to do:
> > 2 different connections to 2 different ISPs.
> > One is handled by an ISDN card, one via ethernet to their router
> > (DSL).
> > We want to use the DSL line; only if this fails we need the ISDN
> > line.
> > I played around with the metrics but could not get it to work.
> 
> This *will* be an FAQ soon! It's by far the most asked question. The short
> answer is: you are out of luck. There is no way to reliably automate this.
> 
> The best solution found so far is to check in a cron script which connection
> is up, and in case of problems, run something like 'ip route replace default
> via 1.2.3.4 dev ppp0' or 'ip route replace default via 4.3.2.1 dev eth1'.
> 
> There are more interesting solutions but they are not easy. There is
> something called 'dead gateway detection'. You may experiment with:
> 
> # ip route add default nexthop 1.2.3.4 dev ppp0 nexthop 4.3.2.1 dev eth1

The syntax is:
ip route add default nexthop via 1.2.3.4 dev ppp0 nexthop via 4.3.2.1
dev eth1

> If that works as intended, please let us know!

I just tried and it does some funny things - still investigating...

Juri

-- 
  If each of us have one object, and we exchange them,
     then each of us still has one object.
  If each of us have one idea,   and we exchange them,
     then each of us now has two ideas.

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

  parent reply	other threads:[~2001-09-26 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-26 13:10 [LARTC] route with different metric Christian Lox
2001-09-26 13:13 ` bert hubert
2001-09-26 13:39 ` Christoph Simon
2001-09-26 13:45 ` Juri Haberland [this message]
2001-09-26 13:53 ` Juri Haberland
2001-09-26 14:10 ` bert hubert
2001-09-26 14:37 ` Juri Haberland
2001-09-26 18:05 ` Adrian Chung
2001-09-26 20:53 ` bert hubert
2001-09-26 21:16 ` Adrian Chung
2001-09-27  7:44 ` Juri Haberland
2001-09-27 22:40 ` 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-100151193623955@msgid-missing \
    --to=haberland@altus.de \
    --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.