Replies: 3 comments 1 reply
-
This indicates the ethernet network interface's state of your Raspberry Pi has been continuously changing. You may use |
Beta Was this translation helpful? Give feedback.
-
On the other hand, have you let your otbr-agent join/create a Thread network? I don't see relevant logs. |
Beta Was this translation helpful? Give feedback.
-
ip monitor link command doesn't seem to show anything for what happened. The previous behavior happens if i didn't join/create thread network in a little time (less than 3 minutes) which is strange for me ! I wants to run test cases from thread harness tool under br1 and br2 roles so I needed to add thread border router and start running test case quickly before otbr-agent stop running. Although I have managed to start previous procedure quickly, I can see many test cases fails from test harness 1- Is the behavior of restarting otbr-agent normal in case of no activity done on the device ? 2- Are there any specific configurations that should be enabled in raspberry pi setup to run BR_1 and BR_2 roles for thread 1.2 test cases like DUA feature ( is it enough to use default build INFRA_IF_NAME=eth0 ./script/setup) ? |
Beta Was this translation helpful? Give feedback.
-
Hi,
I'm working on OTBR using raspberry pi (RCP design),
I have followed steps from : https://openthread.io/guides/border-router/build#install-otbr
raspberry pi and my pc are connected on locally ethernet switch( not connected to internet) , pc communicate with raspberry pi using ssh.
otbr-agent keep changing status continuously and when it's status not running, I can't communicate to raspberry pi.
The following logs shows the services status
can anyone help me with this ?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions