You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When it's implemented in the code a functionality with border_router_add_ipv6_node() and radio_init_setup() (setting ipv6 address) is throwing a conflict if both functions are used, the radio initialization it's broken and the others configurations parameters are not set. If you retry using first radio_init_setup() you could find that border_router_add_ipv6_node() doesn't change the ipv6 address. This issue also affects in rpl initialization, if radio_init_setup() is not executed the anothers functonalities are affected.
Also Rpl initilization to dodag or dag should be manage only in the rpl module, in border_router_add_ipv6_node() is initializing the node as dodag. This means that if want to create a dag node, couldn't work, because is initialized as dodag...
The text was updated successfully, but these errors were encountered:
When it's implemented in the code a functionality with border_router_add_ipv6_node() and radio_init_setup() (setting ipv6 address) is throwing a conflict if both functions are used, the radio initialization it's broken and the others configurations parameters are not set. If you retry using first radio_init_setup() you could find that border_router_add_ipv6_node() doesn't change the ipv6 address. This issue also affects in rpl initialization, if radio_init_setup() is not executed the anothers functonalities are affected.
Also Rpl initilization to dodag or dag should be manage only in the rpl module, in border_router_add_ipv6_node() is initializing the node as dodag. This means that if want to create a dag node, couldn't work, because is initialized as dodag...
The text was updated successfully, but these errors were encountered: