[Xorp-users] Bugs? recursive malloc, fib2mrib doesn't update nexthop vif, and PIM RP never initiates a Register-Stop

[Pavlin Radoslavov]

> > > > 2. XORP doesn't update its nexthop vif on multicast routing table If
> > > > Zebra updates a routing entry.
> > > >     show route table ipv6 multicast fib2mrib shows that the nexthop
> > > > vif is not  changed even though the nexthop address is.
> > > >   I am not sure whether this problem is intermittent or not.
> > >
> > > Can you trigger the same problem by using userland commands like
> > > "route delete" and "route add". If "yes", could you provide the
> > > sequence of those commands.
> > 
> > Here's the snippet of the ndp command on my router
> > fe80::2e0:81ff:fe20:afc2%fxp0        0:e0:81:20:af:c2    fxp0 16h26m32s S R
> > fe80::207:e9ff:fe05:ba6f%fxp1        0:7:e9:5:ba:6f      fxp1 17s       R R
> > 
> > a. after
> > route -n add -inet6 A:B:C:D::/64 fe80::2e0:81ff:fe20:afc2%fxp0
> > 
> > show pim6 mrib shows
> > A:B:C:D::/64 fe80::2e0:81ff:fe20:afc2 fxp0    0               254  65535
> > 
> > b. after
> > route -n change -inet6 A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f%fxp1
> > show pim6 mrib shows
> > A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f fxp0    0               254  65535
> > 
> > c. deleting the A:B:C:D::/64 and then
> > route -n add -inet6 A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f%fxp1
> > gives the same result
> > 
> > show pim6 mrib shows
> > A:B:C:D::/64 fe80::207:e9ff:fe05:ba6f fxp0    0               254  65535
> 
> Thank you for the info. I will look into that.

I think I found the bug. I believe it was triggered in certain cases.
E.g., one of the cases was when the next-hop is an IPv6 link-local
address that belongs to the router itself.

Now it should be fixed in CVS:

Revision  Changes                                Path
1.15      +116 -1;  commitid: 156da44e53f497ea6; xorp/libfeaclient/ifmgr_atoms.cc
1.24      +46 -1;  commitid: 156da44e53f497ea6; xorp/libfeaclient/ifmgr_atoms.hh
1.31      +11 -5;  commitid: 1595844e54db77ea6;  xorp/fib2mrib/fib2mrib_node.cc

Please let me know if you still have the problem.

Thanks,
Pavlin