[Xorp-users] xorp RIPng

Hansi hantongs at gmail.com
Wed Nov 14 00:44:30 PST 2007 

Hello Pavlin,

Replacing the global address with the link-local IPv6 address provides
the same results. No peerings between two XORP machines w/ RIPng
enabled are established. Attached is the configuration file used.

Also, I managed to do a trace as you instructed to:

2:33:20<root at demo_rtr :/usr/local/xorp/bin>)#less typescript | grep
"socket6_user"
"typescript" may be a binary file.  See it anyway? y

[ 2007/11/14 02:28:57 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:28:57 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:28:57 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:29:27 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:29:27 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:29:27 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:29:57 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:29:57 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:29:57 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:30:27 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:30:27 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:30:27 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:30:57 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:30:57 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:30:57 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:31:27 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:31:27 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:31:27 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:31:57 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:31:57 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:31:57 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:32:27 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:32:27 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:32:27 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
[ 2007/11/14 02:32:57 INFO xorp_fea XRL ] Resolving
xrl:finder://ripng-775637ed507ee002ab82dd3f24333ee1@127.0.0.1/socket6_user/0.1/recv_event?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:32:57 INFO xorp_fea XRL ] Sending
stcp://127.0.0.1:49674/socket6_user/0.1/recv_event-10be5b2055e768a3?sockid:txt=00000000-000032e1-000ab21c-063b0000&src_host:ipv6=fe80::215:f2ff:fe3d:ac91&src_port:u32=521&data:binary=%01%01%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%00%10
[ 2007/11/14 02:32:57 INFO xorp_ripng IPC ] dispatch_xrl (valid)
socket6_user/0.1/recv_event
(2:33:27<root at demo_rtr :/usr/local/xorp/bin>)#

I don't know how to interpret these log messages. Perhaps you could help. :)

I did a ping to the all-ripv6 routers multicast address ff02::9 just
to double check:

$ ping6 -I vr0 ff02::9
PING6(56=40+8+8 bytes) fe80::213:d4ff:fed8:6808%vr0 --> ff02::9
16 bytes from fe80::213:d4ff:fed8:6808%vr0, icmp_seq=0 hlim=64 time=0.192 ms
16 bytes from fe80::215:f2ff:fe3d:ac91%vr0, icmp_seq=0 hlim=64
time=0.254 ms(DUP!)
16 bytes from fe80::213:d4ff:fed8:6808%vr0, icmp_seq=1 hlim=64 time=0.112 ms
16 bytes from fe80::215:f2ff:fe3d:ac91%vr0, icmp_seq=1 hlim=64
time=0.232 ms(DUP!)
16 bytes from fe80::213:d4ff:fed8:6808%vr0, icmp_seq=2 hlim=64 time=0.107 ms
16 bytes from fe80::215:f2ff:fe3d:ac91%vr0, icmp_seq=2 hlim=64
time=0.228 ms(DUP!)
16 bytes from fe80::213:d4ff:fed8:6808%vr0, icmp_seq=3 hlim=64 time=0.122 ms
16 bytes from fe80::215:f2ff:fe3d:ac91%vr0, icmp_seq=3 hlim=64
time=0.252 ms(DUP!)
16 bytes from fe80::213:d4ff:fed8:6808%vr0, icmp_seq=4 hlim=64 time=0.105 ms
16 bytes from fe80::215:f2ff:fe3d:ac91%vr0, icmp_seq=4 hlim=64
time=0.226 ms(DUP!)
16 bytes from fe80::213:d4ff:fed8:6808%vr0, icmp_seq=5 hlim=64 time=0.105 ms
16 bytes from fe80::215:f2ff:fe3d:ac91%vr0, icmp_seq=5 hlim=64
time=0.219 ms(DUP!)

Attached is my xorp config file.

Regards,
Hansi

On Nov 13, 2007 11:44 PM, Pavlin Radoslavov <pavlin at icir.org> wrote:
> > Yes. RIP takes 30 seconds to transmit a packet to a multicast ipv6
> > address. The problem though here is that XORP seems to transmit
> > forever without any peering established. :( All I am seeing are RIP
> > request packets being transmitted by both XORP machines. Correct me if
> > I'm wrong but isn't it supposed to be that if a RIP peering is
> > established, the dump from the network would show an exchange of RIP
> > request and response messages? I'm not seeing any response messages in
> > this case even when RIPng is already enabled in both XORP machines..
> >
> > Shown below is the tcpdump output:
> >
> > 05:05:26.395302 IP6 (hlim 1, next-header: UDP (17), length: 32)
> > fe80::213:d4ff:fed8:6808.521 > ff02::9.521: [udp sum ok]  ripng-req
> > dump
> > 05:05:29.755473 IP6 (hlim 1, next-header: UDP (17), length: 32)
> > fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-req
> > dump
> > 05:05:56.394739 IP6 (hlim 1, next-header: UDP (17), length: 32)
> > fe80::213:d4ff:fed8:6808.521 > ff02::9.521: [udp sum ok]  ripng-req
> > dump
> > 05:05:59.754388 IP6 (hlim 1, next-header: UDP (17), length: 32)
> > fe80::215:f2ff:fe3d:ac91.521 > ff02::9.521: [udp sum ok]  ripng-req
> > dump
>
> <DEL>
>
> >
> > The XORP box seems to listen on port 521 though:
> >
> > $ sockstat -6l
> > USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
> > root     xorp_fea   43829 20 udp6   *:*                   *:*
> > root     xorp_fea   43829 39 udp6   *:521                 *:*
> > root     sshd       790   3  tcp6   *:22                  *:*
> > root     syslogd    640   6  udp6   *:514                 *:*
> >
> > Issuing "show ripng peer statistics all" would yield:
> >
> > admin at demo_rtr.infoweapons.com> show ripng peer statistics all
> > There are no known peers.
> >
> > Could I have overlooked something in this configuration? I'm certain
> > that this is also the procedures I took on how I was able to enable
> > RIPv2 and everything worked fine. Hope you could shed some light on
> > this matter.
>
> The only thing that comes to mind is to try to use the interface's
> IPv6 link-local address instead of the global address (inside the
> RIPng config).
>
> If this has no impact, then enable the XRLTRACE environmental
> variable before starting XORP and save the terminal output to a
> file. E.g., in csh/tcsh:
>
> setenv XRLTRACE yes
> script
> ./xorp_rtrmgr -b config.boot
> ...
> Ctrl-C
> exit
>
> This will save the output in file named "typescript".
> Check inside that file for "socket6_user" XRLs from the FEA to
> RIPng. This will tell you whether the FEA actually received the
> RIPng packets and sent them to the RIPng.
> Also, if you saw any warning/error messages from RIPng itself this
> could be useful.
>
> Regards,
> Pavlin
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: "
Type: application/octet-stream
Size: 3280 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-users/attachments/20071114/1556188a/attachment.obj

More information about the Xorp-users mailing list