All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Picton <chrisp@tangent.co.za>
To: lartc@vger.kernel.org
Subject: [LARTC] DGD of upstream routers
Date: Thu, 08 Mar 2007 16:48:39 +0000	[thread overview]
Message-ID: <45F03E67.6040604@tangent.co.za> (raw)

Hi

I have read various info, and mailing list archives, but have not found 
an answer to the following.

I have a few servers with configurations similar to the following:

They each have multiple uplinks to the Internet, and a sample config is 
as follows:

eth1 is 192.168.0.1, connected to 192.168.0.2
eth2 is 192.168.1.1, connected to 192.168.1.2

My default route looks like:
ip route add scope global equalize nexthop via 192.168.0.2 dev eth1 \ 
weight 1 nexthop via 192.168.1.2 dev eth2 weight 1

If one line goes down, I would like the second to be used exclusively 
until the first comes back up

However, the IPs 192.168.0.2 and 192.168.1.2 are always available and 
reachable.   It is the connection past those devices which may drop.

Do any of the available options or patches take this into account, or do 
I have to write custom ping scripts to try reach remote hosts via each 
gateway, and modify the routes if a line appears to be down.


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

             reply	other threads:[~2007-03-08 16:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-08 16:48 Chris Picton [this message]
2007-03-14 12:44 ` [LARTC] DGD of upstream routers Chris Picton
2007-03-14 13:29 ` Michał Margula

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=45F03E67.6040604@tangent.co.za \
    --to=chrisp@tangent.co.za \
    --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.