MQTT connection fail while "THREAD_RADIO_MODE_RX_OFF_WHEN_IDLE" - SED

[Maboo]

Hi,

I use a pca10056 with the "mqttsn_sleepy_publisher" example. Unfortunately, I cant connect to the mqttsn gateway. It throws me:

"NRF_LOG_ERROR("CONNECT message could not be sent. Error: 0x%x\r\n", err_code);"

I use the standard code for the DK and the border router. I just formed my own thread network and adjusted the credentials (panid ...) within the DK. Connecting and transmitting with radio ON works fine. 

I have found that ticket. So I guess it might has something to do with those values:

#define DEFAULT_CHILD_TIMEOUT    40                                     /**< Thread child timeout [s]. */
#define DEFAULT_POLL_PERIOD      1000                                     /**< Thread Sleepy End Device polling period when MQTT-SN Asleep. [ms] */
#define SHORT_POLL_PERIOD        100                                      /**< Thread Sleepy End Device polling period when MQTT-SN Awake. [ms] */
#define SEARCH_GATEWAY_TIMEOUT   5                                          /**< MQTT-SN Gateway discovery procedure timeout in [s]. */                                   

Do you have any idea, whether those values need to change? I know what they should do, but changing them didnt help much. 

Ps: I use Linux, SDK17, VS-Code, pca10056

[Simonr]

Hi

Are you using the exact same configurations for the border router and MQTT-SN gateway as we use in out border router image? Have you tested the provided border router image to see if the examples works correctly with this? Please make sure to follow the instructions in Testing closely.

If possible, can you upload a sniffer trace showing on-air communication between the devices? Please check out the nRF Sniffer for 802.15.4 for example that can be used to capture packetrs transmitted on protocols based on IEEE 802.15.4, like Thread for instance.

Best regards,

Simon

[Maboo]

Hi Simonr,

thanks a lot for your answer. I tested the setting with a freshly flashed border router and DK with standard software and it still doesn't work. But when I reflashed the border router I came across a change I made (found it in my notes 6 month ago) after the flash. 6 month ago, I had the same problem with the mqttsn gateway, but with a normal enddevice (not sleepy enddevice). I used the example "mqttsn_client_publisher". The solution was to change the "GatewayUDP6Broadcast" address in /etc/paho-mqtt-sn-gateway.conf to "ff03::1" fitting the address in the SDK. After restarting the gateway, everything worked fine. Now, I thought maybe that is the problem, so I changed it back to the original one "ff33:40:fdde:ad00:beef:0:0:1", but it didn't work neither. Do you think it has something to do with that address because the discription inside the conf says:

# GatewayUDP6Broadcast address is set to all Thread devices address
# in order to enable Thread Sleepy Devices to receive multicast messages
# sent from the gateway.

Greetings

Maboo

[Øyvind]

Hello, 

Simon is currently on vacation, so I will follow-up while he is away. 

Can you please export the Wireshark results to a text file? Also, you mentioned

It throws me:

"NRF_LOG_ERROR("CONNECT message could not be sent. Error: 0x%x\r\n", err_code);"

 What error code do you get? Can you provide the UART output from the device? Are there any indications on the border router?

Thanks.

Kind regards,
Øyvind

[Maboo]

Hi,

thanks for taking over. Unfortunately I can't provide any UART Output since I don't use SEGGER. I just have the Thread CLI via putty in FTD mode. In SED mode even that isn't working. Is it even possible to route NRF_LOG_INFO to the Thread CLI? 

I used the LEDs for debugging the error, I know it enters the error condition, but I don't know what causes the actual error.

The border router works fine, as long as I use the "ff03::1" address for the"GatewayUDP6Broadcast" address in /etc/paho-mqtt-sn-gateway.conf and FTD mode. Changing it back to the standard address "ff33:40:fdde:ad00:beef:0:0:1" it's not working regardless of the device mode (SED or FTD).

Here is the wpan status from the border router

