All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Jaussaud <tatooin@kelkoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] does metric in route works?
Date: Fri, 15 Nov 2002 20:21:04 +0000	[thread overview]
Message-ID: <marc-lartc-103739176531857@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103705713712097@msgid-missing>

Hi,

No, you can't use metric this way.
If you plan to implement alternatives route with dead gateway detection,
you'll need to patch your kernel using julian's patches available at:
http://www.linux-vs.org/~julian/

From julian's doc:
"alternative  routes are  those routes that  are created  in same route
table,  have equal route  destination, prefix length,  metric and scope.
This  is  an  essential  requirement for  the  reverse  path (rp_filter)
protection  because it avoids reaching less specific routes when looking
up by specific output device."

Hope this helps.
Regards,
Vincent.

On Tue, 2002-11-12 at 00:24, Poltorak Serguei wrote:
> Hello
> 
> I would like to know how does metric work for now.
> I'm trying to use it for "failover". if my nexthop (gateway) is down i
> want another route with bigger metric to be used. for now all in vain. :(
> are there any implementation of metric in current routing mechanism??
> 
> PoltoS/
> 
> 
> 
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
-- 
Vincent Jaussaud <tatooin@kelkoo.com>
Kelkoo.com

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

      reply	other threads:[~2002-11-15 20:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-11 23:24 [LARTC] does metric in route works? Poltorak Serguei
2002-11-15 20:21 ` Vincent Jaussaud [this message]

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-103739176531857@msgid-missing \
    --to=tatooin@kelkoo.com \
    --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.