All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: semi OT: default route
Date: Wed, 20 Oct 2004 12:48:30 -0400	[thread overview]
Message-ID: <20041020164830.GA7438@bender.817west.com> (raw)
In-Reply-To: <20041020163734.GR21006@metastasis.org.uk>

On Wed, Oct 20, 2004 at 05:37:34PM +0100, Nick Drage wrote:
> However if you want to give the routes different metrics....
> 
> ip route add default via 1.2.3.4 metric 1
> ip route add default via 4.5.6.7 metric 2
> 
> "ip" will accept that input.
> 
> That should mean if the host can't send the traffic via 1.2.3.4 it will
> realise this ( I presume solely if it gets no arp-reply for 1.2.3.4) it
> will try and send the traffic via 4.5.6.7 instead.
> 
> That seems to be the way it should work, however on a test box my host
> is happily trying to arp for 1.2.3.4 continuosly.
> 
> Anyone help me finish off this answer ;)

yes--the linux routing code will do dead gateway detection and fall
back to a lower metric route in the event of failure, and also go back
to the higher metric route upon resurrection.  this can be useful for
an active-standby setup.

as for which route added by 'route' actually gets used--i've never spent
the time to figure out how it picks the one it uses, but it certainly
only appears to ever use one--maybe it picks the one with the lowest
numerical value...  or maybe it uses one of those magic 8-ball things...

-j

-- 
Jason Opperisano <opie@817west.com>


  reply	other threads:[~2004-10-20 16:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-20 13:25 semi OT: default route Payal Rathod
2004-10-20 16:17 ` Jason Opperisano
2004-10-20 16:37   ` Nick Drage
2004-10-20 16:48     ` Jason Opperisano [this message]
2004-10-20 16:57       ` Payal Rathod
2004-10-20 18:24         ` Jason Opperisano
2004-10-22 16:40       ` multiple external interface ? Faisal
  -- strict thread matches above, loose matches on Subject: below --
2004-10-20 18:08 semi OT: default route Daniel Chemko
2004-10-20 18:53 ` Lopsch
2004-10-20 19:56 Daniel Chemko
2004-10-20 21:05 Lopsch

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=20041020164830.GA7438@bender.817west.com \
    --to=opie@817west.com \
    --cc=netfilter@lists.netfilter.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.