wpan0 => [
	"NCP:State" => "associated"
	"Daemon:Enabled" => true
	"NCP:Version" => "OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr  5 2020 21:51:18"
	"Daemon:Version" => "0.08.00d (; Apr 21 2020 19:11:43)"
	"Config:NCP:DriverName" => "spinel"
	"NCP:HardwareAddress" => [F4CE36791D40C566]
	"NCP:Channel" => 11
	"Network:NodeType" => "leader"
	"Network:Name" => "OpenThreadDemo"
	"Network:XPANID" => 0x1111111122222222
	"Network:PANID" => 0xABCD
	"IPv6:LinkLocalAddress" => "fe80::1028:6768:6ee4:2727"
	"IPv6:MeshLocalAddress" => "fd11:1111:1122:0:3ab1:cb84:a673:bf93"
	"IPv6:MeshLocalPrefix" => "fd11:1111:1122::/64"
	"com.nestlabs.internal:Network:AllowingJoin" => false
]

And here is the Wireshark result (I used the same setting then before):

Frame 1: 108 bytes on wire (864 bits), 108 bytes captured (864 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: 12:28:67:68:6e:e4:27:27, Src: a2:28:b5:49:e1:a5:77:5f
6LoWPAN, Src: fe80::a028:b549:e1a5:775f, Dest: fe80::1028:6768:6ee4:2727
Internet Protocol Version 6, Src: fe80::a028:b549:e1a5:775f, Dst: fe80::1028:6768:6ee4:2727
User Datagram Protocol, Src Port: 19788, Dst Port: 19788
Mesh Link Establishment
Data (39 bytes)

0000  ba 61 9d 87 7c 69 c6 e0 be 27 da e1 0f 72 d4 f1   .a..|i...'...r..
0010  a3 c6 7d 9f f4 5f 8f ac c8 eb 53 55 5e b9 2e 06   ..}.._....SU^...
0020  aa 20 96 c6 37 e8 ef                              . ..7..

Frame 2: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 1

Frame 3: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 4: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 2

Frame 5: 99 bytes on wire (792 bits), 99 bytes captured (792 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: a2:28:b5:49:e1:a5:77:5f, Src: 12:28:67:68:6e:e4:27:27
6LoWPAN, Src: fe80::1028:6768:6ee4:2727, Dest: fe80::a028:b549:e1a5:775f
Internet Protocol Version 6, Src: fe80::1028:6768:6ee4:2727, Dst: fe80::a028:b549:e1a5:775f
User Datagram Protocol, Src Port: 19788, Dst Port: 19788
Mesh Link Establishment
Data (30 bytes)

0000  26 57 ea f6 ad 21 b4 29 c3 0e b7 f6 8a 93 54 40   &W...!.)......T@
0010  eb a1 57 de 94 9a 75 1d 83 4c 63 93 f3 64         ..W...u..Lc..d

Frame 6: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 29

Frame 7: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 8: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 3

Frame 9: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 10: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 4

Frame 11: 95 bytes on wire (760 bits), 95 bytes captured (760 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: Broadcast, Src: 12:28:67:68:6e:e4:27:27
6LoWPAN, Src: fe80::1028:6768:6ee4:2727, Dest: ff02::1
Internet Protocol Version 6, Src: fe80::1028:6768:6ee4:2727, Dst: ff02::1
User Datagram Protocol, Src Port: 19788, Dst Port: 19788
Mesh Link Establishment
Data (31 bytes)

0000  ca 69 e0 42 32 2f 7d e6 84 c7 36 88 b2 a8 12 ec   .i.B2/}...6.....
0010  87 f8 32 bf bc 40 a0 5c d8 f9 05 af ae c1 6e      ..2..@.\......n

Frame 12: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 13: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 5

Frame 14: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 15: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 6

Frame 16: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 17: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 7

Frame 18: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 19: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 8

Frame 20: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 21: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 9

Frame 22: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 23: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 10

Frame 24: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 25: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 11

Frame 26: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 27: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 12

Frame 28: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 29: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 13

Frame 30: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 31: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 14

Frame 32: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 33: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 15

Frame 34: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 35: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 16

Frame 36: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 37: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 17

Frame 38: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 39: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 18

Frame 40: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 41: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 19

Frame 42: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 43: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 20

Frame 44: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 45: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 21

Frame 46: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 47: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 22

Frame 48: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 49: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 23

Frame 50: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 51: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 24

Frame 52: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 53: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 25

