Thread Border Router networking fail

RE: Thread Border Router networking fail

Jørgen Holmefjord — Wed, 09 Dec 2020 14:13:37 GMT

Hi Rick,

Unfortunately, this is not something we can assist with. Router configuration is way outside of our area of expertise, I'm sure you can find some help with this on OpenWRT forum or similar.

I only tested this briefly a few years ago with a Netgear WNR3500v2/RangeMax N300 router. I do not remember exactly which firmware I used.

Best regards,
Jørgen

RE: Thread Border Router networking fail

Rick — Tue, 08 Dec 2020 02:05:03 GMT

Hi Jørgen

How are you today!
now I need to test IPv6 /56 prefix from OpenWRT.
Pls kindly help advise any support list for OpenWRT Router and support version for OpenWRT?
Asus Router or other?

Best Regards,
Rick.

RE: Thread Border Router networking fail

Rick — Thu, 26 Nov 2020 15:03:29 GMT

OK, I go to check ISP provide WAN, thanks.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Thu, 26 Nov 2020 14:52:57 GMT

Yes, you need ISP to provide you with a WAN prefix same or lower than the one you want assigned to the subnet. If you want /56 subnet to border router/LAN prefix, you need at least /56 prefix from ISP.

RE: Thread Border Router networking fail

Rick — Thu, 26 Nov 2020 14:50:56 GMT

Hi Jørgen

This is my Router Setting, Pls looking it and check the green block it, this you say WAN prefix of 64?
So I need ISP support WAN prefix of 48?

RE: Thread Border Router networking fail

Jørgen Holmefjord — Thu, 26 Nov 2020 14:39:46 GMT

If you have a WAN prefix of 64, you will not be able to make the router set a 56 prefix for the LAN address, the WAN subnet needs to be large in order to provide larger subnets.

When I have tested this, I was assigned a 48 prefix address from my ISP, and was able to get a 56 subnet to the Border Router.

RE: Thread Border Router networking fail

Rick — Thu, 26 Nov 2020 14:25:51 GMT

Hi Jørgen

Thank you for your reply.

My ISP support static IPv6 information, So I setting the config to static IPv6, I try setting "Stateful" and "Stateless" , it not share /62 prefix.

Best Regards.
Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Thu, 26 Nov 2020 12:24:02 GMT

This must be configured in the router, not in the RPi. See this page about configuring IPv6 in Asus routers.

Try setting the config to Native, and set "Stateful" Auto Configuration Setting.

Like I said, I'm not sure if the Asus routers are able to support non-SLAAC setup. This is something you should check with Asus.

RE: Thread Border Router networking fail

Rick — Thu, 26 Nov 2020 02:52:56 GMT

Hi Jørgen

How can I setting enable DHCPv6 service for Rpi and disable autoconfig?

The Thread Border Router WEB steps description,

When dealing with the native IPv6 connectivity, make sure you use the DHCPv6 service and not the popular Stateless Address Autoconfiguration (SLAAC) tool. This autoconfig tool will only provide a 64-bit long prefix that is not sufficient to delegate a new 64-bit long prefix for the Thread network.

nRF52840 DK Version：nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\examples\thread\ncp\ftd\uart\hex

Raspberry Pi 3 Version：RaspPi_OT_Border_Router_Demo_v4.1.0-1.alpha

Best Regards.
Rick.

RE: Thread Border Router networking fail

Rick — Wed, 25 Nov 2020 14:39:34 GMT

Hi Jørgen

Thank you for your reply.

now I go to contact the manufacturer of the router (Asus) to get help on configuration and details about whether this router can support larger address spaces.
Thanks.
Best Regards.
Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Wed, 25 Nov 2020 14:28:56 GMT

Hi,

I do not think that "RaspPi_Thread_Border_Router_Demo_v0.11.0-1.alpha.img" is setup to work as a router, even though it runs on the OpenWRT firmware. This is a very old version of the border router, and it is not compatible with the latest SDK. I would not recommend using this.

It would probably be much simpler to get a router that supports this, instead of having to do a lot of setup/hacking to make this work on a Raspberry Pi/Custom router. Unfortunately, we cannot provide any support on this. You will have to get help from some open-source communities if you want to go down that road.

Best regards,
Jørgen

RE: Thread Border Router networking fail

Rick — Wed, 25 Nov 2020 12:02:03 GMT

Hi Jørgen,

Thank you for your reply.

now i don't have OpenWRT device,

Could you Support me "RaspPi_Thread_Border_Router_Demo_v0.11.0-1.alpha.img", because it looking can support OpenWRT in Rpi?

