[Xorp-users] xorp RIPng

Hansi hantongs at gmail.com
Wed Nov 21 22:31:43 PST 2007


Hello Pavlin,

Thank you for the fix and accomodating this concern. :) Everything's
working smoothly now.

Regards,
Hansi
On Nov 21, 2007 6:40 PM, Pavlin Radoslavov <pavlin at icir.org> wrote:
> > > What is the output of the "show route table ipv6 unicast ripng"
> > > xorpsh command?
> >
> >
> > admin at demo_rtr.infoweapons.com> show route table ipv6 unicast ripng
> > 2001:ec0:4000:beef::/64 [rip(120)/1]
> >                 > to fe80::213:d4ff:fed8:6808 via sk0/sk0
> > 2001:ec1:4001:10af::/64 [rip(120)/1]
> >                 > to fe80::213:d4ff:fed8:6808 via sk0/sk0
> >
> > This status output was taken from Router 2. Link-local address
> > fe80::213:d4ff:fed8:6808 is the vr0 interface of Router1. So I believe
> > it should be vr0 instead of the one shown above.
> >
> > Output of show route table ipv6 unicast ripng from Router 1:
> >
> > admin at demo_rtr.infoweapons.com> show route table ipv6 unicast ripng
> > 2001:ec2:4002:fa11::/64 [rip(120)/1]
> >                 > to fe80::215:f2ff:fe3d:ac91 via sk0/sk0
> >
> >
> > Thanks,
> > Hansi
> > >
> > > 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.
>
> Thank you for the info.
> I just committed a fix to CVS. Please let me know whether the latest
> code fixes the problem for you.
>
> Thanks,
> Pavlin
>



More information about the Xorp-users mailing list