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

Martine Lenders notifications at github.com
Tue Jan 8 09:09:11 CET 2019

miri64 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:

> 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.;

Yupp, neither RSSI nor LQI are of interest for neighbor discovery, just for routing protocols (but AFAIK we don't use it as a metric for RPL at the moment).

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190108/501b7fe6/attachment.html>

More information about the notifications mailing list