OpenThread
Replies: 3 comments 5 replies
-
|
@adamhoof I hope this explanation helps: https://github.com/orgs/openthread/discussions/9688#discussioncomment-7771734 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your quick reply, I now get why does the pinging from OTBR not work, but that still does not explain, or I didn't get it, why in all of the examples, executing ping 8.8.8.8 from the CLI works? Also pinging the devices on wifi side worked? And it does not have to be border router, it is ok if only the ot_cli will be able to do that. |
Beta Was this translation helpful? Give feedback.
-
|
On a Thread device (not a border router), all messages are sent and received over the Thread stack. The Thread stack handles the message if the destination is the Thread interface itself (source code), so it works. However, on a border router (BR) device, the ping message is initiated from the OT CLI but is actually sent and received over the Wi-Fi stack. The ping reply reaches LwIP and is not forwarded to the Thread stack, so you cannot see the reply from the OT CLI.
It works well if you use the LwIP Socket APIs. The OT CLI ping command is just a special case, it works if you use the LwIP ICMP API to do the ping test. |
Beta Was this translation helpful? Give feedback.
-
|
But for me, pinging 8.8.8.8 or some local IPv4 address like 192.168.1.15 does not, that is my question really, why does it not work in my case, even though I have seen examples where it did? Also, I would be ok if this did not work but standard tcp using code or cli (tcpsockclient) worked, idc really about the ping, that is just for testing purposes... so do you suggest just try to connect to mqtt broker from the device on Thread network, using the standard ESP-MQTT, since it uses the lwip under the hood? Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Ok so I managed to make it to work on the LAN (still unable to ping 8.8.8.8), however, I do not really know how to be honest, I did not do anything new. Look for the row that contains n at the end, so there is sn in this example. So the ping command will look like this now: MAKE SURE to not include extra (displayed) ":" in the prefix, it would not work -> fd97:fbac:e740:2:0:0: >>>> : <<<</96 sn low 7800 Here it is WITH the extra ":" Some tips that might make it work:After reboot, wait until both the border router and the cli device display data when you type netdata show |
Beta Was this translation helpful? Give feedback.
-
|
@adamhoof It should work to ping IPv4 address from a Thread device (not a BR), the output looks like this: Also, the There should not be these two limitations, could you please double check? |
Beta Was this translation helpful? Give feedback.
-
@chshu This is my output for ping 8.8.8.8: Currently ping to 192.168.1.17 (but it worked for me like an hour ago and I literary did not do anything): And this is from approx an hour ago:
Indeed those are rather observed limitations and the one with border router being a leader is probably a not valid, thus the ? there, but the second one is more tied to I believe the border router starting up |
Beta Was this translation helpful? Give feedback.
-
|
@chshu And here we go again, after literary just TURNING ON AND OF the devices, the ping to 192.168.1.17 works again: But the ping to 8.8.8.8 does not work still |
Beta Was this translation helpful? Give feedback.
-
Hi there, i have been struggling with this one nut that has been holding me back for a couple of day now and i am out of ideas what to try.
I have scouted the ESP32 and this forum for answers but haven't really found any solution.
TLDR
Pinging and in general communication within Thread network works, but once i try to ping outside IPv4 address of my PC for example, it does not work, neither does pinging 8.8.8.8 work.
I am sorry to be asking here, but i am pretty unsure what to do now, i have tried a lots of things but they do not work, so any help will be really appreciated.
Hardware
ESP Thread Border Router from Espressif: https://www.aliexpress.com/item/1005005688193617.html
ESP32-H2-DevKitM-1-N4: https://www.aliexpress.com/item/1005005252175587.html
How to reproduce
I have followed the official docs for setting up border router here: https://docs.espressif.com/projects/esp ... d_run.html
That means i have successfully:
Menuconfig for ot_cli
Menuconfig for basic_thread_border_router
Commands I ran on the ot_cli
Commands I ran on the basic_thread_border_router
NOTE that there is not a Translator: Active displayed when inputting nat64 state, which I have seen with the RPI based border routers for example, could this be an issue and perhaps some unsupported feature from the Espressif side?
Thread network MLEID addresses:
ot_cli
basic_thread_border_router
Pinging within Thread network
ot_cli --->>> basic_thread_border_router
basic_thread_border_router --->>> ot_cli
Pinging IPv4 address from Thread network
Super nice, but pinging the IPv4 device on my home WLAN just does not work :/ I suppose there might also be something wrong with prefixes?
basic_thread_border_router/ot_cli --->>> device IPv4 on WiFi network
Pinging GLOBAL IPv6 address from Thread network
basic_thread_border_router --->>> device IPv6 on WiFi network - WHY DOES THIS ALSO NOT WORK?
ot_cli --->>> device IPv6 on WiFi network - WORKS
I went through the codelabs etc, but they are typically oriented towards RPI OTBR, so the settings are irrelevant, official ESP docs and it just seems to be working outa the box there, I must have missed something that I just can't see. I am also pretty new to IPv6 world, so I might not understand something fundamentally. Any help is greatly appreciated!
Beta Was this translation helpful? Give feedback.
All reactions