I get the information from the website" https://infocenter.nordicsemi.com/index.jsp?topic=%2Fcom.nordic.infocenter.threadsdk.v0.11.0%2Fthread_border_router.html "

Best Regards,

Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Wed, 25 Nov 2020 11:29:57 GMT

Hi,

I do not have this router available, so unfortunately I'm not able to help you with configuration of this. You should contact the manufacturer of the router (Asus) to get help on configuration and details about whether this router can support larger address spaces. I have only been able to get this to work with a router running OpenWRT firmware, but I have not tested on a large number of devices..

Best regards,
Jørgen

RE: Thread Border Router networking fail

Rick — Wed, 25 Nov 2020 06:31:07 GMT

Hi Jørgen:

Now I have support IPv6 from ISP and Router is (ASUS RT-AX56U)，but I still not get /62 prefix.

this is my ifconfig from RPi .

pi@raspberrypi:~ $ ifconfig eth0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500

        inet 192.168.50.103  netmask 255.255.255.0  broadcast 192.168.50.255

        inet6 2001:b030:214e:2200:****:****:****:****  prefixlen 64  scopeid 0x0<global>

        inet6 fe80::ba27:ebff:feda:4146  prefixlen 64  scopeid 0x20<link>

        ether b8:27:eb:da:41:46  txqueuelen 1000  (Ethernet)

        RX packets 870  bytes 76151 (74.3 KiB)

        RX errors 0  dropped 0  overruns 0  frame 0

        TX packets 530  bytes 78362 (76.5 KiB)

        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

and the WEB steps description, How can I setting DHCPv6 service for Rpi and disable autoconfig?

Best Regards,

Rick.

RE: Thread Border Router networking fail

Rick — Wed, 23 Sep 2020 09:29:56 GMT

Hi Jørgen:

I created a new thread is Thread MQTT-SN Example publish and subscribe can not combine operations ,

Pls kindly help advise how to solve it?

Best Regards,

Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Wed, 23 Sep 2020 08:37:09 GMT

Hi Rick,

Your latest questions is getting far outside of the topic of this thread. Can you please post it in a new thread, to prevent this from getting too messy? That will help other users with similar questions find the information much more easily.

If you do that, we will try to help you achieve what you want.

Best regards,
Jørgen

RE: Thread Border Router networking fail

Rick — Tue, 22 Sep 2020 15:46:11 GMT

Hi Jørgen,

1. I did not use the publish of two devices.
I use this example "Thread MQTT-SN Example".
Use one device of the MQTT-SN Subscriber application and other one device of the MQTT-SN Publisher application. (one publish device, one subscribe device)

2. Yes, two subscribers well the same problems too. do you have any advice that can solve the problems of two subscribers?

3. Now I have two devices, wanted to combine operations publish and subscribe at the same time in the device.
Pls kindly help advise how to solve it?

Best Regards,

Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Tue, 22 Sep 2020 14:48:45 GMT

I only tested the publisher, as it looked like this was the one you are using.

Are you having problem with two subscribers as well? You did not mention that you wanted to combine these operations, that may require large modifications of the examples.

RE: Thread Border Router networking fail

Rick — Tue, 22 Sep 2020 14:33:33 GMT

Hi Jørgen,

Thank you for your reply.

if work is to disconnect after each node is done publishing, it can subscribe MQTT?
because I follow the WEB steps below Playing with Thread and MQTT-SN on Nordic nRF52840, I need support to publish and subscribe at the same time in the device.

Pls kindly help advise how to solve it?

Best Regards,

Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Tue, 22 Sep 2020 14:13:50 GMT

Hi Rick,

I tested this on my end, and I am seeing the same behavior. I believe that the unhandled event message happens because the second board is in a state where it does not expect to receive this event when the first board does a Gateway search. The examples are most likely not written with multiple publishers in mind.

I'm not sure if the limitation is in the example code, or in the configuration of the Eclipse Paho MQTT-SN Gateway on the Raspberry Pi, but a workaround that seems to work is to disconnect after each node is done publishing (by pushing button 3), and reconnecting (by pressing button 3) on the second board before pressing button 4 to publish a message. You can also integrate this into a single button-press:

