[Unstrung-hackers] unable to see routes with sunshine on b2b connected nodes

Vijay Anand R (vanandr) vjanandrgky at gmail.com
Tue Sep 22 11:57:00 EDT 2015


Hi,

I am trying to evaluate unstrung implementation of RPL for one of my 
projects. Please note my target platform is a 64bit linux ubuntu 
machine, so I made some changes to the build-setup-travis.sh script and 
some changes to the Makefile.inc to get a clean build.

The below is a simple topology I started of with:

SNBI-TB-A  eth1 =============== eth1 SNBI-TB-B
(Root Rank-1)
TB-A has a dummy interface (SNBI-FE) with an IPV6 ULA address assigned: 
fd6a:fbaa:36f9:4141:3a42:423a:3
Similarly TB-B has dummy interface (SNBI-FE) with an IPv6 ULA 
fd6a:fbaa:36f9:0:4141:3a42:423a:2.

I want to advertise the IPV6 ULA addresses, and bring up the RPL daemon 
in storing mode on both the test beds.
Also please note I am trying to build a DODAG based on OF0 as defined by 
RFC 6552.

Based on the above requirements and from the documentation I tried the 
below configs.

*TB-A
====
*sudo sunshine --dagid fd6a:fbaa:36f9:4141:3a42:423a:3 -I 0 -i eth1 
--syslog --verbose --prefix fd6a:fbaa:36f9:0:4141:3a42:423a:3/128 --rank 1

Also please note in the DIO messages I see the dagID as "fd6a:fbaa:36f9:4".

*TB-B
====
*sudo sunshine --dagid fd6a:fbaa:36f9:1:4141:3a42:423a:2 -I 0 -i eth1 
--syslog --verbose --prefix fd6a:fbaa:36f9:0:4141:3a42:423a:2/128*
*
Also I went thru RFC6550 and it says that the DAGID is the unique 
identifier for the root. But sunshine mandates that I give the dagid 
every time even though there is already a root with a specific dagid 
(TB-A). So will TB-B be considered another root of a separate DODAG 
different from TB-A ?

I checked the routes on both the devices, but I dont see the ULA address 
routes. Can anyone point to me what I might be missing here ?

Please see below show outputs :

[snbi-tb-a:/var/log]
516 => ifconfig SNBI-FE
SNBI-FE   Link encap:Ethernet  HWaddr 82:15:b7:1d:ea:33
           inet6 addr: fe80::8015:b7ff:fe1d:ea33/64 Scope:Link
           inet6 addr: fd6a:fbaa:36f9:0:4141:3a42:423a:3/128 Scope:Global
           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

[snbi-tb-a:/var/log]
517 => ip -6 route show
2001:db8::/64 dev eth0  proto kernel  metric 256
fd08:2eef:c2ee:0:aabb:cc00:c900:1 dev eth1  proto kernel  metric 256
fd08:2eef:c2ee:0:aabb:cc00:c900:2 dev eth2  proto kernel  metric 256
fd08:2eef:c2ee:0:aabb:cc00:c900:3 dev eth1  proto zebra  metric 1
fd08:2eef:c2ee:0:aabb:cc00:c900:4 via fe80::20c:29ff:fe62:267f dev eth1  
proto zebra  metric 2
unreachable fd6a:fbaa:36f9:0:20c:29ff:fee8:a5dc dev lo  proto kernel  
metric 256  error -101
fd6a:fbaa:36f9:0:4141:3a42:423a:3 dev SNBI-FE  proto kernel  metric 256
unreachable fd6a:fbaa:36f9:0:4141:3a42:423a:3 dev lo  metric 1024 error -101
fe80::/64 dev eth2  proto kernel  metric 256
fe80::/64 dev eth1  proto kernel  metric 256
fe80::/64 dev eth0  proto kernel  metric 256
fe80::/64 dev SNBI-FE  proto kernel  metric 256


[snbi-tb-b:~]
326 => ifconfig SNBI-FE
SNBI-FE   Link encap:Ethernet  HWaddr 3e:3f:12:d1:02:58
           inet6 addr: fd6a:fbaa:36f9:0:4141:3a42:423a:2/128 Scope:Global
           inet6 addr: fe80::3c3f:12ff:fed1:258/64 Scope:Link
           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

[snbi-tb-b:~]
327 => ifconfig SNBI-FE^C
[snbi-tb-b:~]
327 => ip -6 route show
2001:420:54ff:4::402:0/119 dev eth0  proto kernel  metric 256 expires 
2591906sec
fd08:2eef:c2ee:0:aabb:cc00:c900:1 dev eth1  proto zebra  metric 1
fd08:2eef:c2ee:0:aabb:cc00:c900:2 via fe80::20c:29ff:fee8:a5dc dev eth1  
proto zebra  metric 2
fd08:2eef:c2ee:0:aabb:cc00:c900:3 dev eth1  proto kernel  metric 256
fd08:2eef:c2ee:0:aabb:cc00:c900:4 dev eth2  proto kernel  metric 256
unreachable fd6a:fbaa:36f9:0:20c:29ff:fe62:2675 dev lo  proto kernel  
metric 256  error -101
unreachable fd6a:fbaa:36f9:0:20c:29ff:fe62:267f dev lo  proto kernel  
metric 256  error -101
fd6a:fbaa:36f9:0:4141:3a42:423a:2 dev SNBI-FE  proto kernel  metric 256
unreachable fd6a:fbaa:36f9:0:4141:3a42:423a:2 dev lo  metric 1024 error -101
fe80::/64 dev eth1  proto kernel  metric 256
fe80::/64 dev eth2  proto kernel  metric 256
fe80::/64 dev eth0  proto kernel  metric 256
fe80::/64 dev SNBI-FE  proto kernel  metric 256
default via fe80::5:73ff:fea0:57a dev eth0  proto ra  metric 1024 
expires 1706sec
default via fe80::21b:2bff:fef6:8680 dev eth0  proto ra  metric 1024  
expires 1695sec

[snbi-tb-b:~]
329 => ping6 fd6a:fbaa:36f9:0:4141:3a42:423a:2
PING 
fd6a:fbaa:36f9:0:4141:3a42:423a:2(fd6a:fbaa:36f9:0:4141:3a42:423a:2) 56 
data bytes
64 bytes from fd6a:fbaa:36f9:0:4141:3a42:423a:2: icmp_seq=1 ttl=64 
time=0.056 ms
64 bytes from fd6a:fbaa:36f9:0:4141:3a42:423a:2: icmp_seq=2 ttl=64 
time=0.058 ms


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sandelman.ca/pipermail/unstrung-hackers/attachments/20150922/1c32a6d1/attachment.html>


More information about the Unstrung-hackers mailing list