[prev in list] [next in list] [prev in thread] [next in thread] 

List:       quagga-dev
Subject:    [quagga-dev 4877] Re: Problem with Multipath
From:       "David H. Guerrero" <elcinturapartida () yahoo ! es>
Date:       2007-05-30 7:03:52
Message-ID: 363425.44849.qm () web26008 ! mail ! ukl ! yahoo ! com
[Download RAW message or body]

Hi all,

AFIK, when a next hop is selected, an entry is added to the cache, the routing \
subsystem always consults the cache before invoking any check on  routing tables. The \
next traffic will be handled straight from the cache. 

Best regards,

David

----- Mensaje original ----
De: Jorge Rodríguez <jrs327@tid.es>
Para: quagga-dev@lists.quagga.net
Enviado: martes, 29 de mayo, 2007 17:03:57
Asunto: [quagga-dev 4873] Problem with Multipath

Hi all,

I am trying to send traffic through multiple paths in a simple test bed. 
However, I am facing some problems. I would be very grateful if somebody 
could help me :-)

The test bed is the following one:

+----------+     +------+       +------+      +----------+
> > > > -------|      |      |          |
> net 1  |-----| rt 1 |       | rt 2 |------|   PC 1   |
> > > > -------|      |      |          |
+----------+     +------+       +------+      +----------+


net 1 -> 10.95.0.0/19
rt1 interface in net 1 -> 10.95.7.218
rt1 shared interfaces -> 172.16.96.4
                                     172.16.99.4
rt2 shared interfaces -> 172.16.96.2
                                     172.16.99.2
rt2 interface with PC1 -> 172.16.97.2
PC1 interface              -> 172.16.97.3

I have configured rt1 and rt2 with ./configure --enable-multipath=2.

I think I have configured rt1 and rt2 correctly. In fact, when I type  
"ip route list" in rt1  I obtain the following routing table:

172.16.97.0/24  proto zebra  metric 30
        nexthop via 172.16.96.2  dev eth0 weight 1
        nexthop via 172.16.99.2  dev eth2 weight 1
172.16.96.0/24 dev eth0  proto kernel  scope link  src 172.16.96.4
172.16.99.0/24 dev eth2  proto kernel  scope link  src 172.16.99.4
10.95.0.0/19 dev eth1  proto kernel  scope link  src 10.95.7.218


It seems as though I have two paths to reach PC1 with the same weight. 
However, when I send two ICMP requests from different machines in net1, 
both travel the same interface (172.16.99.2 dev eth2).

I don't know what I am doing wrong. Please, could somebody help me?

Thanks in advance!
Jorge
_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-dev





       
____________________________________________________________________________________
¡Descubre una nueva forma de obtener respuestas a tus preguntas!
Entra en Yahoo! Respuestas.
http://es.answers.yahoo.com/info/welcome

_______________________________________________
Quagga-dev mailing list
Quagga-dev@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-dev


[prev in list] [next in list] [prev in thread] [next in thread]