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

Erik Tromp erik_tromp at hotmail.com
Mon May 8 08:15:57 BST 2006


Paul,

Thanks for your answer. However, I'm afraid it will not do. For two reasons:

1.) 10.0.3.3 *is* connected. Even though a kernel route to it also exists.
2.) After step 6. the route to 10.0.43.0 *is* active, but after step 10 is
it not. The configuration after step 6 is exactly the same as after the last
step, step 10.

I know that removing the static route to 10.0.3.3 may solve the problem,
however I cannot: that route is created by another routing protocol. And it
is a valid route.

Best Regards,
Erik


----- Original Message ----- 
From: "Paul Jakma" <paul at clubi.ie>
To: "Erik Tromp" <erik_tromp at hotmail.com>
Cc: <quagga-dev at lists.quagga.net>
Sent: Friday, May 05, 2006 6:02 PM
Subject: [quagga-dev 4120] Re: Inconsistent "inactive" route in OSPF


> On Fri, 5 May 2006, Erik Tromp wrote:
>
> >  root at OspfOlsrNode:/etc/rc2.d# ip route
> >  10.0.3.0/24 dev eth1  proto kernel  scope link  src 10.0.3.2
>
> > Step 10.)
> > Now, we add the route to host 10.0.3.3 *first*
> >
> >  root at OspfOlsrNode:/etc/rc2.d# route add -host 10.0.3.3 eth1
>
> >  10.0.3.3 dev eth1  scope link
> >  10.0.3.0/24 dev eth1  proto kernel  scope link  src 10.0.3.2
>
> >  C>* 10.0.3.0/24 is directly connected, eth1
> >  K>* 10.0.3.3/32 is directly connected, eth1
> >  C>* 10.0.42.0/24 is directly connected, eth2
>
> > Zebra says that is ok. We have a kernel route to host 10.0.3.3.
>
> > Now we add the static route to network 10.0.43.0/24 again.
> >
> >  OspfOlsrNode(config)# ip route 10.0.43.0/24 10.0.3.3
>
> >  C>* 10.0.3.0/24 is directly connected, eth1
> >  K>* 10.0.3.3/32 is directly connected, eth1
> >  C>* 10.0.42.0/24 is directly connected, eth2
> >  S   10.0.43.0/24 [1/0] via 10.0.3.3 inactive
> >                                      ^^^^^^^^
>
> > Why is this???
>
> Because the 10.0.43.0/24 static is via 10.0.3.3. The nexthop must
> resolve to a connected route for zebra to consider it valid. With the
> above, 10.0.3.3 matches the 'K>* 10.0.3.3/32' route.
>
> Remove that route, and the 10.0.3.3 nexthop will match 'C>*
> 10.0.3.0/24' and will work.
>
> regards,
> -- 
> Paul Jakma paul at clubi.ie paul at jakma.org Key ID: 64A2FF6A
> Fortune:
> After all, it is only the mediocre who are always at their best.
>   -- Jean Giraudoux
> _______________________________________________
> 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/20060508/10f26aed/attachment.txt>


More information about the Quagga-dev mailing list