Replies: 3 comments 1 reply
-
@jukkar, as I have seen that you've worked on this, can you please let me know what do you think about this? Thanks! |
Beta Was this translation helpful? Give feedback.
-
Maybe we could have an optional packet callback pointer stored in |
Beta Was this translation helpful? Give feedback.
-
Or another option to have a packet callback registered per |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I am currently implementing OpenThread Border Router support in Zephyr and in my current usecase, a DNS upstream resolver functionality is required. An OpenThread node can initiate a DNS query which will arrive on the Border Router. Now, in theory, the Border Router should start querying on the backbone interface for that particular transaction initiated by the Thread node and provide an answer if available.
Looking over what is currently implemented, this platform code that would reside on the Border Router side will duplicate what is currently existing in the
dns_resolve.h
/resolve.c
files from Zephyr. What is making this implementation not 100% percent usable in this case is the fact that the answer will be stored indns_addrinfo
data structure fromdns_resolve_cb_t
, while the OpenThread node that initiatied that query expects a DNS packet as a response.Would it be possible to add some new API that will return a DNS packet instead of that data structure? I am thinking to implement something new in order not to break compatibility with previous version. If this is to be agreed, I am willing to start working on this specific feature. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions