[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 17:44:32 CET 2019


gschorcht commented on this pull request.



> -        netif->ops->set(netif, &opt);
+    switch (netif->device_type) {
+        case NETDEV_TYPE_IEEE802154: {
+            /* see https://tools.ietf.org/html/rfc6775#section-5.2 */
+            uint16_t src_len = IEEE802154_LONG_ADDRESS_LEN;
+            gnrc_netapi_opt_t opt = { .opt = NETOPT_SRC_LEN,
+                                      .data = &src_len,
+                                      .data_len = sizeof(src_len) };
+
+            /* XXX we are supposed to be in interface context here, so use driver
+             * directly everything else would deadlock anyway */
+            netif->ops->set(netif, &opt);
+            /* intentionally falls through */
+        }
+        case NETDEV_TYPE_BLE:
+        case NETDEV_TYPE_NRFMIN:

Ok for the moment. Once #10723 is solved, there should be be no reason why ESP-NOW nodes shouldn't talk 6Lo-ND. It worked in the tests with the workaround as expected.

There might be another reason why ESP-NOW nodes are different, the RSSI. It is not possible to extract the RSSI for a single message. RSSI is only measured during the scan-for-peers phase every 10 s. On the other hand, I did not find any place in the source code, where RSSI  or LQI are used for routing or something like that.;

-- 
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#discussion_r245720310
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190107/215ae11f/attachment.html>


More information about the notifications mailing list