[riot-notifications] [RIOT-OS/RIOT] gnrc_tcp-change and verfy addrs in use (#10963)

Simon Brummer notifications at github.com
Thu Feb 7 09:26:20 CET 2019


brummer-simon commented on this pull request.



> @@ -54,6 +76,25 @@ int main(void)
     return 0;
 }
 
+bool verify_ip_addr(gnrc_netif_t *netif)
+{
+    ipv6_addr_t must_match;
+
+    if (!ipv6_addr_from_str(&must_match, LOCAL_ADDR)) {
+        return false;
+    }
+
+    for (int i = 0; i < GNRC_NETIF_IPV6_ADDRS_NUMOF; ++i) {
+        bool ip_match = ipv6_addr_equal(&must_match, &(netif->ipv6.addrs[i]));

> Please don't forget to adapt the README files.
> 
> Other than that I can confirm it fixes the issue with native. Running on boards I get this failed assertion on the client which is triggered in the NIB: [`sys/net/gnrc/network_layer/ipv6/nib/_nib-internal.c:317 => 0xbb5`](https://github.com/RIOT-OS/RIOT/blob/master/sys/net/gnrc/network_layer/ipv6/nib/_nib-internal.c#L317)

Martine mentioned something that I might have to add routing information due to the different IP-Address class. 

-- 
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/10963#discussion_r254582391
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190207/80625480/attachment.html>


More information about the notifications mailing list