case BSP_EVENT_KEY_3:
{
    uint32_t err_code;

    if (mqttsn_client_state_get(&m_client) == MQTTSN_CLIENT_DISCONNECTED)
    {
        err_code = mqttsn_client_connect(&m_client, &m_gateway_addr, m_gateway_id, &m_connect_opt);
        if (err_code != NRF_SUCCESS)
        {
            NRF_LOG_ERROR("CONNECT message could not be sent. Error: 0x%x\r\n", err_code);
        }
    }
    while(ready_to_publish == false)
    {
        thread_process();
    }
    publish();
    while(ready_to_publish == true)
    {
        thread_process();
    }
    err_code = mqttsn_client_disconnect(&m_client);
    if (err_code != NRF_SUCCESS)
    {
        NRF_LOG_ERROR("DISCONNECT message could not be sent. Error: 0x%x\r\n", err_code);
    }
    break;
}

You also needs to declare the flag in top of main.c:

static uint8_t ready_to_publish = false;

And set/clear the flags in the appropriate event cases:

case MQTTSN_EVENT_REGISTERED:
    NRF_LOG_INFO("MQTT-SN event: Client registered topic.\r\n");
    regack_callback(p_event);
    ready_to_publish = true;
    break;

case MQTTSN_EVENT_PUBLISHED:
    NRF_LOG_INFO("MQTT-SN event: Client has successfully published content.\r\n");
    ready_to_publish = false;
    break;

You can now remove/comment out the entire BSP_EVENT_KEY_2 case, as this is no longer needed.

Attaching full main.c as well: devzone.nordicsemi.com/.../2022.main.c

Best regards,
Jørgen

RE: Thread Border Router networking fail

Rick — Tue, 22 Sep 2020 07:10:44 GMT

Hi Jørgen:

How are you today!

Are you have any advice? and are you have the same issue?

Pls kindly help advise how to solve it?

Best Regards,

Rick.

RE: Thread Border Router networking fail

Rick — Mon, 21 Sep 2020 01:39:40 GMT

Hi Jørgen,

I get the message_type is 1.

both are the same.

Pls kindly help advise how to solve it?

Best Regards,

Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Fri, 18 Sep 2020 14:19:56 GMT

Can you check which message type you are receiving when this problem occurs, for instance by printing it in mqttsn_packet_receiver.c:949:

NRF_LOG_ERROR("Message of unsupported type has been received: %d.\r\n", message_type);

RE: Thread Border Router networking fail

Rick — Fri, 18 Sep 2020 09:13:10 GMT

Hi Jørgen,

Thank you for your reply.

It can work.

now I try this example "Thread MQTT-SN Example".

after i compile the code than i do the step below

1.Build the example according to the instructions in Building examples.
2.Turn the MQTT-SN gateway on according to the instructions in Thread Border Router.
3.Program a development board with the MQTT-SN Subscriber application.
4.Program another development board with the MQTT-SN Publisher application.
5.Let the clients find the MQTT-SN gateway by pressing Button 2 on both boards.

one of the FTD get kick out , when i do the 5 step

and the error message show up
"0> <error> app: Message of unsupported type has been received.
0>
0> <error> app: MQTT-SN message could not be processed."

so the border router seems to be can only connect to one FTD

if i connect two devices in the same time one of FTD will be kick of

is there any reason may cause that? Or i miss some step need to be done?

Please help me,thanks

Best Regards,

Rick.

RE: Thread Border Router networking fail

Jørgen Holmefjord — Thu, 17 Sep 2020 14:45:39 GMT

Hi Rick,

1. "fdaa:bb:1::2" is he address of the NAT64 interface, which redirects the dns request to the DNS64 service. See your ifconfig output:

nat64: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 192.168.255.1  netmask 255.255.255.255  destination 192.168.255.1
        inet6 fe80::8370:ba52:f49e:93f6  prefixlen 64  scopeid 0x20<link>
        inet6 fdaa:bb:1::2  prefixlen 128  scopeid 0x0<global>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 500  (UNSPEC)
        RX packets 264  bytes 31313 (30.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 268  bytes 31457 (30.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

2. Looks like the URI also needs to include "/resources/". I checked that this code works for getting the counter-value from thethings.io cloud by pressing button 4 (make sure to input your token ID):

devzone.nordicsemi.com/.../main.c

<info> app: Received CoAP data: [{"key":"counter","value":"4","datetime":"2020-09-17T14:34:55.098Z"}]
<info> app: Received CoAP data: [{"key":"counter","value":"6","datetime":"2020-09-17T14:38:05.843Z"}]
<info> app: Received CoAP data: [{"key":"counter","value":"7","datetime":"2020-09-17T14:38:08.157Z"}]
<info> app: Received CoAP data: [{"key":"counter","value":"8","datetime":"2020-09-17T14:38:20.912Z"}]

I used another board running the original example, to post updated counter values.

Best regards,
Jørgen