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

List:       zebra
Subject:    [zebra 11026] Re: First Time to ospf  (Long mail)
From:       bino () indoakses-online ! com
Date:       2001-10-31 11:47:14
[Download RAW message or body]

Dear All.

On Wed, 31 October 2001, Stephane Bortzmeyer wrote:
> On Wed, Oct 31, 2001 at 02:37:13AM -0800,
>  bino@indoakses-online.com <bino@indoakses-online.com> wrote 
>  a message of 14 lines which said:
> 
> > I did it from RTR-A ... So the shortest path to 172.17.1.1 (RTR-C
> > Eth1) is via 192.168.1.1 (RTR-C eth0).
> 
> How could OSPF know it? Both RTR-B and RTR-C announce
> 172.17.1.0/24. OSPF cannot use other informations than its
> configuration file :-)

 Yes, Both RTR-B and RTR-C announce 172.17.1.0/24
So .. using "sh ip ospf route" in RTR-A i can get :

ospfd-a# sh ip ospf route
============ OSPF network routing table ============
N    10.1.1.0/24           [10] area: 0.0.0.0
                           directly attached to eth0
N IA 172.17.1.0/24         [20] area: 0.0.0.0
                           via 10.1.1.1, eth0
                           via 192.168.1.1, eth1

It's Clear.
But why when I do "ip route" from RTR-A Shell
RTR-A# ip route
192.168.0.0/28 dev eth2  proto kernel  scope link  src 192.168.0.8 
192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.254 
10.1.1.0/24 dev eth0  proto kernel  scope link  src 10.1.1.254 
172.17.1.0/24 via 10.1.1.1 dev eth0  proto zebra  metric 20 

I just get 1 path to 172.17.1.0/24 ... why not 2 path ?

sincerely
-bino-

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