[riot-notifications] [RIOT-OS/RIOT] shell/ping6: Incorrect handling of unexpected pongs (#11519)

Martine Lenders notifications at github.com
Tue Jul 30 22:26:06 CEST 2019


> 2\. On A: ping6 node B and immediately afterwards ping6 some unreachable/unassigned IPv6 address

Ok, but then I don't understand what is happening. If I ping an unreachable address, there should be no reply. As we now with #11933 check the source of the packet against the pinged address the second case should also be fixed. Setting the ID to a more node-specific one is in my eyes only patch-work to fix a sympton, but not the underlying issue (if two nodes have the same ID by chance the problem would still exist)

-- 
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/issues/11519#issuecomment-516581994
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190730/6aaf6594/attachment.htm>


More information about the notifications mailing list