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

Vijay Anand R vjanandrgky at gmail.com
Thu Sep 24 13:28:12 EDT 2015

Hi Michael,

To give a quick brief background on what I am trying to do.
I am working on an open source version of autonomic networking, and 
trying to explore if RPL is the best choice of routing protocol.
RPL is of interest to us because we have to setup the routing only for 
the control plane traffic of autonomic networking and we prefer a light 
weight routing infrastructure.

Regarding the PIO : I think that could be optional since each node would 
get a /128 ULA address from Autonomic Networking infrastructure. The 
goal now is to use a routing protocol to advertise the routes to these 
ULA addresses.

Here are some thoughts regarding the input to sunshine, kindly let me 
know what you think.

a. Providing a CIDR in the command line is certainly a possibility but 
the ULA address assigned are always /128 prefix and except for the first 
byte of FD rest 15 bytes are generated by some rules.
b. Further addition of interfaces within a node to the DODAG is dynamic, 
so the only current alternative seems to be kill the current instance 
and start a new one with the new set of interfaces in the command line 
(with the -i option).  This seems to be destructive and could impair 
routing to current reachable nodes. But I agree once we have this 
integrated into Quagga we get a CLI prompt we can work with. But in the 
interim do you think having a configuration file would help ? I update 
the configuration file and send a signal to sunshine daemon for it to 
gracefully restart with the new configuration ?


On 9/24/2015 1:19 AM, Michael Richardson wrote:
> Vijay Anand R <vjanandrgky at gmail.com> wrote:
>      > a. Should be able to advertise a specific IPv6 address (/128) assigned to a
>      > loopback or dummy interface on a node.
> okay, that's possible to do, but not coded.
> How would you like to specify this?   Yes, it could be specified on the
> command line, but that isn't that flexible.  Would you want to announce
> any address that matched some CIDR (which you'd put on the command line),
> or??
>      > The RPL instance (sunshine) is running on the same node, so I am not trying
>      > to proxy advertise a different /128 IPv6 address but rather an address on the
>      > same box. From your reply below it seems possible.
>      > b. No other IPV6 address on the node should be advertised.
> Do you want the RPL node to auto-configure an address from the PIO?
> At present this can't be turned off, but that certainly could be made an option.
>      > c. Should be able to control on which interfaces RPL is enabled (i.e, not all
>      > interface on the node is part of the DODAG).
> You should be able to do that now with multiple -i options.
>      > d. Requirement C is dynamic in nature - Should be able to add/remove the
>      > interface on a node to the DODAG. I think this will create different DODAG
>      > versions but this is something that is required.
> So, how would you want to enable/disable RPL on a particular interface?
> What kind of interface would you want?  I plan to integrate with
> quagga/zebrad at some point, but it's not a priority.
>      > e. Ofcourse all downward routes stored on a node should be propagated up
>      > towards the Root.
> That it already does.
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr at sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

More information about the Unstrung-hackers mailing list