Frame 54: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 55: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 26

Frame 56: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 57: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 27

Frame 58: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 59: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 28

Frame 60: 79 bytes on wire (632 bits), 79 bytes captured (632 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: 0xf000, Src: 0xf00a
Data (32 bytes)

0000  e9 33 9b 60 23 60 44 20 a7 1e dc e6 91 e6 0b 88   .3.`#`D ........
0010  7b f4 82 f3 d4 4e 79 ed d7 bd fc f8 16 ef 27 37   {....Ny.......'7

Frame 61: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 29

Frame 62: 94 bytes on wire (752 bits), 94 bytes captured (752 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: Broadcast, Src: 0xf000
Data (47 bytes)

0000  1f 89 68 c2 55 ed ca df f8 64 8d 93 a5 01 4c 92   ..h.U....d....L.
0010  53 27 d5 36 ed c6 79 ce 2e 0b f6 0d f6 3a 55 a6   S'.6..y......:U.
0020  f6 82 7a 88 22 13 1a 33 f0 43 39 50 78 17 f7      ..z."..3.C9Px..

Frame 63: 94 bytes on wire (752 bits), 94 bytes captured (752 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: Broadcast, Src: 0xf000
Data (47 bytes)

0000  fb 5d 27 1e b1 70 aa 0d f1 05 17 45 4f 6b 83 31   .]'..p.....EOk.1
0010  36 8c 3d 9d 58 53 e7 70 5c 0f 49 0f 81 d0 83 ee   6.=.XS.p\.I.....
0020  59 6e 01 6e 58 b8 dd 1e 13 4f c8 cf 75 a9 a3      Yn.nX....O..u..

Frame 64: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 65: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 30

Frame 66: 80 bytes on wire (640 bits), 80 bytes captured (640 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: Broadcast, Src: 0xf000
Data (33 bytes)

0000  44 dd ec 0b 0a 9c 3f cd 47 59 d6 eb 5a 0e 94 47   D.....?.GY..Z..G
0010  c6 3d f3 41 8e d4 ac e1 46 22 bb b6 9b 7e 83 9c   .=.A....F"...~..
0020  da                                                .

Frame 67: 80 bytes on wire (640 bits), 80 bytes captured (640 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Data, Dst: Broadcast, Src: 0xf000
Data (33 bytes)

0000  fa 46 de 4f 83 b0 1d f6 da 3b 53 43 66 9f a9 11   .F.O.....;SCf...
0010  0b 8b 05 82 3e b8 fb 52 a2 e7 29 bd 13 25 f0 4b   ....>..R..)..%.K
0020  0a                                                .

Frame 68: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 69: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 31

Frame 70: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 71: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 32

Frame 72: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 73: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 33

Frame 74: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 75: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 34

Frame 76: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 77: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 35

Frame 78: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 79: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 36

Frame 80: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 81: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 37

Frame 82: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 83: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 38

Frame 84: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 85: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 39

Frame 86: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 87: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 40

Frame 88: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 89: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 41

Frame 90: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 91: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 42

Frame 92: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 93: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 43

Frame 94: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 95: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 44

Frame 96: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 97: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 45

Frame 98: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 99: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 46

Frame 100: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 101: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 47

Frame 102: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 103: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 48

Frame 104: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 105: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 49

Frame 106: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 107: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 50

Frame 108: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 109: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 51

Frame 110: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 111: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 52

Frame 112: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 113: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 53

Frame 114: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 115: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 116: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 54

Frame 117: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 118: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 55

Frame 119: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 120: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 56

Frame 121: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 122: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 57

Frame 123: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 124: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 58

Frame 125: 48 bytes on wire (384 bits), 48 bytes captured (384 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Command, Dst: 0xf000, Src: 0xf00a

Frame 126: 31 bytes on wire (248 bits), 31 bytes captured (248 bits) on interface /tmp/wireshark_extcap_-dev-ttyACM2_20210707095934_8gQO4O, id 0
IEEE 802.15.4 TAP
IEEE 802.15.4 Ack, Sequence Number: 59

Kind regards,

Maboo

[Maboo]

I managed to get JLink-RTT-Viewer up running. These are the logging results.

Test 1:
Settings:
* GatewayUDP6Broadcast = ff03::1
* FTD
 Results:

<info> app_timer: RTC: initialized.
<info> app: Thread version   : OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr  5 2020 21:51:18
<info> app: Network name     : OpenThreadDemo
<info> app: Thread interface has been enabled.
<info> app: 802.15.4 Channel : 11
<info> app: 802.15.4 PAN ID  : 0xABCD
<info> app: Radio mode       : rx-on-when-idle
<warning> app_timer: RTC instance already initialized.
<info> app: State changed! Flags: 0x011FD33D Current role: 1

<info> app: State changed! [0000024087] TEST
<error> app: TEST
<info> app: TEST
TEST<info> app: MQTT-SN event: Client has found an active gateway.

<info> app: MQTT-SN event: Gateway discovery procedure has finished.

<info> app: MQTT-SN event: Gateway discovery result: 0x0.

<info> app: MQTT-SN event: Client connected.

<info> app: MQTT-SN event: Client registered topic.

<info> app: MQTT-SN event: Topic has been registered with ID: 1.

<info> app: MQTT-SN event: Client has successfully published content.

Test 2:
Settings:
* GatewayUDP6Broadcast = ff03::1
* SED
Results:

SEGGER J-Link V7.50 - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20 V1.0, SN=683835218
Process: JLinkExe
<info> app_timer: RTC: initialized.
<info> app: Thread version   : OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr  5 2020 21:53:43
<info> app: Network name     : OpenThreadDemo
<info> app: Thread interface has been enabled.
<info> app: 802.15.4 Channel : 11
<info> app: 802.15.4 PAN ID  : 0xABCD
<info> app: Radio mode       : rx-off-when-idle
<warning> app_timer: RTC instance already initialized.
<info> app: State changed! Flags: 0x0117D33D Current role: 1

<info> app: State changed!<info> app: MQTT-SN event: Gateway discovery procedure has finished.

<info> app: MQTT-SN event: Gateway discovery result: 0x3.

<error> app: CONNECT message could not be sent. Error: 0xE

Test 3:
Settings:
* GatewayUDP6Broadcast = ff33:40:fdde:ad00:beef:0:0:1
* FTD
Results:

SEGGER J-Link V7.50 - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20 V1.0, SN=683835218
Process: JLinkExe
<info> app_timer: RTC: initialized.
<info> app: Thread version   : OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr  5 2020 21:51:18
<info> app: Network name     : OpenThreadDemo
<info> app: Thread interface has been enabled.
<info> app: 802.15.4 Channel : 11
<info> app: 802.15.4 PAN ID  : 0xABCD
<info> app: Radio mode       : rx-on-when-idle
<warning> app_timer: RTC instance already initialized.
<info> app: State changed! Flags: 0x011FD33D Current role: 1

<info> app: State changed! [0000577562] TEST
<error> app: TEST
<info> app: TEST
TEST<info> app: MQTT-SN event: Gateway discovery procedure has finished.

<info> app: MQTT-SN event: Gateway discovery result: 0x3.

<error> app: CONNECT message could not be sent. Error: 0xE

<error> app: CONNECT message could not be sent. Error: 0xE

Test 4:
Settings:
* GatewayUDP6Broadcast = ff33:40:fdde:ad00:beef:0:0:1
* SED
Results:

SEGGER J-Link V7.50 - Real time terminal output
J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20 V1.0, SN=683835218
Process: JLinkExe
<info> app_timer: RTC: initialized.
<info> app: Thread version   : OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr  5 2020 21:53:43
<info> app: Network name     : OpenThreadDemo
<info> app: Thread interface has been enabled.
<info> app: 802.15.4 Channel : 11
<info> app: 802.15.4 PAN ID  : 0xABCD
<info> app: Radio mode       : rx-off-when-idle
<warning> app_timer: RTC instance already initialized.
<info> app: State changed! Flags: 0x0117D33D Current role: 1

<info> app: State changed!<info> app: MQTT-SN event: Gateway discovery procedure has finished.

<info> app: MQTT-SN event: Gateway discovery result: 0x3.

<error> app: CONNECT message could not be sent. Error: 0xE

[Carl Richard]

Hello, Maboo!

Apologies for the very late response on your question. We have been understaffed due to the summer holiday here in Norway. Øyvind went on holiday himself, so I have taken over your case. 

First, thank you for the extensive logs. The result you see in Test 2 is expected, as SEDs doesn't support multicast address "ff03::1". I reached out to a colleague about the issue with the other address. It seems like you may be using the wrong mesh-local prefix. The default (from wpan status) should be: 

"IPv6:MeshLocalPrefix" => "fdde:ad00:beef::/64"

but you have,

"IPv6:MeshLocalPrefix" => "fd11:1111:1122::/64"

You must change the address to match the network prefix.

Best regards,
Carl Richard

[Maboo]

Hi Carl Richard,

Sorry for my very late reply, I was on holiday as well. First, thanks alot for your reply. It helped me alot, to understand where the problem lies. Still, I don't quite understand where I can change my MeshLocalPrefix. I tried to figure it out by reading the Open Thread - Get Started, but I couldn't. I am somehow confused, since the GatewayUDP6Broadcast address is another parameter. 

1. Could you recommend a website/tutorial just to better understand the network parameters? (Open Thread website was a good start, but it doesn't goes that deep)
2. Where can I change the MeshLocalPrefix?
3. What is the difference between the MeshLocalPrefix and the OnMeshPrefix?

Greetings Maboo

[Edvin]

Hello Maboo,

I'll handle this ticket, since Carl Richard is currently out of office. 

Maboo said:

Where can I change the MeshLocalPrefix?

I am not sure you can change this, or if it is just given when the network forms. Is there a particular reason why you want to change this?

Maboo said:

1. What is the difference between the MeshLocalPrefix and the OnMeshPrefix?

Where did you find "OnMeshPrefix"? A quick search on the openthread - get started guide didn't give any search results. Perhaps you can show me where you found it?

Maboo said:

Could you recommend a website/tutorial just to better understand the network parameters? (Open Thread website was a good start, but it doesn't goes that deep)

I am not aware of any other guides that go that much deeper. I guess you can check with Open Thread's website and forums. 

Best regards,

Edvin

[Maboo]

Hi Edvin,

thanks for taking over. Basically I struggling with the answer from Carl Richard.

Carl Richard said:

You must change the address to match the network prefix

What address? Does he mean the "GatewayUDP6Broadcast" address in /etc/paho-mqtt-sn-gateway.conf. And how do I form/change the address to match the network prefix? (==mesh local prefix???).

I found this on Open Thread webpage:

You might notice that Sleepy End Devices (SEDs) are not included as a recipient in the multicast table above. Instead, Thread defines link-local and realm-local scope unicast prefix-based IPv6 multicast address used for All Thread Nodes, including SEDs. These multicast addresses vary by Thread network, because it is built on the unicast Mesh-Local prefix (see RFC 3306 for more details on unicast-prefix-based IPv6 multicast addresses).

But the explanations on the RFC 3306 webside are too confusing for me.

The problem why I ask is, as long as I use the standard values from nRF it would work I guess. But when I create my own network it automatically creates its own mesh local prefix (learned this last week). That is the point were I need to understand how to change or form the right address to match it.

Ps: The OnMeshPrefix is located under "/etc/border_router.conf.

Best regards,

Markus

[Edvin]

Sorry for the late answer. I am struggling a bit to understand where you are stuck, and what the issue is.

<p>I am not familiar with this website. Have you tried to check openthread's own <a href="">openthread.io/.../a> or guides?</p>

Maboo said:

But the explanations on the RFC 3306 webside are too confusing for me.

I am not familiar with this website. Have you tried to check out openthread's own documentation or guides?

Maboo said:

The problem why I ask is, as long as I use the standard values from nRF it would work I guess. But when I create my own network it automatically creates its own mesh local prefix (learned this last week).

What works and what do you change, and what doesn't work after you change it? Is this something that I can reproduce using a couple of nRF52840 DKs?

I guess you have stumbled upon this guide? If not, perhaps it will answer some of your questions?

Best regards,

Edvin

[Maboo]

Hi Edvin,

my goal is to form my own thread network and let several SED (Sleepy End Devices - rx-off-when-idle) communicate with the border router -> Homeassistant. That means the SED wakes up every 5 min and publishes a status update. Homeassistant subscribes to the SED topic and displays the new status.

When I form my own thread network (you can do this on the local border router website). I can connect all the sensors as FTD (Full Thread Device - rx-on-when-idle) and the thread network works perfectly.

When I flash them as an SED (rx-off-when-idle) I think I need to change "GatewayUDP6Broadcast" address in /etc/paho-mqtt-sn-gateway.conf. to fit the new MeshLocalPrefix (which was created by forming the network) [see below] Otherwise the SED won't find a gateway.

wpan0 => [
"NCP:State" => "associated"
"Daemon:Enabled" => true
"NCP:Version" => "OPENTHREAD/20191113-00534-gc6a258e3; NRF52840; Apr 5 2020 21:51:18"
"Daemon:Version" => "0.08.00d (; Apr 21 2020 19:11:43)"
"Config:NCP:DriverName" => "spinel"
"NCP:HardwareAddress" => [F4CE36791D40C566]
"NCP:Channel" => 11
"Network:NodeType" => "leader"
"Network:Name" => "OpenThreadDemo"
"Network:XPANID" => 0x1111111122222222
"Network:PANID" => 0xABCD
"IPv6:LinkLocalAddress" => "fe80::1028:6768:6ee4:2727"
"IPv6:MeshLocalAddress" => "fd11:1111:1122:0:3ab1:cb84:a673:bf93"
"IPv6:MeshLocalPrefix" => "fd11:1111:1122::/64"
"com.nestlabs.internal:Network:AllowingJoin" => false
]

If I am using the statndard network parameters from nrf, the standard MeshLocalPrefix from nrf is: "fdde:ad00:beef::/64" and the standard GatewayUDP6Broadcast is "ff33:40:fdde:ad00:beef:0:0:1". As you can see, it somehow fits. And everthing works, even if I flash it as SED.

But if I form my own network, my MeshLocalPrefix is "fd11:1111:1122::/64", so it doesn't fit to the GatewayUDP6Broadcast address anymore + the SED can't connect to the gateway. So now is the question, do I have to create a new fitting GatewayUDP6Broadcast or is there even more I have to change to get the SED connecting to the thread network?

The answer from Carl Richard suggested I must change the address to match the network prefix.

But how do i do it? And which address does he mean? GatewayUDP6Broadcast? Or am I wrong here?

Carl Richard said:

First, thank you for the extensive logs. The result you see in Test 2 is expected, as SEDs doesn't support multicast address "ff03::1". I reached out to a colleague about the issue with the other address. It seems like you may be using the wrong mesh-local prefix. The default (from wpan status) should be: 

Fullscreen

1

"IPv6:MeshLocalPrefix" => "fdde:ad00:beef::/64"

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

"IPv6:MeshLocalPrefix" => "fdde:ad00:beef::/64"

but you have,

Fullscreen

1

"IPv6:MeshLocalPrefix" => "fd11:1111:1122::/64"

XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

"IPv6:MeshLocalPrefix" => "fd11:1111:1122::/64"

You must change the address to match the network prefix.

Ps: the openthread documentation doesn't help me here. Regarding SEDs it just refers to the RFC 3306 webside.

[Edvin]

Hello,

Sorry for the late reply. I have tried a couple of times to get a OTBR up and running but so far with no luck. 

I believe that the MQTT-SN Gateway uses a realm-local all thread nodes multicast address. By default the "gatewayUDP6Broadcast" address is ff33:40:fdde:ad00:beef:0:0:1. This is a multicast address defined in Thread, so all Thread devices are reached with that particular mesh-local prefix (default fdde:ad00:beef). If you use another prefix address, you need to change that in the paho configuration to use your new prefix. 

I see that it looks like you already changed this. But I can't see that it is used in the sniffer trace that you uploaded a screenshot of earlier (and I can't see that you uploaded the actual sniffer trace, but perhaps I just can't see it. Please correct me if I am wrong). 

This is quite down the openthread specification rabbit hole. If I knew the answer I would tell you immediately, but I can try to figure it out together with you. You may want to open some communication in an openthread forum as well, as you may get help quicker there. 

Best regards,

Edvin