-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Release 2022.10 - RC3 #266
Comments
IMO #264 (comment) is still valid, as the changes since RC2 have a close to zero chance to break things. I ticked task 8.11 therefore. |
Regarding the remaining Linux interop tests, I think @jia200x was going to give them a try |
|
these two are build environment errors - which system was this built on? |
I manually launched |
08-InteropTask 12
==> SUCCESS Task 13
==> FAILED (no public IPv6 address obtained) |
@benpicco, @gschorcht: Any idea why 8.13 failed? Is the issue that my WiFi is using channel 11 and the test only succeeds when channel 6 is used? |
@maribu Unfortunatly, I can't test it because my shitty Telekom Speedport Pro Plus Router doesn't support prefix delegation 😟 What I can say is that if your WiFi is using channel 11, you have to configure the same channel for the ESP-NOW interface by For the background, ESP-NOW and ESP-WiFi are using the single WiFi interface in Station and Soft-AP mode at the same time so that the channel for the Soft-AP mode used by ESP-NOW has to be the same as for the Station mode used by ESP-WiFi and ESP-NOW. |
I was told that @MrKevinWeiss ran the Contiki interop test and marked it as passed. Please holler if this is incorrect. |
I added the reference to the comment #264 (comment) |
For the following tests I could not manage to reach addresses past the iotlab A8 node. There may be a missconfiguration. The RIOT node reaches the Linux host running on the A8 via the BR (running on the m3 node of the A8 board). We discussed this offline with @maribu, for now we will consider these passes, but he may re-run them on a different hardware later. 08. Interop - Task 05 [PASSED]
08. Interop - Task 06 [PASSED]
08. Interop - Task 07 [PASSED]
|
|
I finally got the ESP border router working |
Was it the ESP-NOW channel or something else? |
Both. I have two routers (one that I chose with OpenWrt, one that I didn't chose with a proprietary firmware that I need to connect to the ISP). I was struggling hard to get prefix delegation working from the first router to the second to the boarder router. I still ended up with the boarder router choosing the ULA over the public prefix and assumed it to be an issue with my router setup, but it is rather a bug in RIOT. Disabling ULA in the OpenWRT box workes around the issue. If the second ESP switched the channel at runtime to the one ESP border router chose (it picked the acccess point with the best signal and used the same channel for ESP NOW), I had no connectivity between the two ESPs. I think it did work once to switch the channel at run time. But I am not sure anymore. |
It could compile those two on 2022.10-branch both on current arch and with |
I will run the missing interop tests during the day |
This issue lists the status of all tests for the Release Candidate 3 of the 2022.10 release.
Specs tested:
The text was updated successfully, but these errors were encountered: