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

Vijay Anand R vjanandrgky at gmail.com
Wed Sep 23 01:40:07 EDT 2015

The following is what I am trying to explore if we can achieve.

a. Should be able to advertise a specific IPv6 address (/128) assigned 
to a loopback or dummy interface on a node.
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.
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).
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.
e. Ofcourse all downward routes stored on a node should be propagated up 
towards the Root.

On 9/23/2015 1:02 AM, Michael Richardson wrote:
> Vijay Anand R <vjanandrgky at gmail.com> wrote:
>      > curious about the command that you suggested: /sbin/sunshine.run
>      > --dagid ripple -i eth1 --rank 1 --prefix 2001:db8:0001::/48 --interval
>      > 30000 --verbose --timelog
>      > so the prefix here is what is used by the nodes to auto configure
>      > themselves and is propagated using the DIO messages from the root to
>      > the rest of the DAG.  But what if I want to advertise a particular IPV6
>      > address (/128) that is assigned by me ? How do I provide the address
>      > that has to be advertised in the DAO messages ?
> The --prefix is what the DODAG root will announce in the PIO option of the
> DIO message.
> Based upon that, other nodes that join that DODAG will autoconfigure (usually
> using SLAAC, but they could use stable private addresses, or some other way
> of getting a lower-64-bits) an address. The new address will be placed
> as an alias on lo, as a /128.
> The new /128 will be added the addresses reachable via this node and
> sent upwards in the next DAO.  That DAO will also have any other /128s
> reachable below the current node.
> It seems that you want to advertise a *different* /128, and that is
> conceptually possible, but there is no code to do that yet.
> What is the origin of this /128?  If it is an address that is a neighbour
> that does not run RPL, but might have heard a route advertisement via
> Efficient ND... then that's definitely something that should be done.
> How would you like to specify those other addresses?
> Would code that enumerated all the addresses on all the interfaces
> and then announce those that matched some netmask work? (You could, of
> course, specify ::/0 as the mask to get them all. We'd have to filter out
> ::/64, the loopback addresses, anyway).
> Hmm. maybe all addresses with a > scope would make sense, filter out
> scope = 1 and scope = 2 addresses, as that gets the link local and the
> loopback addressses automatically.
>      > Please note I am trying to configure all nodes in storing mode so I
>      > need to store routes and advertise DAO as well (unlike the glow
>      > program).
> "glow" isn't written yet, btw :-)
> --
> ]               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