<div dir="ltr"><div>I would thought so too. Well, that's a bummer. CC'ing mailing list, maybe someone will be able to contribute. Thanks for the feedback. <br><br></div>Pawel<br></div><div class="gmail_extra"><br><br>
<div class="gmail_quote">2014-05-28 0:35 GMT+02:00 Avinash Sridharan <span dir="ltr"><<a href="mailto:avinash.sridharan@gmail.com" target="_blank">avinash.sridharan@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">If OSPFv3 works, then I suspect there could be a bug in the RIPng code. I am not sure if this piece of code has been tested well enough. I am not a developer of XORP (at least not yet), so can't make any concrete claims here, but it does look a bit odd that R3 is not learning the <span style="font-family:'courier new',monospace;font-size:12.727272033691406px">:3B87/64 network from R1. </span></div>
<div class="HOEnZb"><div class="h5">
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, May 27, 2014 at 3:07 PM, Paweł Sroczyński <span dir="ltr"><<a href="mailto:leniwiec16@gmail.com" target="_blank">leniwiec16@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Nobody has any idea at all? I should have mentioned that at the same time ospfv3 works just fine. So it can't be problem with topology or hardware configuration.<br>
<br></div>Regards,<br></div>
Pawel<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-22 0:44 GMT+02:00 Paweł Sroczyński <span dir="ltr"><<a href="mailto:leniwiec16@gmail.com" target="_blank">leniwiec16@gmail.com</a>></span>:<div>
<div><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>What I meant is that R2 can't ping R3. I followed your advice to not add eth2::1 if of R2 and eth2::2 if of R3 to XORP so the topology look like that:<br>
<br><span style="font-family:courier new,monospace"> eth1::2 </span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">eth1|::1</span> </span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">eth1::1 eth1::2</span><br>
R2</span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">+</span></span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">---------</span></span>----------------</span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">+</span></span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">R1+----------------------+R3</span> <br>
</span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">:3B87/64</span> </span><span style="font-family:courier new,monospace"><span style="font-family:courier new,monospace">:2CA1/64</span>
<br></span><br></div><div>ripng-resp for <span style="font-family:arial,sans-serif;font-size:12.7273px">fdb0:777:4dce:2ca1::/64 which R3 receives is from R1. To me it seems that </span><span style="font-family:arial,sans-serif;font-size:12.7273px"><span style="font-family:arial,sans-serif;font-size:12.7273px">R1 doesn't advertise fdb0:777:4dce:3B87::/64</span> to R3 for some reason. <br>
<br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.7273px">Pawel<br></span></div><div><span style="font-family:arial,sans-serif;font-size:12.7273px"><br><br></span></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2014-05-22 0:30 GMT+02:00 Avinash Sridharan <span dir="ltr"><<a href="mailto:avinash.sridharan@gmail.com" target="_blank">avinash.sridharan@gmail.com</a>></span>:<div><div>
<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">I don't understand, <div>From your description it seems like there is no connectivity between R2 and R3 (though your figure shows there is), so why are you expecting messages from R2? The network should be exported by R1 to R3. Are you getting any messages from R1? The only messages that R3 seems to be getting are the ripng-resp for <span style="font-family:arial,sans-serif;font-size:12.7273px">) fdb0:777:4dce:2ca1::/64 . Is this coming from R1?</span></div>
<span><font color="#888888">
<div><br></div><div>-Avinash</div></font></span></div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 21, 2014 at 3:13 PM, Paweł Sroczyński <span dir="ltr"><<a href="mailto:leniwiec16@gmail.com" target="_blank">leniwiec16@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>Hi Avinash, <br><br></div>Thanks for your reply. I didn't know about the "ip link" command, quite useful one. All interfaces are up and running. <br>
<br></div>I did the test you proposed. There is no connectivity between R2 and R3 eth1 interface. R2 has learned the route to fdb0:777:4dce:2ca1::/64 network but R3 didn't learned the route to fdb0:777:4dce:3b87::/64. So the last interface which responds to ping from R2 is R1 eth2 (fdb0:777:4dce:2ca1::1). <br>
<br>tcpdump on R1 eth2:<br>root@router:~# tcpdump -i eth2<br>tcpdump: WARNING: eth2: no IPv4 address assigned<br>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes<br>
00:02:58.694024 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-resp 2: ::/0 (255) fdb0:777:4dce:2ca1::/64<br>00:03:00.851341 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-req dump<br>00:03:29.931314 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-resp 2: ::/0 (255) fdb0:777:4dce:2ca1::/64<br>
00:03:30.851452 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-req dump<br><br>tcpdump on R3 eth1:<br>root@router:~# tcpdump -i eth1<br>tcpdump: WARNING: eth1: no IPv4 address assigned<br>tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes<br>00:03:29.930363 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-resp 2: ::/0 (255) fdb0:777:4dce:2ca1::/64<br>00:03:30.850598 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-req dump<br>
00:04:00.851172 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-req dump<br>00:04:02.271207 IP6 fe80::a00:27ff:fea3:ff3e.521 > ff02::9.521: ripng-resp 2: ::/0 (255) fdb0:777:4dce:2ca1::/64<br><br></div><div>
Any ideas? <br></div><div><br></div>Pawel<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-21 23:35 GMT+02:00 Avinash Sridharan <span dir="ltr"><<a href="mailto:avinash.sridharan@gmail.com" target="_blank">avinash.sridharan@gmail.com</a>></span>:<div>
<div><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Without adding the eth2::1 interface of R2 and eth2::2 interface of R3 to XORP , can you test the connectivity between R2 and R3 in linux. Also, once you have configured the interfaces in XORP you can "ip link" on linux shell to verify the addresses configured on the specific interfaces to make sure that they are up and configured correctly in the linux kernel. <div>
<br></div><div>-Avinash</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Wed, May 21, 2014 at 2:13 PM, Paweł Sroczyński <span dir="ltr"><<a href="mailto:leniwiec16@gmail.com" target="_blank">leniwiec16@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><div dir="ltr"><div><div><div><div><div><div><div><div><span style="font-family:courier new,monospace">Hi All, <br>
</span></div>
<span style="font-family:courier new,monospace">I'm trying to configure RIPng in a simple 3 router topology without success. I'm using XORP 1.8.5 installed on the latest stable Debian version 7.5. Network is as follows:<br>
<br> First 48bit of each subnet are: <br> FDB0:777:4DCE::/48 <br> <br> eth1::2 eth2::1 <br> +---------+R2+-----------+ <br> | | <br> | | <br>
| | <br> |:3B87/64 |:888/64<br> | | <br> | | <br>eth1|::1 :2CA1/64 +eth2::2<br> R1+----------------------+R3 <br>
eth1::1 eth1::2 <br><br></span></div><span style="font-family:courier new,monospace">Sorry for bad ASCII.<br><br></span></div><span style="font-family:courier new,monospace">The problem I encountered is that after launching XORP on each router only R1 and R2 have complete routing table.<br>
<br>Route table on R1:<br>student@router> show route table ipv6 unicast final<br>fdb0:777:4dce:888::/64 [rip(120)/1]<br> > to fe80::a00:27ff:feb1:9514 via eth1/eth1<br>fdb0:777:4dce:2ca1::/64 [connected(0)/0]<br>
> via eth2/eth2<br>fdb0:777:4dce:3b87::/64 [connected(0)/0]<br> > via eth1/eth1<br>fe80::/64 [connected(0)/0]<br> > via eth1/eth1<br><br>Route table on R2:<br>
student@router> show route table ipv6 unicast final<br>
fdb0:777:4dce:888::/64 [connected(0)/0]<br> > via eth2/eth2<br>fdb0:777:4dce:2ca1::/64 [rip(120)/1]<br> > to fe80::a00:27ff:fe4d:c528 via eth1/eth1<br>fdb0:777:4dce:3b87::/64 [connected(0)/0]<br>
> via eth1/eth1<br>fe80::/64 [connected(0)/0]<br> > via eth1/eth1<br>Route table on R3:<br>student@router> show route table ipv6 unicast final<br>fdb0:777:4dce:888::/64 [connected(0)/0]<br>
> via eth2/eth2<br>fdb0:777:4dce:2ca1::/64 [connected(0)/0]<br> > via eth1/eth1<br>fe80::/64 [connected(0)/0]<br> > via eth1/eth1<br><br></span></div><span style="font-family:courier new,monospace">I've run tcpdump on each interface and it seems there is absolutely nothing going on on R2<->R3 link. Why is that is beyond my comprehension. I also enabled traceoptions, you can see results below:<br>
R1:<br>[ 2014/05/21 22:41:09.941083 TRACE xorp_ripng RIP ] adding RIB route fdb0:777:4dce:2ca1::/64<br>[ 2014/05/21 22:41:09.941529 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:2ca1::/64<br>[ 2014/05/21 22:41:09.941575 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:2ca1::/64<br>
[ 2014/05/21 22:41:09.941691 TRACE xorp_ripng RIP ] adding RIB route fdb0:777:4dce:3b87::/64<br>[ 2014/05/21 22:41:09.941742 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:3b87::/64<br>[ 2014/05/21 22:41:09.941773 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:3b87::/64<br>
[ 2014/05/21 22:41:19.610982 TRACE xorp_ripng RIP ] Packet on 7f000101-00005c1f-0000bd2f-0e680000 from interface eth1 vif eth1 fe80::a00:27ff:feb1:9514/521 24 bytes<br><br><br>R2:<br>[ 2014/05/21 22:41:19.613244 TRACE xorp_ripng RIP ] Packet on 7f000101-00005bf4-00057451-0b880000 from interface eth1 vif eth1 fe80::a00:27ff:fe4d:c528/521 64 bytes<br>
[ 2014/05/21 22:41:19.613527 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:2ca1::/64<br>[ 2014/05/21 22:41:19.613551 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:2ca1::/64<br>
[ 2014/05/21 22:41:19.613579 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:3b87::/64<br>[ 2014/05/21 22:41:19.613593 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:3b87::/64<br>
[ 2014/05/21 22:41:19.634655 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:2ca1::/64<br>[ 2014/05/21 22:41:19.634693 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:2ca1::/64<br>
[ 2014/05/21 22:41:19.634721 TRACE xorp_ripng RIP ] Was filtered: 0, Accepted: 1<br>[ 2014/05/21 22:41:19.634735 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:3b87::/64<br>[ 2014/05/21 22:41:19.634748 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:3b87::/64<br>
[ 2014/05/21 22:41:21.637290 TRACE xorp_ripng RIP ] Was filtered: 0, Accepted: 1<br>[ 2014/05/21 22:41:21.642894 TRACE xorp_ripng RIP ] adding RIB route fdb0:777:4dce:888::/64<br>[ 2014/05/21 22:41:21.643075 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:888::/64<br>
[ 2014/05/21 22:41:21.643115 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:888::/64<br>[ 2014/05/21 22:41:21.643178 TRACE xorp_ripng RIP ] adding RIB route fdb0:777:4dce:3b87::/64<br>[ 2014/05/21 22:41:21.643214 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:3b87::/64<br>
[ 2014/05/21 22:41:21.643242 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:3b87::/64<br>[ 2014/05/21 22:41:56.522666 TRACE xorp_ripng RIP ] Packet on 7f000101-00005bf4-00057451-0b880000 from interface eth1 vif eth1 fe80::a00:27ff:fe4d:c528/521 44 bytes<br>
<br><br>R3:<br> 2014/05/21 22:41:27.245528 TRACE xorp_ripng RIP ] adding RIB route fdb0:777:4dce:888::/64<br>[ 2014/05/21 22:41:27.245866 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:888::/64<br>[ 2014/05/21 22:41:27.245907 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:888::/64<br>
[ 2014/05/21 22:41:27.246016 TRACE xorp_ripng RIP ] adding RIB route fdb0:777:4dce:2ca1::/64<br>[ 2014/05/21 22:41:27.246057 TRACE xorp_ripng RIP ] Running import filter on route fdb0:777:4dce:2ca1::/64<br>[ 2014/05/21 22:41:27.246085 TRACE xorp_ripng RIP ] Running source match filter on route fdb0:777:4dce:2ca1::/64<br>
<br></span></div><span style="font-family:courier new,monospace">Configuration on each router is parallel to this one:<br><br>interfaces {<br> restore-original-config-on-shutdown: true<br> interface eth1 {<br> description: "link between R1 and R2"<br>
disable: false<br> vif eth1 {<br> disable: false<br> address FDB0:777:4DCE:3B87::1 {<br> prefix-length: 64<br> disable: false<br> }<br> address fe80::a00:27ff:fe4d:c528 {<br>
prefix-length: 64<br> disable: false<br> } <br> }<br> }<br> interface eth2 {<br> description: "link between R1 and R3"<br> disable: false<br>
vif eth2 {<br> disable: false<br> address FDB0:777:4DCE:2CA1::1 {<br> prefix-length: 64<br> disable: false<br> }<br> address fe80::a00:27ff:febe:336e {<br>
prefix-length: 64<br> disable: false<br> } <br> }<br> }<br>}<br><br>fea {<br> unicast-forwarding6 {<br> disable: false<br> }<br>}<br><br>policy {<br>
policy-statement export-connected {<br> term export {<br> from {<br> protocol: "connected"<br> network6 <= ::/0<br> }<br> }<br> }<br>}<br>
<br>protocols {<br> ripng {<br> export: "export-connected"<br> interface eth1 {<br> vif eth1 {<br> address fe80::a00:27ff:fe4d:c528 {<br> disable: false<br>
}<br> }<br> }<br> interface eth2 {<br> vif eth2 {<br> address fe80::a00:27ff:febe:336e {<br> disable: false<br> }<br> }<br>
}<br> traceoptions {<br> flag all {<br> disable: false<br> }<br> } <br> }<br>} <br><br></span></div><span style="font-family:courier new,monospace">I've double and triple-checked all the link-local addresses etc. so addressing should be fine. Why R3 is not participating in the route exchange process as it's supposed to?<br>
<br></span></div><span style="font-family:courier new,monospace">I will greatly appreciate any help to find the root of the problem. <br><br></span></div><span style="font-family:courier new,monospace">Thanks and regards,<br>
Pawel<br></span></div>
<br></div></div>_______________________________________________<br>
Xorp-users mailing list<br>
<a href="mailto:Xorp-users@xorp.org" target="_blank">Xorp-users@xorp.org</a><br>
<a href="http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users" target="_blank">http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div></div></div><br></div></div>
</blockquote></div></div></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>