Upgrading from ESP-IDF 5.1 to 5.3; breaking changes? (TZ-1396) #112
Comments
github-actions
bot
changed the title
|
Hi @motters did you use the tag: v5.3.2 for your test or could you please share the commit hash you used? I try to reproduce the issue you encountered but failed. All features related NAT64 works well on my side. We found a problem on the tag v5.3.2 and we are investigating it these days.(There will be an error logs So could you please try the code base metioned in the docs: https://docs.espressif.com/projects/esp-thread-br/en/latest/dev-guide/build_and_run.html#set-up-the-repositories and see if NAT64 works? For the dns resolving command you metioned above: Did you execute the command on the BR device or on the node? |
|
HI @zwx1995esp thanks for the reply. We have tried both 5.3.1 & 5.3.2 releases. I will try the commit mentioned in the documentation this morning. All commands were executed from the BR, including Maybe one difference is we have https://github.com/espressif/arduino-esp32 package installed to speed up development. Could this be causing issues? |
|
Could you share the steps to reproduce the issue, including how you integrated Arduino-ESP32 into your application? In the meantime, could you try running the basic_thread_border_router example as-is and let us know if the issue also occurs? |
|
Hi @chshu, I've setup a new copy of
We're having the same issues with connection timeouts: 
Heres the (slightly tidied up) log from the above: As per our production firmware we integrated ESP-Ardunio using the manual method https://docs.espressif.com/projects/arduino-esp32/en/latest/esp-idf_component.html#manual-installation-of-arduino-framework . However since we're having the same issue with the |
|
Hi, @motters just a question, does this |
|
This DNS resolve command is used for the end node devices which attached in BR's thread network. So could you please also try if it works on the end node devices? |
|
@zwx1995esp i see, is there a command i can run on the BR to test the network? I'll test from a node and post the result. |
|
Good news the dns command does work from the node when using the BR is using the However it does not work from our modded / production version on the BR. I suppose next step is to exclude idf-ardunio causing the issue? |
|
I'm comparing the logs of We are also getting multiple of the following warnings: However the So i'm assuming the issues is todo with |
|
After more digging it seems the esp-arduino WebServer is the component causing the issues. Once we remove all the WebSever code OpenThread is now working correctly. |
|
@zwx1995esp @chshu I think this can be closed. It seems using any arduino-esp32 However, i think it's worth noting in the README that OpenThread BR features cannot be used in conjunction with |
Checklist
Issue or Suggestion Description
Hi,
Summary
Are there any API changes that could break routing data from the NAT to the backbone when migrating from IDF 5.1 to 5.3?
Details
We were having issues with the ESP BR crashing during high bursts of data, (https://github.com/orgs/openthread/discussions/11038). @chshu suggested we upgraded to IDF 5.3 which fixed a bug around this issue.
We have updated ESP-IDF to 5.3 and everything is working, except the BR is not passing requests from the NAT to the backbone.
For example, when a node tries to perform a DNS request using the BR's NAT, there is no reply. Below shows the BR log where
fd6e:266c:4da0:1:7d59:1874:de24:c55eis the node.The BR can contact the node:
The BR's NAT is active:
The BR has an internet connection as we are running other libraries that use the same network. However OT cannot ping any external ip addresses:
The BR's openthread stack can also not perform DNS requests
The nodes use OT SRP and these services are registered to the building's router through the BR successfully. Hence proving the backbone is registered correctly. See the below output from a computer on the same network.
Some BR logs that may help:
Do you have any suggestion?
Thanks!
The text was updated successfully, but these errors were encountered: