[Xorp-users] xorp RIPng

Hansi hantongs at gmail.com
Sun Nov 18 23:36:47 PST 2007


Hello Pavlin,

Here's the output taken from tcpdump:

e3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-req dump
07:31:50.929298 IP6 (hlim 1, next-header: UDP (17), length: 32)
fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-req
dump
07:32:20.929740 IP6 (hlim 1, next-header: UDP (17), length: 32)
fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-req
dump
07:32:29.944286 IP6 (hlim 1, next-header: UDP (17), length: 72)
fe80::213:d4ff:fed8:6808.521 > ff02::9.521: [udp sum ok]  ripng-resp
3:
        ::/0 (255)
        2001:ec0:4000:beef::/64
        2001:ec1:4001:10af::/64
07:32:31.871290 IP6 (hlim 1, next-header: UDP (17), length: 92)
fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-resp
4:
        ::/0 (255)
        2001:ec0:4000:beef::/64
        2001:ec2:4002:fa11::/64
        2001:ec1:4001:10af::/64 (16)
07:32:32.122065 IP6 (hlim 1, next-header: UDP (17), length: 52)
fe80::213:d4ff:fed8:6808.521 > ff02::9.521: [udp sum ok]  ripng-resp
2:
        ::/0 (255)
        2001:ec2:4002:fa11::/64 (16)
07:32:50.496254 IP6 (hlim 1, next-header: UDP (17), length: 92)
fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-resp
4:
        ::/0 (255)
        2001:ec0:4000:beef::/64
        2001:ec1:4001:10af::/64 (16)
        2001:ec2:4002:fa11::/64
07:33:21.618279 IP6 (hlim 1, next-header: UDP (17), length: 92)
fe80::213:d4ff:fed8:6808.521 > ff02::9.521: [udp sum ok]  ripng-resp
4:
        ::/0 (255)
        2001:ec0:4000:beef::/64
        2001:ec1:4001:10af::/64
        2001:ec2:4002:fa11::/64 (16)
07:33:24.255844 IP6 (hlim 1, next-header: UDP (17), length: 92)
fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-resp
4:
        ::/0 (255)
        2001:ec0:4000:beef::/64
        2001:ec1:4001:10af::/64 (16)
        2001:ec2:4002:fa11::/64
07:33:50.167961 IP6 (hlim 1, next-header: UDP (17), length: 92)
fe80::213:d4ff:fed8:6808.521 > ff02::9.521: [udp sum ok]  ripng-resp
4:
        ::/0 (255)
        2001:ec0:4000:beef::/64
        2001:ec1:4001:10af::/64
        2001:ec2:4002:fa11::/64 (16)
07:33:52.804191 IP6 (hlim 1, next-header: UDP (17), length: 92)
fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-resp
4:
        ::/0 (255)
        2001:ec0:4000:beef::/64
        2001:ec1:4001:10af::/64 (16)
        2001:ec2:4002:fa11::/64

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.

Thanks,
Hansi



On Nov 19, 2007 2:16 PM, Pavlin Radoslavov <pavlin at icir.org> wrote:
> >    The CVS code downloaded from the XORP CVS repository still exhibits
> > the same bug issue. The wrong interface is still being used as the
> > incoming interface as seen using netstat.
>
> Please enable again the XRLTRACE environmental variable and send me
> the log output. This will help finding whether the problem is in
> the FEA or RIP.
>
> Also, please run tcpdump on both interface to double-check that the
> RIPng packet is indeed coming on the expected interface.
>
> Thanks,
> Pavlin
>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xrltrace.txt
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071119/3fd1fd13/attachment-0001.txt 


More information about the Xorp-users mailing list