[riot-notifications] [RIOT-OS/RIOT] tests/gnrc_tcp_*: #2 not working on 6Lo-based boards (#10956)

Simon Brummer notifications at github.com
Wed Feb 6 14:30:40 CET 2019


> > Hm this is something I can't test at home :(.
> 
> But in the IoT-LAB ;-).

That might be true. Do you have any reference on how to use that?

I just want to collect what works and what not:
1) Currently native works without Packet flooding and with the Device ID 5.
2) Non-native works but has Packet flooding. And the Device ID 6 is required, because
there is the additional 6LoPan Layer native doesn't use. 

=> Hardcoding a device identifier is a bad idea. Maybe I could use a Unique local address (fc00/7)
for those tests. Then there is no need for a changing device identifier, that causes obviously problems between running the test on native and non-native. This might improve the situation.

I am not sure what causes the described Packet Flood, the last changes to gnrc_tcp itself were #9233 (there was the previously mentioned discussion). It is from last may but as far as I know it worked on the samr-xpro without any odd behavoir.


-- 
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/10956#issuecomment-461023346
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190206/27ac57ab/attachment-0001.html>


More information about the notifications mailing list