Re: [LARTC] route with different metric

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.



[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux