-
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 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.
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.
Maybe we could have an optional packet callback pointer stored in
struct dns_resolve_context
, registered with a separate API? All responses could then be passed "raw" to the registered callback w/o affecting existing functionalities.