Send/receive message from/to thread Device and global address using OpenThread API

RE: Send/receive message from/to thread Device and global address using OpenThread API

vipin das — Tue, 17 Jan 2023 12:45:41 GMT

Ok Charlie, I will create a new issue and start the discussion there.

Thanks for your support.

Regards

Vipin Das

RE: Send/receive message from/to thread Device and global address using OpenThread API

Charlie — Tue, 17 Jan 2023 12:19:45 GMT

Hi Vipin,

Thanks for your update. Unfortunately, I do not have much experience with the adaptation of TCP running on top of OpenThread.

I suggest you add an issue report to the original case and continue the discussion there.

Best regards,

Charlie

RE: Send/receive message from/to thread Device and global address using OpenThread API

vipin das — Tue, 17 Jan 2023 10:43:15 GMT

Hi Charlie,

Thank you for your reply.

I followed the discussion suggested by you (+) Error -22 in mqtt_connect() - nRF52840dk with Azure IoT Hub using OpenThread and TCP - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com) and adapted the necessary changes on echo client sample. The good thing is that I was able to ping our http server (https://mainnet.incubed.net) from the application.

[00:00:37.808,624] <dbg> in3_ot: ping_send: Ping Server:
[00:00:37.808,624] <dbg> in3_ot: print_ipv6_address: Mesh Local EID Address: fd97.6739.093e.0002.0000.0000.a756.5ef8
[00:00:37.809,265] <dbg> in3_ot: ping_send: ping send response:0
[00:00:37.809,295] <dbg> main: main: Connected to thread network
[00:00:37.895,446] <dbg> in3_ot: ping_reply_cb: Ping reply
[00:00:37.895,477] <dbg> in3_ot: print_ipv6_address: Mesh Local EID Address: fd97.6739.093e.0002.0000.0000.a756.5ef8
[00:00:47.460,449] <inf> net_l2_openthread: State changed! Flags: 0x00000064 Current role: router

But I am unable to send TCP packets to our HTTP server. Even I integrated the http client sample by thinking if the http header format is required to have proper communication. But nothing helps. Do you have any suggestions or thoughts on this. Logs collected as follows:

[00:00:30.631,896] <inf> usb_cdc_acm: Device resumed
[00:00:30.748,016] <inf> usb_cdc_acm: Device suspended
[00:00:30.987,182] <inf> usb_cdc_acm: Device resumed
[00:00:31.048,187] <inf> usb_cdc_acm: Device configured
[00:00:45.052,551] <inf> net_l2_openthread: State changed! Flags: 0x00004000 Current role: disabled
[00:00:45.053,192] <inf> net_l2_openthread: State changed! Flags: 0x00020000 Current role: disabled
[00:00:45.053,283] <inf> net_l2_openthread: State changed! Flags: 0x00040000 Current role: disabled
[00:00:45.053,375] <inf> net_l2_openthread: State changed! Flags: 0x00000100 Current role: disabled
[00:00:45.056,671] <inf> net_l2_openthread: State changed! Flags: 0x00010000 Current role: disabled
[00:00:45.056,762] <inf> net_l2_openthread: State changed! Flags: 0x00008000 Current role: disabled
[00:00:45.057,281] <inf> net_l2_openthread: State changed! Flags: 0x10000000 Current role: disabled
[00:00:45.057,556] <inf> net_l2_openthread: State changed! Flags: 0x10000000 Current role: disabled
[00:00:45.058,624] <inf> net_l2_openthread: State changed! Flags: 0x00001000 Current role: disabled
[00:00:45.058,807] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:45.058,837] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:45.058,929] <inf> net_l2_openthread: State changed! Flags: 0x00000001 Current role: disabled
[00:00:45.059,020] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:45.059,112] <inf> net_l2_openthread: State changed! Flags: 0x00000008 Current role: disabled
[00:00:45.059,234] <inf> net_l2_openthread: State changed! Flags: 0x01000000 Current role: disabled
[00:00:45.059,356] <inf> net_l2_openthread: State changed! Flags: 0x00000004 Current role: detached
[00:00:45.059,509] <inf> net_l2_openthread: State changed! Flags: 0x00000001 Current role: detached
[00:00:45.059,600] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:45.059,692] <inf> net_l2_openthread: State changed! Flags: 0x00001000 Current role: detached
[00:00:45.059,844] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:45.059,967] <inf> net_l2_openthread: State changed! Flags: 0x00001000 Current role: detached
[00:00:45.060,119] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:45.060,211] <inf> net_l2_openthread: State changed! Flags: 0x00000010 Current role: detached
[00:00:45.060,943] <inf> net_l2_openthread: State changed! Flags: 0x10000000 Current role: detached
[00:00:47.353,790] <inf> net_l2_openthread: State changed! Flags: 0x200012a4 Current role: child
[00:00:47.354,064] <inf> net_l2_openthread: State changed! Flags: 0x00000001 Current role: child
[00:00:47.354,187] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:47.354,217] <wrn> net_l2_openthread: No address info provided with event, please enable CONFIG_NET_MGMT_EVENT_INFO
[00:00:47.354,278] <dbg> in3_ot: ping_send: Ping Server:
[00:00:47.354,309] <dbg> in3_ot: print_ipv6_address: Mesh Local EID Address: fd97.6739.093e.0002.0000.0000.2e04.6974
[00:00:47.354,919] <dbg> in3_ot: ping_send: ping send response:0
[00:00:47.354,949] <dbg> main: main: Connected to thread network
[00:00:47.355,499] <dbg> net_tcp: tcp_conn_ref: (main): conn: 0x20033ad8, ref_count: 1
[00:00:47.355,529] <dbg> net_tcp: tcp_conn_alloc: (main): conn: 0x20033ad8
[00:00:47.355,743] <dbg> net_tcp: net_tcp_connect: (main): context: 0x20013594, local: ::, remote: fd97:6739:93e:2::2e04:6974
[00:00:47.355,895] <dbg> net_tcp: net_tcp_connect: (main): conn: 0x20033ad8 src: fd11:22::bd3f:a678:d35a:f0c1, dst: fd97:6739:93e:2::2e04:6974
[00:00:47.356,048] <dbg> net_tcp: tcp_in: (main):  [LISTEN Seq=1179184775 Ack=0]
[00:00:47.356,292] <dbg> net_tcp: tcp_out_ext: (main): SYN Seq=1179184775 Len=0
[00:00:47.356,445] <dbg> net_tcp: tcp_send_process_no_lock: (main): SYN Seq=1179184775 Len=0 
[00:00:47.356,689] <dbg> net_tcp: tcp_send: (main): SYN Seq=1179184775 Len=0
[00:00:47.357,055] <dbg> net_tcp: tcp_in: (main): LISTEN->SYN_SENT
[00:00:47.402,557] <dbg> in3_ot: ping_reply_cb: Ping reply
[00:00:47.402,587] <dbg> in3_ot: print_ipv6_address: Mesh Local EID Address: fd97.6739.093e.0002.0000.0000.2e04.6974
[00:00:47.564,208] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:47.564,422] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:47.771,697] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:47.771,942] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:47.979,217] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:47.979,431] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:48.186,706] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:48.186,950] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:48.394,226] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:48.394,439] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:48.601,715] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:48.601,959] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:48.809,234] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:48.809,448] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:49.016,723] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:49.016,967] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:49.224,243] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:49.224,456] <dbg> net_tcp: tcp_send: (tcp_work): SYN Seq=1179184775 Len=0
[00:00:49.431,732] <dbg> net_tcp: tcp_send_process_no_lock: (tcp_work): SYN Seq=1179184775 Len=0 in_retransmission
[00:00:49.431,793] <dbg> net_tcp: tcp_conn_unref_debug: (tcp_work): conn: 0x20033ad8, ref_count=1 (tcp_send_process():568)
[00:00:49.431,823] <dbg> net_tcp: tcp_conn_unref_debug: (tcp_work): conn: 0x20033ad8 is waiting on connect semaphore

