Comments (17)
I will do the two ESP tests later today tomorrow, namely:
from release-specs.
So, ESP task 12:
> 2024-02-07 11:14:35,665 # WiFi connected to ssid Loeffelnetz, channel 1
ping riot-os.org
2024-02-07 11:14:43,123 # ping riot-os.org
2024-02-07 11:14:43,424 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=0 ttl=57 time=45.077 ms
2024-02-07 11:14:44,422 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=1 ttl=57 time=43.803 ms
2024-02-07 11:14:45,437 # 12 bytes from 2a01:4f9:1a:9508::1: icmp_seq=2 ttl=57 time=43.548 ms
this works. I had to cheat a bit by adding UPLINK
wifi password and additional USEMODULE
to the Makefile
instead of via command line, as this wasn't passed to the docker image with BUILD_IN_DOCKER=1
. But I think this was broken before and is easy to work around, so let's not let this block the release.
from release-specs.
Task #06 - GNRC LoRaWAN (ABP) - PASSES*
I couldn't test downlink because Chirpstack is also replying with downlink frames in Port 0, which requests the node to change transmission settings and won't send additional data until it takes effect. So we cannot test this in ABP unless we implement the missing FOpts.
In any case, I wouldn't worry that much. The downlink feature is decoupled from the joining logic and it was already tested in the OTAA test.
|
-- | --
0 |
type | "up"
payload |
applicationID | "2"
applicationName | "ABP_dev"
deviceName | "abo"
devEUI | "b+vTS0jfJp4="
rxInfo |
0 |
gatewayID | "3KYy//4m/as="
time | "2024-02-07T10:49:55.760286Z"
timeSinceGPSEpoch | "1391338214.760s"
rssi | -41
loRaSNR | 8
channel | 2
rfChain | 1
board | 0
antenna | 0
location |
latitude | 53.55595
longitude | 10.02491
altitude | 2
source | "UNKNOWN"
accuracy | 0
fineTimestampType | "NONE"
context | "rh6nrA=="
uplinkID | "+i/278hORIKnVz/ue7HV2g=="
crcStatus | "CRC_OK"
txInfo |
frequency | 868500000
modulation | "LORA"
loRaModulationInfo |
bandwidth | 125
spreadingFactor | 12
codeRate | "4/5"
polarizationInversion | false
adr | false
dr | 0
fCnt | 3
fPort | 1
data | "aG9sYQ=="
objectJSON | ""
tags | {}
confirmedUplink | false
devAddr | "APOM8A=="
publishedAt | "2024-02-07T10:48:01.988712229Z"
1 |
type | "up"
payload |
applicationID | "2"
applicationName | "ABP_dev"
deviceName | "abo"
devEUI | "b+vTS0jfJp4="
rxInfo |
0 |
gatewayID | "3KYy//4m/as="
time | "2024-02-07T10:50:30.153534Z"
timeSinceGPSEpoch | "1391338249.153s"
rssi | -41
loRaSNR | 7.8
channel | 2
rfChain | 1
board | 0
antenna | 0
location |
latitude | 53.55595
longitude | 10.02491
altitude | 2
source | "UNKNOWN"
accuracy | 0
fineTimestampType | "NONE"
context | "rV5I9A=="
uplinkID | "62DrhsHaRraMeYo0tZqOwA=="
crcStatus | "CRC_OK"
txInfo |
frequency | 868500000
modulation | "LORA"
loRaModulationInfo |
bandwidth | 125
spreadingFactor | 12
codeRate | "4/5"
polarizationInversion | false
adr | false
dr | 0
fCnt | 2
fPort | 1
data | "aG9sYQ=="
objectJSON | ""
tags | {}
confirmedUplink | false
devAddr | "APOM8A=="
publishedAt | "2024-02-07T10:47:49.372349073Z"
2 |
type | "up"
payload |
applicationID | "2"
applicationName | "ABP_dev"
deviceName | "abo"
devEUI | "b+vTS0jfJp4="
rxInfo |
0 |
gatewayID | "3KYy//4m/as="
time | "2024-02-07T10:49:17.884510Z"
timeSinceGPSEpoch | "1391338176.884s"
rssi | -42
loRaSNR | 8.5
channel | 1
rfChain | 1
board | 0
antenna | 0
location |
latitude | 53.55595
longitude | 10.02491
altitude | 2
source | "UNKNOWN"
accuracy | 0
fineTimestampType | "NONE"
context | "qzTdFA=="
uplinkID | "WhT3HUNQRnWfkHwxk9NWgQ=="
crcStatus | "CRC_OK"
txInfo |
frequency | 868300000
modulation | "LORA"
loRaModulationInfo |
bandwidth | 125
spreadingFactor | 12
codeRate | "4/5"
polarizationInversion | false
adr | false
dr | 0
fCnt | 1
fPort | 1
data | "aG9sYQ=="
objectJSON | ""
tags | {}
confirmedUplink | false
devAddr | "APOM8A=="
publishedAt | "2024-02-07T10:47:13.110266810Z"
3 |
type | "up"
payload |
applicationID | "2"
applicationName | "ABP_dev"
deviceName | "abo"
devEUI | "b+vTS0jfJp4="
rxInfo |
0 |
gatewayID | "3KYy//4m/as="
time | "2024-02-07T10:49:19.583570Z"
timeSinceGPSEpoch | "1391338178.583s"
rssi | -44
loRaSNR | 9
channel | 0
rfChain | 1
board | 0
antenna | 0
location |
latitude | 53.55595
longitude | 10.02491
altitude | 2
source | "UNKNOWN"
accuracy | 0
fineTimestampType | "NONE"
context | "qXXBfA=="
uplinkID | "crJjdXDsTMqWEg0DKFJAHA=="
crcStatus | "CRC_OK"
txInfo |
frequency | 868100000
modulation | "LORA"
loRaModulationInfo |
bandwidth | 125
spreadingFactor | 12
codeRate | "4/5"
polarizationInversion | false
adr | false
dr | 0
fCnt | 0
fPort | 1
data | "aG9sYQ=="
objectJSON | ""
tags | {}
confirmedUplink | false
devAddr | "APOM8A=="
publishedAt | "2024-02-07T10:46:43.820248120Z"
from release-specs.
I opened an issue regarding the failing ESP test: RIOT-OS/RIOT#20349
I think that the test would have worked if I didn't had a chain of two routers. My current setup is that I use a cheap FritzBox with a VDSL2 modem but no WiFi capabilities (802.11g and 2.4 GHz only IMO "no WiFi capabilities) and an OpenWrt box with WiFi behind that (802.11 ax dual-band). As a result the OpenWrt only has a smaller prefix to delegate. My guess is that RIOT's DHCPv6 is asking for a prefix longer than what the OpenWrt can or is willing to offer.
So no regression, but an issue that always has been there. Should IMO not block the release and is documented via the issue.
from release-specs.
Perfect... I think we can release as is and just backport RIOT-OS/RIOT#20348 to the release branch and it will be included with any point releases in the future.
from release-specs.
Remaining tests for RC2:
Task #02 - ICMPv6 echo between iotlab-m3 and Linux with 6LowPAN
Task #04 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN
Task #05 - ICMPv6 echo between iotlab-m3 and Internet host through RIOT border router
Task #06 - UDP between iotlab-m3 and Internet host through RIOT border router
Task #07 - UDP between iotlab-m3 and Internet host through RIOT border router (200b payload)
Task #11 - UDP exchange between iotlab-m3 and Zephyr
Task #12 - ICMPv6 echo between Border Router with WiFi uplink to named Internet host
Task #13 - ICMPv6 echo between ESP and named Internet host through RIOT BR with 6LowPAN
Task #06 - GNRC LoRaWAN (ABP)
from release-specs.
Test Report
from release-specs.
Test
Task #02 - ICMPv6 echo between iotlab-m3 and Linux with 6LowPAN: PASS
2024-02-06 12:00:36,584 # --- 2001:db8:1:0:204:2519:1801:bddb PING statistics ---
2024-02-06 12:00:36,589 # 3 packets transmitted, 3 packets received, 0% packet loss
2024-02-06 12:00:36,594 # round-trip min/avg/max = 22.674/23.830/25.167 ms
from release-specs.
Task #04 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN PASS
2024-02-06 12:05:09,602 # 12 bytes from 2001:db8:1:0:204:2519:1801:bddb: icmp_seq=75 ttl=63 rssi=-50 dBm time=21.955 ms
2024-02-06 12:05:10,604 # 12 bytes from 2001:db8:1:0:204:2519:1801:bddb: icmp_seq=76 ttl=63 rssi=-51 dBm time=22.703 ms
2024-02-06 12:05:11,608 # 12 bytes from 2001:db8:1:0:204:2519:1801:bddb: icmp_seq=77 ttl=63 rssi=-50 dBm time=24.617 ms
1 0.000000000 2001:db8::204:2519:1801:8930 2001:db8:1:0:204:2519:1801:bddb ICMPv6 66 Echo (ping) request id=0xfd83, seq=15, hop limit=63 (reply in 2)
2 0.000046490 2001:db8:1:0:204:2519:1801:bddb 2001:db8::204:2519:1801:8930 ICMPv6 66 Echo (ping) reply id=0xfd83, seq=15, hop limit=64 (request in 1)
from release-specs.
Test Report
Task | Outcome | |
---|---|---|
✔ | 01. Task 02 - Unittests on native | PASSED |
✖ | 08. Task 11 - UDP exchange between iotlab-m3 and Zephyr | FAILED |
from release-specs.
Task #06 - UDP between iotlab-m3 and Internet host through RIOT border router PASS
Task #07 - UDP between iotlab-m3 and Internet host through RIOT border router (200b payload) PASS
~/ sudo socat UDP6-LISTEN:80,fork,su=nobody - | xxd
00000000: 1e1e 1e1e 1e1e 1e1e 1e1e 1f1f 1f1f 1f1f ................
00000010: 1f1f 1f1f 2020 2020 2020 2020 2020 2121 .... !!
00000020: 2121 2121 2121 2121 2222 2222 2222 2222 !!!!!!!!""""""""
00000030: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
00000040: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
00000050: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
00000060: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
00000070: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
00000080: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
00000090: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
000000a0: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
000000b0: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
000000c0: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
000000d0: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
000000e0: 2222 2222 2222 2222 2222 2222 2222 2222 """"""""""""""""
udp send 2001:db8:1:0:204:2519:1801:bddb 80 10
> 2024-02-06 13:24:17,745 # udp send 2001:db8:1:0:204:2519:1801:bddb 80 10
2024-02-06 13:24:17,753 # Success: send 10 byte to [2001:db8:1:0:204:2519:1801:bddb]:80
> udp send 2001:db8:1:0:204:2519:1801:bddb 80 210
2024-02-06 13:24:24,150 # udp send 2001:db8:1:0:204:2519:1801:bddb 80 210
2024-02-06 13:24:24,170 # Success: send 210 byte to [2001:db8:1:0:204:2519:1801:bddb]:80
from release-specs.
Task #11 - UDP exchange between iotlab-m3 and Zephyr
iotlab-m3
ifconfig
2024-02-06 13:51:26,383 # ifconfig
2024-02-06 13:51:26,387 # Iface 5 HWaddr: 0D:74 Channel: 26 NID: 0x23 PHY: O-QPSK
2024-02-06 13:51:26,388 #
2024-02-06 13:51:26,390 # Long HWaddr: A6:67:AF:41:D9:E4:8D:74
2024-02-06 13:51:26,393 # TX-Power: 0dBm State: IDLE max. Retrans.: 3 CSMA Retries: 4
2024-02-06 13:51:26,395 # AUTOACK ACK_REQ CSMA L2-PDU:102 MTU:1280 HL:255 RTR
2024-02-06 13:51:26,396 # RTR_ADV 6LO IPHC
2024-02-06 13:51:26,396 # Source address length: 8
2024-02-06 13:51:26,396 # Link type: wireless
2024-02-06 13:51:26,397 # inet6 addr: fe80::a467:af41:d9e4:8d74 scope: link VAL
2024-02-06 13:51:26,398 # inet6 addr: 2001:67c:254:b0c1:a467:af41:d9e4:8d74 scope: global TNT[3]
2024-02-06 13:51:26,399 # inet6 group: ff02::2
2024-02-06 13:51:26,399 # inet6 group: ff02::1
2024-02-06 13:51:26,400 # inet6 group: ff02::1:ffe4:8d74
2024-02-06 13:51:26,400 # inet6 group: ff02::1a
2024-02-06 13:51:26,400 #
2024-02-06 13:51:26,401 # Statistics for Layer 2
2024-02-06 13:51:26,401 # RX packets 4 bytes 307
2024-02-06 13:51:26,402 # TX packets 5 (Multicast: 2) bytes 360
2024-02-06 13:51:26,402 # TX succeeded 5 errors 0
2024-02-06 13:51:26,409 # Statistics for IPv6
2024-02-06 13:51:26,410 # RX packets 4 bytes 320
2024-02-06 13:51:26,410 # TX packets 5 (Multicast: 2) bytes 402
2024-02-06 13:51:26,411 # TX succeeded 5 errors 0
2024-02-06 13:51:26,411 #
> ifconfig 5 set chan 26
2024-02-06 13:51:31,274 # ifconfig 5 set chan 26
2024-02-06 13:51:31,276 # success: set channel on interface 5 to 26
> ifconfig 5 set pan_id 0xabcd
2024-02-06 13:51:39,146 # ifconfig 5 set pan_id 0xabcd
2024-02-06 13:51:39,150 # success: set network identifier on interface 5 to 0xabcd
> udp server start 4242
2024-02-06 13:51:48,137 # udp server start 4242
2024-02-06 13:51:48,139 # Success: started UDP server on port 4242
> udp send fe80::d870:14a4:758a:a654 4242 "RIOT Testing!"
2024-02-06 13:52:59,620 # udp send fe80::d870:14a4:758a:a654 4242 "RIOT Testing!"
2024-02-06 13:52:59,621 # Error: unable to parse data_len
> udp send fe80::d870:14a4:758a:a654 4242 12
2024-02-06 13:53:14,723 # udp send fe80::d870:14a4:758a:a654 4242 12
2024-02-06 13:53:14,726 # Success: send 12 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:14,737 # Packets received: 1
> udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:24,770 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:24,786 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:24,787 # Packets received: 2
> udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:28,290 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:28,305 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:28,306 # Packets received: 3
udp send fe80::d870:14a4:758a:a654 4242 85
> 2024-02-06 13:53:29,298 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:29,301 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:29,312 # Packets received: 4
udp send fe80::d870:14a4:758a:a654 4242 85
> 2024-02-06 13:53:30,306 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:30,308 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:30,320 # Packets received: 5
udp send fe80::d870:14a4:758a:a654 4242 85
> 2024-02-06 13:53:31,313 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:31,316 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:31,316 # Packets received: 6
udp send fe80::d870:14a4:758a:a654 4242 85
> 2024-02-06 13:53:32,305 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:32,308 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:32,320 # Packets received: 7
udp send fe80::d870:14a4:758a:a654 4242 85
> 2024-02-06 13:53:33,314 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:33,317 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:33,328 # Packets received: 8
udp send fe80::d870:14a4:758a:a654 4242 85
> 2024-02-06 13:53:34,321 # udp send fe80::d870:14a4:758a:a654 4242 85
2024-02-06 13:53:34,324 # Success: send 85 byte to [fe80::d870:14a4:758a:a654]:4242
2024-02-06 13:53:34,336 # Packets received: 9
samr21-xpro
uart:~$ D: (udp6): UDP (IPv6): Received and replied with 12 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
D: (udp6): UDP (IPv6): Received and replied with 85 bytes
I: IPv6 UDP: Received 11 B/sec
from release-specs.
I will do the two ESP tests
If nothing else goes wrong then only:
Task #04 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN
and
are left and we can release!
from release-specs.
I will do the two ESP tests
If nothing else goes wrong then only:
[Task #4 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN]> > (https://github.com/RIOT-OS/Release-Specs/blob/0c23dbb567f79d415be96ec52c4ead4d4df48754/08-interop/README.md#task-04---icmpv6-echo-between-iotlab-m3-and-internet-host-through-linux-with-6lowpan)
and
are left and we can release!
I'm on it!
from release-specs.
Wait, the second interface doesn't get a global IP. I think my home network does do prefix delegation, at least my OpenWRT does claim to do that.
from release-specs.
Task #04 - ICMPv6 echo between iotlab-m3 and Internet host through Linux with 6LowPAN PASSES
2024-02-07 12:03:58,485 # ping 2002:67c:254:b0c2::1
2024-02-07 12:03:58,505 # 12 bytes from 2002:67c:254:b0c2::1: icmp_seq=0 ttl=64 rssi=-70 dBm time=11.406 ms
2024-02-07 12:03:59,508 # 12 bytes from 2002:67c:254:b0c2::1: icmp_seq=1 ttl=64 rssi=-70 dBm time=10.237 ms
2024-02-07 12:04:00,515 # 12 bytes from 2002:67c:254:b0c2::1: icmp_seq=2 ttl=64 rssi=-70 dBm time=11.433 ms
from release-specs.
Release is complete!
from release-specs.
Related Issues (20)
- Release 2022.10 - RC1 HOT 7
- Release 2022.10 - RC2 HOT 9
- 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.04 - RC1 HOT 12
- Release 2024.04 - RC2 HOT 4
- Release 2024.07 - RC1 HOT 12
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.