[Xorp-users] xorp RIPng

[Pavlin Radoslavov]

<DEL>

> Appears though that the correct interface is sending out the ripng
> packets. Although I am seeing a metric of 16 here which should not be
> the case since its a connected network.
> 
> I'm attaching a file of the output of the trace since its quite long
> to paste here.

The trace output shows that the FEA has correctly identified vr0 as
the incoming interface for the RIPng packets:

[ 2007/11/19 03:33:55 INFO xorp_fea XRL ] Resolving xrl:finder://ripng-77422bcc5c4f8cc6087ec1f71328cb21@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000\000-0000058a-0004a5e5-03c70000&if_name:txt=vr0&vif_name:txt=vr0&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%02%01%00%00%00%00%00%00%0\0%00%00%00%00%00%00%00%00%00%00%00%00%00%00%FF+%01%0E%C0@%00%BE%EF%00%00%00%00%00%00%00%00%00%00@%00+%01%0E%C1@%01%10%AF%00%00%00%00%00%00%00%00%00%00@%10+%01\%0E%C2@%02%FA%11%00%00%00%00%00%00%00%00%00%00@%00

What is the output of the "show route table ipv6 unicast ripng"
xorpsh command?

I believe I have found the problem (RIPng doesn't send the interface
information along with the route it sends to the RIB so the RIB
mis-calculates the outgoing interface), but I'd like to cross-check
this with the "show route" output.

Thanks,
Pavlin