[riot-notifications] [RIOT-OS/RIOT] gnrc_netif: introduce distinction if an interface supports 6Lo or if it performs ND according to RFC 6775 (#10499)

Gunar Schorcht notifications at github.com
Mon Jan 7 15:33:39 CET 2019


@miri64 I changed it locally and have already tested it. Address assignment with global routing prefix from RAs works now, at least for nodes that are able to receive the RAs from the border router. Following remarks:

- On the border router as well as the router nodes the multihop prefix had to be disabled explicitly due to the `assert` as discussed in #10524.
-  Furthermore, the SLAAC had to be enabled explicitly on all nodes due to https://github.com/RIOT-OS/RIOT/blob/2d1edfc7693786002c8e706fad5639dcd7398418/sys/net/gnrc/netif/gnrc_netif.c#L630
-  Non-6Lo-ND compiled as routers are not sending RAs anymore https://github.com/RIOT-OS/RIOT/blob/2d1edfc7693786002c8e706fad5639dcd7398418/sys/net/gnrc/network_layer/ipv6/nib/nib.c#L748-L750
Shouldn't they send RAs to distribute the prefix over the whole mesh, or is 6Lo-ND and multihop prefix capability a must for it?

Maybe it would be possible to define a pseudomodule for multihop prefix or 6Lo-ND  and to tune the dependencies a bit that the following setting are done automatically if the nodes are non 6Lo-ND nodes.

```
 CFLAGS="-DGNRC_IPV6_NIB_CONF_MULTIHOP_P6C=0 -DGNRC_IPV6_NIB_CONF_SLAAC=1" make ...
```


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/10499#issuecomment-451953543
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190107/8b423885/attachment.html>


More information about the notifications mailing list