Sorry, you are right. It is possible for NAT64 to receive packets if it has the state from a recent transfer, or it is using static routing.
Have you tried removing the first backslash from the URI path? As you can see from the proceeding resource definitions, the leading backslash is not used in the path, this is added automatically by the CoAP libraries:
.mUriPath = "$sys/CxD2hb4NHT/tttt/thing/property/set",
I've tried it, but it still doesn't work.
Do you have any log outputs from your application?
Are you receiving any events in coap_default_handler() (or some other CoAP handler) when the message is received?
coap_default_handler() or other coap handle have no received any events when the message is received.
Where do I add the print log?
I believe that logging should be enabled by default in this example, over RTT. You can use J-Link RTT Viewer to see the logs.
You can increase the log-level output from application by setting this config to Debug/4 in your sdk_config.h file:
// <o> NRF_LOG_DEFAULT_LEVEL - Default Severity level // <0=> Off // <1=> Error // <2=> Warning // <3=> Info // <4=> Debug #ifndef NRF_LOG_DEFAULT_LEVEL #define NRF_LOG_DEFAULT_LEVEL 4 #endif
For more details about logging from OpenThread stack, see OpenThread logging.