Comments (9)
Task 03 - UDP exchange between iotlab-m3 and Contiki
udp server start 3000
2022-11-03 14:27:38,053 # udp server start 3000
2022-11-03 14:27:38,055 # Success: started UDP server on port 3000
> udp nd fe80::0212:4b00:0422:9db8 3000 1
2022-11-03 14:27:41,078 # udp send fe80::0212:4b00:0422:9db8 3000 1
2022-11-03 14:27:41,081 # Success: send 1 byte to [fe80::0212:4b00:0422:9db8]:3000
2022-11-03 14:27:41,093 # Packets received: 1
udp send fe80::0212:4b00:0422:9db8 3000 1>
2022-11-03 14:27:42,183 # udp send fe80::0212:4b00:0422:9db8 3000 1
2022-11-03 14:27:42,185 # Success: send 1 byte to [fe80::0212:4b00:0422:9db8]:3000
2022-11-03 14:27:42,197 # Packets received: 2
udp send fe80::0212:4b00:0422:9db8 3000 64
2022-11-03 14:27:50,822 # udp send fe80::0212:4b00:0422:9db8 3000 64
2022-11-03 14:27:50,826 # Success: send 64 byte to [fe80::0212:4b00:0422:9db8]:3000
2022-11-03 14:27:50,836 # Packets received: 3
from release-specs.
After re-triggering some of the tests it looks like the automated tasks are passing. m3-11.saclay.iot-lab.info node seems to be failing, which caused some tests to fail.
from release-specs.
I'm currently collecting output for compile_and_test_for_board.py
here: https://github.com/maribu/riot-test-results/tree/main/2022.10-branch-bf7e4f6ca8096de94c7f2274d4406de7263e9493
There are a few failures, mostly compilation errors presumably due to better diagnostics of my more recent toolchains (e.g. use after free bugs in ccn-lite etc.). I intend to address them and backport them tomorrow.
The test failures are mostly due to missing miniterm.py
or riotctrl
. I will try to obtain them and re-run the tests.
from release-specs.
From a quick skim over the results, you probably also will need scapy ;-).
from release-specs.
Test Report
from release-specs.
✖️ 01. Task 04 - Unittests on iotlab-m3 FAILED
[…]
✖️ 04. Task 04 - ICMPv6 echo with iotlab-m3/samr21-xpro 15 minutes FAILED
There seems to be an erroring M3 node be used in the experiments: https://gist.github.com/riot-ci/3ca2aa5f766aac7810904dbc29d1319a/e0e2a185ec293dbf731329ade3358c4ac08d45e8.
from release-specs.
OK, miniterm.py
is actually provided by py3-pyserial
, but the package didn't expose it in a way it was added to $PATH
. That was easy to fix, though. I will also package riotctrl
now. I bet the results will look much better then already :)
from release-specs.
08-interop - Task #11 - UDP exchange between iotlab-m3 and Zephyr: PASSED
Tested against Zephyr v3.2.0
RIOT node
> ifconfig 6 set pan_id 0xabcd
ifconfig 6 set pan_id 0xabcd
success: set network identifier on interface 6 to 0xabcd
> ifconfig 6 set chan 26
ifconfig 6 set chan 26
success: set channel on interface 6 to 26
> ping fe80::9ccf:400:2e9a:9f3b
ping fe80::9ccf:400:2e9a:9f3b
12 bytes from fe80::9ccf:400:2e9a:9f3b%6: icmp_seq=0 ttl=64 rssi=-66 dBm time=16.642 ms
12 bytes from fe80::9ccf:400:2e9a:9f3b%6: icmp_seq=1 ttl=64 rssi=-66 dBm time=6.236 ms
12 bytes from fe80::9ccf:400:2e9a:9f3b%6: icmp_seq=2 ttl=64 rssi=-66 dBm time=8.469 ms
--- fe80::9ccf:400:2e9a:9f3b PING statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 6.236/10.449/16.642 ms
> udp server start 4242
udp server start 4242
Success: started UDP server on port 4242
> udp send fe80::9ccf:400:2e9a:9f3b 4242 "riot"
udp send fe80::9ccf:400:2e9a:9f3b 4242 "riot"
Success: sent 4 byte(s) to [fe80::9ccf:400:2e9a:9f3b]:4242
> PKTDUMP: data received:
~~ SNIP 0 - size: 4 byte, type: NETTYPE_UNDEF (0)
00000000 72 69 6F 74
~~ SNIP 1 - size: 8 byte, type: NETTYPE_UDP (4)
src-port: 4242 dst-port: 4242
length: 12 cksum: 0x0549
~~ SNIP 2 - size: 40 byte, type: NETTYPE_IPV6 (2)
traffic class: 0x00 (ECN: 0x0, DSCP: 0x00)
flow label: 0x00000
length: 12 next header: 17 hop limit: 64
source address: fe80::9ccf:400:2e9a:9f3b
destination address: fe80::7894:5ff:258d:e7c3
~~ SNIP 3 - size: 24 byte, type: NETTYPE_NETIF (-1)
if_pid: 6 rssi: -65 lqi: 255
flags: 0x0
src_l2addr: 9E:CF:04:00:2E:9A:9F:3B
dst_l2addr: 7A:94:05:FF:25:8D:E7:C3
~~ PKT - 4 snips, total size: 76 byte
> udp send fe80::9ccf:400:2e9a:9f3b 4242 "riot2022.10"
udp send fe80::9ccf:400:2e9a:9f3b 4242 "riot2022.10"
Success: sent 11 byte(s) to [fe80::9ccf:400:2e9a:9f3b]:4242
> PKTDUMP: data received:
~~ SNIP 0 - size: 11 byte, type: NETTYPE_UNDEF (0)
00000000 72 69 6F 74 32 30 32 32 2E 31 30
~~ SNIP 1 - size: 8 byte, type: NETTYPE_UDP (4)
src-port: 4242 dst-port: 4242
length: 19 cksum: 0x42a7
~~ SNIP 2 - size: 40 byte, type: NETTYPE_IPV6 (2)
traffic class: 0x00 (ECN: 0x0, DSCP: 0x00)
flow label: 0x00000
length: 19 next header: 17 hop limit: 64
source address: fe80::9ccf:400:2e9a:9f3b
destination address: fe80::7894:5ff:258d:e7c3
~~ SNIP 3 - size: 24 byte, type: NETTYPE_NETIF (-1)
if_pid: 6 rssi: -66 lqi: 255
flags: 0x0
src_l2addr: 9E:CF:04:00:2E:9A:9F:3B
dst_l2addr: 7A:94:05:FF:25:8D:E7:C3
~~ PKT - 4 snips, total size: 83 byte
Zephyr node
uart:~$ net ipv6
net ipv6
IPv6 support : enabled
IPv6 fragmentation support : disabled
Multicast Listener Discovery support : enabled
Neighbor cache support : enabled
Neighbor discovery support : enabled
Duplicate address detection (DAD) support : enabled
Router advertisement RDNSS option support : enabled
6lo header compression support : enabled
Max number of IPv6 network interfaces in the system : 1
Max number of unicast IPv6 addresses per network interface : 3
Max number of multicast IPv6 addresses per network interface : 4
Max number of IPv6 prefixes per network interface : 2
IPv6 addresses for interface 1 (0x20001c7c) (IEEE 802.15.4)
=========================================================
Type State Lifetime (sec) Address
autoconf preferred infinite fe80::9ccf:400:2e9a:9f3b/128
manual preferred infinite 2001:db8::1/128
uart:~$ D: (udp6): UDP (IPv6): Received and replied with 4 bytes
D: (udp6): UDP (IPv6): Received and replied with 11 bytes
I: IPv6 UDP: Received 0 B/sec
from release-specs.
Closing in favor of #266
from release-specs.
Related Issues (20)
- Release 2022.07 - RC2 HOT 4
- Release 2022.07 - RC3 HOT 7
- Release 2022.07 - RC4 HOT 25
- Release 2022.10 - RC1 HOT 7
- Release 2022.10 - RC3 HOT 18
- Release 2023.01 - RC1 HOT 3
- Release 2023.01 - RC2 HOT 2
- Release 2023.01 - RC3 HOT 14
- 08 - Task 11: Building zephyr on atsamr21_xpro not possible HOT 4
- Release 2023.04 - RC1 HOT 12
- [RFC] Restructure/update Release Specs HOT 2
- Release 2023.04 - RC2 HOT 5
- Release 2023.04 - RC3 HOT 3
- Release 2023.07 - RC5 HOT 15
- Release 2023.10 - RC1 HOT 11
- Release 2023.10 - RC2 HOT 5
- Release 2023.10 - RC3 HOT 4
- Release 2024.01 - RC1 HOT 4
- Release 2024.01 - RC2 HOT 17
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from release-specs.