[quagga-dev 4133] Re: Inconsistent "inactive" route in OSPF

Erik Tromp erik_tromp at hotmail.com
Fri May 12 13:09:10 BST 2006


Paul,

I finally got some time to try your patch. And guess what... it didn't work.
Nothing personal, though.


On the host running both OLSR and OSPF we can see a route to 10.0.43.0/24
via 10.0.3.3, where a kernel route exists for 10.0.3.3/32. No 'inactive'
routes any more (thanks to your patch):

QuaggaOlsrNode> show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       I - ISIS, B - BGP, > - selected route, * - FIB route

C>* 10.0.3.0/24 is directly connected, eth1
K>* 10.0.3.3/32 is directly connected, eth1
K>* 10.0.43.0/24 via 10.0.3.3, eth1
C>* 10.0.44.0/24 is directly connected, eth2
C>* 127.0.0.0/8 is directly connected, lo
O   172.18.190.0/24 [110/10] is directly connected, eth0, 00:07:14
C>* 172.18.190.0/24 is directly connected, eth0
O>* 192.168.11.0/24 [110/20] via 172.18.190.1, eth0, 00:07:01


However, on the host running only OSPF, the route to 10.0.43.0/24 is *not*
visible:

OspfNode> show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       I - ISIS, B - BGP, > - selected route, * - FIB route

O>* 10.0.3.0/24 [110/20] via 172.18.190.4, eth0, 00:07:24
O>* 10.0.44.0/24 [110/20] via 172.18.190.4, eth0, 00:07:24
C>* 127.0.0.0/8 is directly connected, lo
O   172.18.190.0/24 [110/10] is directly connected, eth0, 02:09:01
C>* 172.18.190.0/24 is directly connected, eth0
C>* 192.168.11.0/24 is directly connected, eth2


By the way I tried the same with the IpInfusion routing suite, we have here.
It costs big bucks, so I expect something from it.  Indeed it worked correct
for our situation:


On the host running both OLSR and OSPF we can see a route to 10.0.73.0/24
via 10.0.45.3, where a kernel route exists for 10.0.45.3/32. No 'inactive'
routes:

IMI#sho ip rout
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
area
       * - candidate default

C       10.0.6.0/24 is directly connected, bridge0.6
K       10.0.6.3/32 via 10.0.45.3, bridge0.45
C       10.0.45.0/24 is directly connected, bridge0.45
K       10.0.45.3/32 is directly connected, bridge0.45
C       10.0.72.0/24 is directly connected, bridge0.7
K       10.0.73.0/24 via 10.0.45.3, bridge0.45
C       127.0.0.0/8 is directly connected, loopback
C       192.7.2.0/24 is directly connected, bridge0.2
O E2    192.7.7.0/24 [110/20] via 192.7.2.1, bridge0.2, 00:29:25


On the host running only OSPF, the route to 10.0.73.0/24 *is* visible.

IMI>sho ip rou
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter
area
       * - candidate default

O E2    10.0.6.0/24 [110/20] via 192.7.2.2, bridge0.2, 00:19:33
O E2    10.0.6.3/32 [110/20] via 192.7.2.2, bridge0.2, 00:19:11
O E2    10.0.45.0/24 [110/20] via 192.7.2.2, bridge0.2, 00:19:33
O E2    10.0.45.3/32 [110/20] via 192.7.2.2, bridge0.2, 00:19:11
O E2    10.0.72.0/24 [110/20] via 192.7.2.2, bridge0.2, 00:19:33
O E2    10.0.73.0/24 [110/20] via 192.7.2.2, bridge0.2, 00:19:11
C       127.0.0.0/8 is directly connected, loopback
C       192.7.2.0/24 is directly connected, bridge0.2
C       192.7.7.0/24 is directly connected, bridge0.7
K       192.7.10.0/24 via 192.7.2.2, bridge0.2
IMI>sho ver
ZebOS version 7.1.4.e0 IPIRouter 03/29/05 10:47:34
 Build # is ZebOS-7-1-4-e0-IPI on host powerpc-unknown-linux-gnu
 Copyright (C) 2001-2004 IP Infusion Inc.  All rights reserved.


Next step is I will try the patch I found posted on
http://www.olsr.org/pipermail/olsr-dev/2006-April/071046.html ; that may
give a solution.

Best Regards,
Erik


----- Original Message ----- 
From: "Paul Jakma" <paul at clubi.ie>
To: "Erik Tromp" <erik_tromp at hotmail.com>
Cc: "Quagga Dev" <quagga-dev at lists.quagga.net>
Sent: Monday, May 08, 2006 8:36 PM
Subject: [quagga-dev 4131] Re: Inconsistent "inactive" route in OSPF


> On Mon, 8 May 2006, Erik Tromp wrote:
>
> > Okay you have a point...
> >
> > So now I go to the guys at OLSR and tell them they made a
> > piece of #$%^
>
> No - don't tell them that :). (OLSR is really cool actually).
>
> > Nope. So the route would have become inactive after 1 minute?
>
> That's the theory.
>
> > Indeed this will also be the case often. Multi-hop connections do
> > occur in the wireless world.
>
> Right, and that case would definitely be useful. Your original case
> is also interesting, but for the reason described by the other
> respondent (the OLSR case remains 'pointless' ;) ).
>
> > So will you support it :-) ?
>
> I'd like to see it, yes. It'll probably require recursive route
> lookups.
>
> > Then I have a case to get OLSR patched (or do it myself) to not
> > enter pointless routes. Then, there will be interopability!
>
> Yes.
>
> > Anyway thanks for your patch. I will try it tomorrow. Which version
> > can I patch it on?
>
> It was against 0.99-CVS.
>
> regards,
> -- 
> Paul Jakma paul at clubi.ie paul at jakma.org Key ID: 64A2FF6A
> Fortune:
> NERVE GAS IS NOT A TOY
> NERVE GAS IS NOT A TOY
> NERVE GAS IS NOT A TOY
> NERVE GAS IS NOT A TOY
>
>   Bart Simpson on chalkboard in episode 2F32
> _______________________________________________
> Quagga-dev mailing list
> Quagga-dev at lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-dev
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Why-is-this-spam.txt
URL: <http://lists.quagga.net/pipermail/quagga-dev/attachments/20060512/1891d5b3/attachment-0001.txt>


More information about the Quagga-dev mailing list