All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Margula" <alchemyx@uznam.net.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Multipath routing
Date: Tue, 05 Jun 2007 09:13:52 +0000	[thread overview]
Message-ID: <46652950.8000701@uznam.net.pl> (raw)
In-Reply-To: <CHEKIDJGBLPDJGGHOGPKGEMHCFAA.lists@aptedtech.com>

Hello!

	I have trouble with multipath routing. Those options are enabled in kernel:

[*]   IP: policy routing
[*]   IP: equal cost multipath
[*]     IP: equal cost multipath with caching support (EXPERIMENTAL)
<*>       MULTIPATH: round robin algorithm

But issuing:

ip r a 1.2.3.0/23 scope global equalize nexthop via 80.245.176.11 \
    dev eth0 weight 1 nexthop via 80.245.176.13 dev eth0 weight 1

and then

# ip r s
[...]
1.2.3.0/24
         nexthop via 80.245.176.11  dev eth0 weight 1
         nexthop via 80.245.176.13  dev eth0 weight 1

As you can see there is no equalize keyword in here.

Also I have trouble using multipath quagga, it simply doesn't put 
multipath route in routing table.

For example:

faramir# sh ip bgp 10.100.0.1
BGP routing table entry for 10.101.0.0/22
Paths: (2 available, best #1, table Default-IP-Routing-Table)
   Not advertised to any peer
   Local
     80.245.176.13 (metric 1) from 80.245.176.13 (80.245.177.4)
       Origin IGP, metric 0, localpref 100, weight 150, valid, internal, 
best
       Last update: Tue Jun  5 01:59:29 2007

   Local
     80.245.176.10 (metric 1) from 80.245.176.10 (80.245.176.10)
       Origin IGP, metric 0, localpref 100, weight 100, valid, internal
       Last update: Tue Jun  5 01:28:02 2007

# ip r s
[...]
10.100.0.0/22 via 80.245.176.11 dev eth0  proto zebra

But if I manually put something like that in quagga:

faramir(config)# ip route 1.2.3.0/24 80.245.176.13
faramir(config)# ip route 1.2.3.0/24 80.245.176.11

Then:

# ip r s
[...]
1.2.3.0/24
         nexthop via 80.245.176.11  dev eth0 weight 1
         nexthop via 80.245.176.13  dev eth0 weight 1


Please help, I am out of ideas.

-- 
Micha³ Margula, alchemyx@uznam.net.pl, http://alchemyx.uznam.net.pl/
"W ¿yciu piêkne s± tylko chwile" [Ryszard Riedel]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-06-05  9:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-24  2:18 [LARTC] multipath routing Lists @ Aptedtech
2004-03-24  6:05 ` RonSenykoff
2004-03-25  1:22 ` Lists @ Aptedtech
2005-10-26 21:47 ` comp.techs
2005-10-27 14:20 ` Edmundo Carmona
2005-10-27 16:02 ` comp.techs
2005-10-27 18:05 ` comp.techs
2005-11-17 20:47 ` comp.techs
2007-06-05  9:13 ` Michał Margula [this message]
2007-06-05 19:46 ` [LARTC] Multipath routing Piotr Chytla
2007-06-06 10:05 ` Michał Margula
2007-06-07  9:07 ` Michał Margula
  -- strict thread matches above, loose matches on Subject: below --
2005-08-16  4:11 [LARTC] Multipath Routing Daniel Frederiksen
2005-08-16  8:39 ` Alexander Samad

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=46652950.8000701@uznam.net.pl \
    --to=alchemyx@uznam.net.pl \
    --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.