Regards

Vipin Das

RE: Send/receive message from/to thread Device and global address using OpenThread API

Charlie — Fri, 06 Jan 2023 12:51:34 GMT

Hi Vipin,

ot cli has some commands related to DNS resolution: openthread/README.md at main · openthread/openthread (github.com)

You can learn about API usage from DNS command implementation.

Best regards,

Charlie

RE: Send/receive message from/to thread Device and global address using OpenThread API

vipin das — Fri, 06 Jan 2023 12:12:51 GMT

Hi Charlie,

Is there anyway, I can use any api to find the ipv6 address of any remote server by host name in OT/Zephyr stack.

To be more precise, in order to send a TCP packet to remote server(global ip address), I might need the ipv6 address of that server how do I find and handle using my application? Any reference implementation would help me.

Regards

Vipin Das

RE: Send/receive message from/to thread Device and global address using OpenThread API

vipin das — Tue, 03 Jan 2023 13:40:16 GMT

Hi Charlie,

It works if I ping fd1f:8fda:e9e0:2:0:0:808:808.

uart:~$ ot ping fd1f:8fda:e9e0:2:0:0:808:808
16 bytes from fd1f:8fda:e9e0:2:0:0:808:808: icmp_seq=6 hlim=113 time=36ms
1 packets transmitted, 1 packets received. Packet loss = 0.0%. Round-trip min/avg/max = 36/36.0/36 ms.
Done

