[Xorp-users] xorp RIPng

[Pavlin Radoslavov]

> 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