[Xorp-users] xorp RIPng
Hansi
hantongs at gmail.com
Tue Nov 13 01:25:21 PST 2007
Hello Pavlin,
See iniine responses.
On Nov 13, 2007 6:03 AM, Pavlin Radoslavov <pavlin at icir.org> wrote:
> Hansi <hantongs at gmail.com> wrote:
>
> > Hello All,
> >
> > I am currently trying to enable RIPNG on XORP and my network topology
> > is looks like this:
> > http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2007-November/002184.html
> > So far so good as I was able to configure RIPng on both XORP machines.
> > However, after "committing" the policy statement in order for networks
> > to be announced. I happen to encounter these logs messages.
> >
> > [ 2007/11/12 02:49:57 INFO xorp_rtrmgr:981 RTRMGR +2228 task.cc
> > run_task ] No more tasks to run
> > [ 2007/11/12 02:51:48 INFO xorp_rtrmgr:981 RTRMGR +96
> > module_manager.cc execute ] Executing module: rib (rib/xorp_rib)
> > [ 2007/11/12 02:51:50 INFO xorp_rtrmgr:981 RTRMGR +96
> > module_manager.cc execute ] Executing module: policy
> > (policy/xorp_policy)
> > [ 2007/11/12 02:51:52 INFO xorp_rtrmgr:981 RTRMGR +96
> > module_manager.cc execute ] Executing module: ripng (rip/xorp_ripng)
> > [ 2007/11/12 02:51:54 WARNING xorp_fea XrlFeaTarget ] Handling method
> > for socket6/0.1/set_socket_option failed: XrlCmdError 102 Command
> > failed Unknown socket option: multicast_hops
>
> This was because of a bug which is now fixed in CVS.
> Please get the latest code from anon CVS and try again.
> Also, I applied few more fixes so now you can run the "show ripng"
> xorpsh operational commands.
Yes, as of the current version downloaded from CVS. The output error
shown above is no longer present.
>
> > [ 2007/11/12 02:51:54 WARNING xorp_ripng XifSocket6 ] Failed to set
> > ttl/hops to 1
> > [ 2007/11/12 02:51:54 INFO xorp_rtrmgr:981 RTRMGR +2228 task.cc
> > run_task ] No more tasks to run
> > [ 2007/11/12 03:08:22 INFO xorp_rtrmgr:981 RTRMGR +2228 task.cc
> > run_task ] No more tasks to run
> > [ 2007/11/12 03:08:50 INFO xorp_rtrmgr:981 RTRMGR +2228 task.cc
> > run_task ] No more tasks to run
> > [ 2007/11/12 03:08:54 WARNING xorp_rtrmgr:981 XrlFinderTarget +406
> > ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> > method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
> > failed Xrl does not resolve:
> > finder://ripng/policy_redist4/0.1/add_route4
>
> Those warnings gets triggered because the RIB tries to export the IPv4
> connected routes to RIPng (which is IPv6-only protocol).
> In this particular case they should be harmless and can be ignored.
> Please try the following export statement to get rid of them:
>
> term export {
> from {
> protocol: "connected"
> network6 <= ::/0
>
> }
> }
>
> > [ 2007/11/12 03:08:54 WARNING xorp_rib RIB ] Unable to complete XRL:
> > add_route4 for ripng route: Dst: 172.16.0.0/16 Vif: sk0 NextHop:
> > NH:172.16.0.1 Metric: 0 Protocol: connected PolicyTags: 0
> > [ 2007/11/12 03:08:54 WARNING xorp_rtrmgr:981 XrlFinderTarget +406
> > ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> > method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
> > failed Xrl does not resolve:
> > finder://ripng/policy_redist4/0.1/add_route4
> > [ 2007/11/12 03:08:54 WARNING xorp_rib RIB ] Unable to complete XRL:
> > add_route4 for ripng route: Dst: 200.10.0.0/24 Vif: vr0 NextHop:
> > NH:200.10.0.1 Metric: 0 Protocol: connected PolicyTags: 0
> > [ 2007/11/12 03:08:54 WARNING xorp_rtrmgr:981 XrlFinderTarget +406
> > ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> > method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
> > failed Xrl does not resolve:
> > finder://ripng/policy_redist4/0.1/add_route4
> > [ 2007/11/12 03:08:54 WARNING xorp_rib RIB ] Unable to complete XRL:
> > add_route4 for ripng route: Dst: 172.16.0.0/16 Vif: sk0 NextHop:
> > NH:172.16.0.1 Metric: 0 Protocol: connected PolicyTags: 0
> > [ 2007/11/12 03:08:54 WARNING xorp_rtrmgr:981 XrlFinderTarget +406
> > ../xrl/targets/finder_base.cc handle_finder_0_2_resolve_xrl ] Handling
> > method for finder/0.2/resolve_xrl failed: XrlCmdError 102 Command
> > failed Xrl does not resolve:
> > finder://ripng/policy_redist4/0.1/add_route4
> > [ 2007/11/12 03:08:54 WARNING xorp_rib RIB ] Unable to complete XRL:
> > add_route4 for ripng route: Dst: 200.10.0.0/24 Vif: vr0 NextHop:
> > NH:200.10.0.1 Metric: 0 Protocol: connected PolicyTags: 0
> >
> > Furthermore, I'm unable to ping pc1 to pc2 and vice versa. No routes
> > were also added to the kernel routing table using netstat despite the
> > configuration being committed already.
> > Is there something I have overlooked in my configuration? appreciate
> > the assistance.
>
> Have in mind that in case of RIP/RIPng if you configure some policy
> you might need to wait some amount of time (e.g., 30 seconds) until
> the routes are (re)transmit.
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
05:06:26.394571 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:06:29.754415 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:06:56.394412 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:06:59.752328 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:07:26.394248 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:07:29.752277 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:07:56.394024 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:07:59.751233 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:08:26.394908 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:08:29.750188 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:08:56.394702 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:08:59.749315 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:09:26.394538 IP6 (hlim 1, next-header: UDP (17), length: 32)
fe80::213:d4ff:fed8:6808.521 > ff02::9.521: [udp sum ok] ripng-req
dump
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.
Regards,
Hansi
>
> You need to start debuging the problem by using the "show route" and
> "show ripng" commands, and by running tcpdump. The tcpdump output
> will tell you what is exchanged on the wire. If you see the IPv6
> routes being exchanged properly, then the "show ripng" and "show
> route" commands will tell you how far they got inside XORP.
>
> BTW, you can get rid of the "fib2mrib" and "plumbing/mfea6"
> configuration statements, because they are needed only for multicast
> routing.
>
> Regards,
> Pavlin
>
More information about the Xorp-users
mailing list