Regards

Vipin Das

RE: Send/receive message from/to thread Device and global address using OpenThread API

Charlie — Tue, 03 Jan 2023 13:26:21 GMT

Hi Vipin,

It looks fd1f:8fda:e9e0:2:0:0::/96 should be used when converting your IPv4 address to IPv6.

What if you ping fd1f:8fda:e9e0:2:0:0:808:808 directly?

Best regards,

Charlie

RE: Send/receive message from/to thread Device and global address using OpenThread API

vipin das — Tue, 03 Jan 2023 09:35:36 GMT

Hi Charlie,

Happy New Year!!!

Thank you for your answers and sorry for late reply.

I setup the OTBR as per the page and formed the network. And followed the steps as mentioned by you. But I still have some issues. Below is my output from the OT CLI end device terminal.

uart:~$ ot networkkey
d6af7ff1a2fcf42743fd7a6989911d67
Done
uart:~$ 
uart:~$ ot ifconfig up
Done
uart:~$ 
uart:~$ ot thread start
Done
uart:~$ 
uart:~$ ot state
leader
Done
uart:~$ 
uart:~$ ot state child
Done
uart:~$ 
uart:~$ 
uart:~$ ot state
leader
Done
uart:~$ 
uart:~$ ot state router
Done
uart:~$ 
uart:~$ ot state router
Done
uart:~$ 
uart:~$ 
uart:~$ 
uart:~$ ot state
leader
Done
uart:~$ 
uart:~$ 
uart:~$ ot netdata show
Prefixes:
fd11:22:0:0::/64 paros med 2400
Routes:
fd1f:8fda:e9e0:2:0:0::/96 sn low 2400
fd70:77a5:30f0:1437::/64 s med 2400
Services:
44970 5d fddead00beef00000cd8cbff1e5c562fd11f s 2400
44970 01 76000500000e10 s 2400
Done
uart:~$ 
uart:~$ ot ping 8.8.8.8
Error 6: Parse
uart:~$ 
uart:~$ ot ping 2001:4860:4860:0:0:0:0:8888
1 packets transmitted, 0 packets received. Packet loss = 100.0%.
Done
uart:~$

Output of OTBR:

pi@pi:~ $ sudo ot-ctl state
router
Done
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ sudo ot-ctl ipaddr
fdde:ad00:beef:0:0:ff:fe00:fc11
fdde:ad00:beef:0:0:ff:fe00:fc38
fd11:22:0:0:5734:5484:47b:792d
fdde:ad00:beef:0:0:ff:fe00:fc10
fdde:ad00:beef:0:0:ff:fe00:2400
fdde:ad00:beef:0:cd8:cbff:1e5c:562f
fe80:0:0:0:1c0e:8cf:728e:e245
Done
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ sudo ot-ctl networkkey
d6af7ff1a2fcf42743fd7a6989911d67
Done
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ sudo ot-ctl state
router
Done
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ 
pi@pi:~ $ sudo ot-ctl netdata show
Prefixes:
fd11:22:0:0::/64 paros med 2400
Routes:
fd1f:8fda:e9e0:2:0:0::/96 sn low 2400
fd70:77a5:30f0:1437::/64 s med 2400
Services:
44970 5d fddead00beef00000cd8cbff1e5c562fd11f s 2400
44970 01 76000500000e10 s 2400
Done
pi@pi:~ $

Could you please tell me what could be possibly wrong in my case.

Regards

Vipin Das

RE: Send/receive message from/to thread Device and global address using OpenThread API

Charlie — Fri, 16 Dec 2022 08:57:04 GMT

Hi Vipin,

[quote user="vipin das"]Is there any way I can use TCP+SSL on Thread end device(nRF5340DK) instead of UDP. [/quote]

