From: Peter Surda <surda@shurdix.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Unequal Multipath Routing?
Date: Tue, 27 Jun 2006 18:16:10 +0000 [thread overview]
Message-ID: <200606272016.11478.surda@shurdix.com> (raw)
In-Reply-To: <592F914D209FD942908826DFF2277A2D02054563@COMMSSERVER>
On Tuesday 27 June 2006 15:16, Luciano Ruete wrote:
> how about:
> ip route add default nexthop via a.a.a.a weight 4 nexthop via b.b.b.b
> weight 3
exactly.
> Not tested but i think it can work.
tested, works.
> Luciano
Yours sincerely,
Peter
--
http://www.shurdix.org - Linux distribution for routers and firewalls
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-06-27 18:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 11:33 [LARTC] Unequal Multipath Routing? Andrew Lyon
2006-06-27 13:16 ` Luciano Ruete
2006-06-27 18:16 ` Peter Surda [this message]
2006-06-28 8:19 ` Andrew Lyon
2006-06-28 13:15 ` Luciano Ruete
2006-06-28 14:01 ` Andrew Lyon
2006-06-28 15:03 ` Luciano Ruete
2006-06-28 15:35 ` Andrew Lyon
2006-06-28 18:43 ` Luciano Ruete
2006-06-28 18:44 ` Torsten Luettgert
2006-06-29 7:26 ` Andrew Lyon
2006-06-29 7:43 ` Andrew Lyon
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=200606272016.11478.surda@shurdix.com \
--to=surda@shurdix.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.