-
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
use CoAP for fetching diagnostic #2569
Comments
@wgtdkp Thanks for the quick answer, I was suspecting something similar. |
The BR knows if the packet is from the kernel: https://github.com/openthread/openthread/blob/005c5cefc22aaf0396e4327ee7f2e0ad32a7733b/src/posix/platform/netif.cpp#L1245 |
But..the CLI can send CoAP request over the network, right? How do those remote systems differentiate the CLI vs a generic CoAP client? |
OpenThread CLI leverages OpenThread's internal CoAP implementation. A generic CoAP client come through the host system's network stack. OpenThread treats those sources of packets differently. |
@jwhui gereat, that would explain my strange observations in wireshark. So, is there a way to use a generic coap client to access those internal endpoints? |
I am Interested in retrieving diagnostic data from devices via CoAP.
From my research, it seems that the TMF CoAP server is listening at port 61631.
I am now trying to use
coap-client
to fetch said diagnostics data via the commandThe issue now is that my
otbr-agent
instance logs outDropping TMF message from untrusted origin
and seems to return 4.04.Thus, here are my questions:
Thanks for your time!
The text was updated successfully, but these errors were encountered: