You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should incorporate all 802.15.4 radios in our release tests.
We should add interoperability tests between different radios.
Especially when it comes to 6LoWPAN fragmentation where multiple frames are sent subsequently, I expect many issues. Just as an example, in #9864 I found out that ping6 with fragmented ICMPv6 packets results in 100% loss between cc2538 and mrf24j40 radios.
The text was updated successfully, but these errors were encountered:
Basic interoperability tests are included in the release phase but only between iotlab-m3, samr21-xpro, arduino-zero/XBee and remote-reva/b. Except for the remote, all these tests can be run on IoT-LAB, and more precisely on the Saclay site: a dozen iotlab-m3, 15 samr21-xpro and 3 arduino-zero are there in the same room and can communicate between each other.
And in a close future (expect 2 to 4 weeks), there will be frdm-kw41z and nrf52840dk (and I'm thinking about adding samr30-xpro as well. All in the same room and easily reachable from the RIOT build system thanks to the awesome IOTLAB_NODE variable !
Especially when it comes to 6LoWPAN fragmentation where multiple frames are sent subsequently, I expect many issues. Just as an example, in #9864 I found out that
ping6
with fragmented ICMPv6 packets results in 100% loss between cc2538 and mrf24j40 radios.The text was updated successfully, but these errors were encountered: