[riot-notifications] [RIOT-OS/RIOT] gnrc_netif: centralize device-type-specific functions (#10524)

Gunar Schorcht notifications at github.com
Fri Jan 4 14:04:08 CET 2019


@miri64 Since I have not yet seen how the test should look like if it works correctly on a platform, here what I did, what I could observe, and some questions I have:

- I have two nodes and one border router.
- The first question came up when I had to compile the nodes as leaf nodes with `CFLAGS="-DGNRC_IPV6_NIB_CONF_6LN=1 - DGNRC_IPV6_NIB_CONF_6LR=0`. Otherwise, I get
   
   ```
    nib: multihop prefix and context dissemination on router activated,
         but no ABRO found. Discarding router advertisement silently
   ```
   on receiption of router advertisements and the global unicast address is not set.
   Is that correct?
- On the nodes, `ifconfig` shows that `RTR_ADV` option is set even though they are leaf nodes. Is that correct and do I have to execute `ifconfig 9 -rtr_adv`?
- In my network, the border router gets over its Ethernet interface the global routing prefix `2003:aaaa:bbbb:cccc::/64` from the LAN and the global unicast address `2003:aaaa:bbbb:cccc:32ae:a4ff:fe47:4ccd`.
- When I use `ifconfig 9 add unicast 2001:db8::1/64`, the leaf nodes get the global unicast addresses `2001:db8::32ae:a4ff:fe18:7a3d` and `2001:db8::32ae:a4ff:fe41:60f9`
- On router, `nib route` gives
   ```
   2003:aaaa:bbbb:cccc::/64 dev #6
   2001:db8::/64 dev #9
   default* via fe80::1 dev #6
   ```
- On the nodes, `nib route` gives
   ```
   default* via fe80::32ae:a4ff:fe47:4ccd dev #9
   ```
- Pinging from one node the other node with `ping6 2001:db8::32ae:a4ff:fe18:7a3d` doesnt work. The reason seems to be that the source node is using rather its link local address than its global unicast address. On the route, I can see the following message:

   ```
   ipv6: Received (src = fe80::32ae:a4ff:fe41:60f9, dst = 2001:db8::32ae:a4ff:fe18:7a3d, next header = 58, length = 12)
   ```
   So it is probably the a problem of `esp_now`.


-- 
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/10524#issuecomment-451438112
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190104/eb5836ec/attachment.html>


More information about the notifications mailing list