Yes, you can find solutions mentioned in (+) Error -22 in mqtt_connect() - nRF52840dk with Azure IoT Hub using OpenThread and TCP - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

[quote user="vipin das"]I am not quite successful in pinging a global address from my thread end device. [/quote]

Looks like your NAT64 prefix is already set to fd83:b72e:262d:2:0:0::/96. Which is the feedback when you run the ping command?

I recently followed Thread Border Router - Bidirectional IPv6 Connectivity and DNS-Based Service Discovery (openthread.io) to set up an OTBR and formed a Thread network through Web GUI with default setting. Run the following commands on OpenThread CLI device, the ping command to 8.8.8.8 just works.

ot networkkey 00112233445566778899aabbccddeeff 
ot networkkey 00112233445566778899aabbccddeeff
Done
ot ifconfig up
ot ifconfig up
Done
ot thread start
ot thread start
ot state
ot state
detached
Done
ot state
ot state
child
Done
ot state
ot state
child
Done
ot state router
ot state router
Done
ot state
ot state
router
Done
ot netdata show
ot netdata show
Prefixes:
fd8e:964d:9d85:1::/64 paos low 3000
Routes:
fd11:1111:1122:2222::/64 s med 3000
fd8e:964d:9d85:2:0:0::/96 sn low 3000
Services:
44970 01 32000500000e10 s 3000
44970 5d fd35e07c0372271ee4a005368966fa59d11f s 3000
Done
ot ping 8.8.8.8
ot ping 8.8.8.8
Pinging synthesized IPv6 address: fd8e:964d:9d85:2:0:0:808:808
16 bytes from fd8e:964d:9d85:2:0:0:808:808: icmp_seq=1 hlim=53 time=38msua

1 packets transmitted, 1 packets received. Packet loss = 0.0%. Round-trip min/avg/max = 38/38.0/38 ms.
Done

[quote user="vipin das"]I am bit confused with ifconfig up / thread start commands done in BR side as well as End device side. Could you please tell me what I should do to make RPi+Dongle side as Router only and nRF5340 side as Child. Few times I noticed in my configuration that BR side as well as End device side as leader. [/quote]

You need to form the network on OTBR first, then turn on and configure the child device to join the formed network, it will become child first then turn to router, you can also set its role with "ot state router".

Best regards,

Charlie

RE: Send/receive message from/to thread Device and global address using OpenThread API

vipin das — Thu, 15 Dec 2022 15:12:06 GMT

Hi Charlie,

Thanks for your reply. I will take a look at the samples you mentioned.

I have few more questions.

Is there any way I can use TCP+SSL on Thread end device(nRF5340DK) instead of UDP.
I am not quite successful in pinging a global address from my thread end device. I followed many Q&A discussions and also some other discussions as well. Could you please give some insights on that. I did set the route/prefix for global addressing. Current route output is

pi@pi:~ $ sudo ip -6 route
::1 dev lo proto kernel metric 256 pref medium
fd11:22::/64 dev wpan0 proto kernel metric 256 pref medium
fd70:77a5:30f0:1437::/64 dev eth0 proto kernel metric 256 expires 1603sec pref medium
fdde:ad00:beef::/64 dev wpan0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev wlan0 proto kernel metric 256 pref medium
fe80::/64 dev wpan0 proto kernel metric 256 pref medium
pi@pi:~ $

pi@pi:~ $ sudo ot-ctl netdata show
Prefixes:
fd11:22:0:0::/64 paros med 6000
Routes:
fd83:b72e:262d:2:0:0::/96 sn low 6000
fd70:77a5:30f0:1437::/64 s med 6000
Services:
44970 5d fddead00beef0000869fa0cfca6b6ce3d11f s 6000
44970 01 3a000500000e10 s 6000
Done
pi@pi:~ $

I am bit confused with ifconfig up / thread start commands done in BR side as well as End device side. Could you please tell me what I should do to make RPi+Dongle side as Router only and nRF5340 side as Child. Few times I noticed in my configuration that BR side as well as End device side as leader.

Looking forward to your reply.

Thanks

Vipin Das

RE: Send/receive message from/to thread Device and global address using OpenThread API

Charlie — Wed, 14 Dec 2022 13:26:08 GMT

Hi Vipin,

CoAP/UDP is normally used on top of the Thread network by your application.

You can refer to the sample mentioned here: (+) OpenThread COAP Client to a public server over Internet - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com)

Best regards,

Charlie