[Xorp-hackers] Route with bad next-hop added with OSPF with redundant-link configuration.

[Atanu Ghosh]

Hi,

This problem is now fixed, thanks for the LSA dump it came in very useful.

1.292     +14 -11;  commitid: 3c75473a31087ea6; xorp/ospf/area_router.cc
1.18      +48 -2;  commitid: 1b2f473975667ea6;  xorp/libproto/spt.hh

	  Atanu.

>>>>> "Ben" == Ben Greear <greearb at candelatech.com> writes:

    Ben> Atanu Ghosh wrote:
    >> Hi,
    >> 
    >> If you think that routes are being incorrectly computed could you
    >> send me the LSA database as well as the routes that you expect to
    >> see.
    >> 
    >> The LSA database can be extracted with the print_lsas command.  $
    >> print_lsas -S saved.lsas
    >> 
    >> Atanu.
    >> 
    Ben> lsas are attached (for router 2).  I see these routes:

    Ben> [root at lf1016-55 lanforge]# ip route show table 10002
    Ben> 99.1.1.0/24 dev 2.3.2 scope link 10.2.2.0/24 dev eth2 scope
    Ben> link 10.1.1.0/24 via 10.1.2.2 dev 1.2.2 proto xorp metric 2
    Ben> notify 10.1.2.0/24 dev 1.2.2 scope link unreachable default
    Ben> proto xorp metric 1 notify

    Ben> I expect to see: [root at lf1016-55 lanforge]# ip route show table
    Ben> 10002 99.1.1.0/24 dev 2.3.2 scope link 10.2.2.0/24 dev eth2
    Ben> scope link 10.1.1.0/24 via 10.1.2.1 dev 1.2.2 proto xorp metric
    Ben> 2 notify ^^^^ 10.1.2.0/24 dev 1.2.2 scope link unreachable
    Ben> default proto xorp metric 1 notify


    Ben> Thanks, Ben

    Ben> -- Ben Greear <greearb at candelatech.com> Candela Technologies
    Ben> Inc http://www.candelatech.com