-
Notifications
You must be signed in to change notification settings - Fork 232
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread Devices Become Unreachable from RPI Over Time Despite Connectivity via ot-ctl #2226
Comments
Some observations from the logs:
You seem to be running an older commit (from 2022). Suggest upgrading to new version. Some specific changes to support larger number of infra-if routers:
|
Thank you for your feedback. In our setup, we have one RCP based border router and 3 other OpenThread devices, which are configured to function as routers within the network. To manage and monitor the state of our OpenThread Border Router (OTBR), we've implemented a script that actively sends messages to these OpenThread devices via UDP. These devices are programmed to respond to these messages, allowing us to ensure continuous communication and validate network stability. The older commit version we're using might indeed be contributing to the issues. We plan to upgrade to a newer version, keeping in mind the enhancements mentioned, especially regarding netdata space savings and flexible data structures. Upgrading will take some time to observe if the issue reoccurs due to its intermittent nature. |
Describe the bug
In my setup, I have a Raspberry Pi (RPI) connected to an OpenThread Border Router (OTBR) via USB, along with a Thread device connected to the OpenThread network. After a period of time, the Thread devices become unreachable from the RPI when attempting to ping them or send/receive UDP packets from/to the thread devices, although they remain reachable from the
ot-ctl
interface via the border router. I suspect the cause for this is when the otbr-agent is not finding the preferred OMR prefix in Thread network.otbr-agent Logs
Ping Snapshots
Border router mIP is
fd2b:2ff3:86e4:8b0f:6172:566b:4bb0:1361
Thread device mIP is
fd2b:2ff3:86e4:8b0f:bf95:5aee:84de:45fc
Here are the ping that were performed from the RPI and
ot-ctl
to the Thread device:Ping to the border router works fine
Environment
The text was updated successfully, but these errors were encountered: