General Setup Joiner Issue

[C. Eldridge]

Hi everyone,

I am currently going through the general setup on the OpenThread website for setting up a border router. I am using Raspberry Pi 3/BBB and two FRDM-KW41Z. 

The issue comes up when trying to commission the joiner. After issuing "ifconfig up", then "joiner start J01NU5", it returns after some time with "Join failed [Security]". 

I've used the web GUI to form a thread network, as well as setting it up manually. Also tried commissioning using the phone app and command line. I recently switched to a BBB and I am running into the same issue.

Any help would be great. Attached is a log from running the otbr-commissioner tool when using a BBB.

[Jeffrey Bumgardner]

Hi there,

Sorry for the late response.  I can't speak to the logs, but can you successfully join using the following procedure? (which is not documented on the website yet)  Not sure if this is the manual method you tried.

https://groups.google.com/d/msg/openthread-users/2vfbmyInNoU/3rAGq6rPBQAJ

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/3ace4cbe-81b4-43d7-b98e-602ae3fa3e39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[C. Eldridge]

Hi Jeffrey,

No worries about late response. I was following the instruction on the website (here), starting with Build and Configuration, Wi-Fi Access Point Setup, Web GUI, and then getting running into the issue on the external commissioning. When the external commissioning did not work, I set up the Thread network manually and then tried using the otbr-commissioner tool (here). I have not tried using the instruction in the link you posted, but I will try them out and report back! Thanks!

[C. Eldridge]

Unfortunately, the instruction in the link you posted resulted in the same issue. After issuing the 'joiner start J01NU5" command, about 2-3 minutes pass and replies with "Join failed [Security]".

Any idea what could be causing the security issue? I'll restart the process from the start and try again.

[C. Eldridge]

Tried again from the start and ended with the same result. Below are the steps I took, let me know if you see something I did wrong.

1. Setup Thread Devices

On Ubuntu terminal:

git clone https://github.com/openthread/openthread

cd openthread

./script/bootstrap

./bootstrap

make -f examples/Makefile-kw41 TMF_PROXY=1 BORDER_ROUTER=1 COMMISSIONER=1

cd output/kw41z/bin

arm-none-eabi-objcopy -O binary ot-ncp-ftd ot-ncp-ftd.bin

Repeated similar process for joiner device with the exception of switches:

make -f examples/Makefile-kw41 JOINER=1

cd output/kw41z/bin

arm-none-eabi-objcopy -O binary ot-cli-ftd ot-cli-ftd.bin

Flashed binaries onto FRDM-KW41Z devices using J-Link Commander.

2. Setup Raspberry Pi

Started with flashing Raspian onto a micro SD card using Etcher. Before ejecting the micro SD card, opened config.txt to enable UART (for the debug/console cable). 

After starting the Pi and logging in:

sudo apt-get install vim

sudo apt-get install git

Once, both were installed:

git clone https://github.com/openthread/borderrouter

cd borderrouter

./script/bootloader

./script/setup

After completion:

ls /dev/tty*

Then plugged in the NCP device:

ls /dev/tty*

Found the device and changed socket path:

sudo vim /etc/wpantund.conf

Changed:

Config:NCP:SocketPath "/dev/ttyUSB0" 

to 

Config:NCP:SocketPath "/dev/ttyACM0"

After power cycling:

sudo systemctl status

Found the following services:

|-wpantund.service

    |--430 /usr/sbin/wpantund -o Daemon:SetDefaultRouterForAutoAddedPre

|-avahi-daemon.service

   |--392 avahi-daemon: running [raspberry pi.local]

   |--395 avahi-daemon: chroot helper

|-otbr-web.service

   |--432 /usr/sbin/otbr-web

|-otbr-agent.service

   |--574 /usr/sbin/otbr-agent -I wpan0

Verify the NCP is in the correct state:

sudo wpanctl status

The following is displayed:

wpan0 => [

        "NCP:State" => "offline"

        "Daemon:Enabled" => true

        "NCP:Version" => "OPENTHREAD/20170716-00458-gc369d72-dirty; KW41Z; Feb 13 2018 10:06:25"

        "Daemon:Version" => "0.08.00d ( /362013f; Feb 13 2018 18:14:02)"

        "Config:NCP:DriverName" => "spinel"

        "NCP:HardwareAddress" => [6C89040000000000]

]

3. Setup Thread Network

On the joiner device:

>eui64

c763050000000000

Done

On the Raspberry Pi:

sudo wpanctl setprop Network:PANID 0xDEAD

sudo wpanctl setprop Network:XPANID DEAD1111DEAD2222

sudo wpanctl setprop Network:Key 11112233445566778899DEAD1111DEAD

sudo wpanctl config-gateway -d "fd11:22::"

Using prefix "fd11:22::"

Gateway Configured.

sudo wpanctl form "OpenThreadGuide"

Forming WPAN "OpenThreadGuide" as node type "router"

Successfully formed!

sudo wpanctl commissioner -e 

Commissioner command applied.

sudo wpanctl commissioner -a J01NU5 c763050000000000

Joiner added.

On the joiner device:

> ifconfig up

Done

> joiner start J01NU5

Done

> Join failed [Security]

[Jeff Bumgardner]

Thanks for the detail on that... I'm not exactly sure why it isn't working, everything looks fine to me.

Can you try taking the two KW41Z devices and seeing if you can join them together as described here:

https://openthread.io/guides/building/commissioning

In other words, don't use the Border Router or NCP setup like you are now, just the two devices by themselves, both as FTDs, one with the commisioner role and the other with the joiner role.

Another thing to try is to run your NCP without the Border Router portion.  So what you tried above but only run wpantund on the RPi (disable the OTBR services).

These might help identify if there's some problem with your OTBR setup or perhaps some limitation of the KW41Z when used in the NCP / OTBR design.

[C. Eldridge]

Followed the link posted above, and everything worked great. 

I then reattached the NCP device, disabled the OTBR services, rebooted, and then ran through the steps I listed above but ran into the same issue on the joiner's end. 

[Jeff Bumgardner]

I was able to replicate the same issue with the KW41Z on my side... it worked fine when both devices were FTDs, but adding an NCP to the mix generated a "Join failed [Security]" error.  We'll investigate further...

On Thu, Feb 22, 2018 at 10:00 AM C. Eldridge <celd...@sanjuansw.com> wrote:

Followed the link posted above, and everything worked great. 

I then reattached the NCP device, disabled the OTBR services, rebooted, and then ran through the steps I listed above but ran into the same issue on the joiner's end. 

--

You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/ebe2eca0-f321-4af5-ae42-65fabf4eb4f2%40googlegroups.com.

[cal...@ubilogix.com]

Hello everyone,

I'm having the same issue as Eldridge, tried with the current version of the openthread stack and border router. I'm using the KW41Z as NCP, will try using a TI CC2538 instead.

[C. Eldridge]

We tried a nRF52840/KW41Z combo as well. Worked fine when both were setup as FTDs, but both setups (nRF52840=NCP/KW41Z=JOINER and nRF52840=JOINER/KW41Z=NCP) resulted in the same issues as before, Join failed [Security].

Let me know if there is anything you would like us to try on our end.

[Jonathan Hui]

Thanks for reporting this issue.

On the joiner side, can you do a clean build with logging enabled?

1) Set OPENTHREAD_CONFIG_LOG_OUTPUT to OPENTHREAD_CONFIG_LOG_OUTPUT_APP

2) Set OPENTHREAD_CONFIG_LOG_LEVEL to OT_LOG_LEVEL_INFO

If you capture and provide your console output with logging enabled, I'll take a closer look.

--

Jonathan Hui

On Tue, Feb 27, 2018 at 10:41 AM, C. Eldridge <celd...@sanjuansw.com> wrote:

We tried a nRF52840/KW41Z combo as well. Worked fine when both were setup as FTDs, but both setups (nRF52840=NCP/KW41Z=JOINER and nRF52840=JOINER/KW41Z=NCP) resulted in the same issues as before, Join failed [Security].

Let me know if there is anything you would like us to try on our end.

--

You received this message because you are subscribed to the Google Groups "openthread-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/3071d0b0-6125-4e9a-8784-57bba4c07ef6%40googlegroups.com.

[C. Eldridge]

Hi Jonathan, attached is a log from the console. Total log time was about 10 minutes. Let me know if you need anything else.

[C. Eldridge]

Tried the setup again with two nRF52840 (one as an NCP) and was able to successfully connect.

[Jeff Bumgardner]

Good to hear you were able to get it working with nRF52840.  Sorry for the problem with the KW41Z!  Hopefully we can figure out what the issue with that one is.

On Mon, Mar 5, 2018 at 9:49 AM C. Eldridge <celd...@sanjuansw.com> wrote:

Tried the setup again with two nRF52840 and was able to successfully connect.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/ee7305c4-893f-4a18-9a16-5bdc4061c00f%40googlegroups.com.

[xvh xvh]

Hi.
Do you have any estimation when the problem with KW41Z may be solved please? So I can schedule my project better.

VH

Dne středa 7. března 2018 19:36:05 UTC+1 Jeff Bumgardner napsal(a):

[Jonathan Hui]

NXP is aware of the issue and looking into it.  They have not communicated a timeline yet.  Feel free to engage NXP support directly to escalate this issue.

--

Jonathan Hui

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/c6a2086c-ce01-4262-aff0-9b3cc7e0e8b3%40googlegroups.com.

[C. Eldridge]

Just checking in to see if there is any new news?

[Jonathan Hui]

No update.  I pinged NXP again, but suspect that they are currently on holiday break.

--

Jonathan Hui

On Thu, Mar 29, 2018 at 12:59 PM, C. Eldridge <celd...@sanjuansw.com> wrote:

Just checking in to see if there is any new news?

--

You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/bfa1f9fe-885d-4293-9e42-75433ede1614%40googlegroups.com.

[xvh xvh]

I've also opened an issue and the response was:
"I have investigated this and indeed there is one person working on this, nonetheless, due to the great work the applications team is having I do not have an estimated date to provide you. 

We will need to wait until they have the chance."

Dne pondělí 2. dubna 2018 18:02:17 UTC+2 Jonathan Hui napsal(a):

No update.  I pinged NXP again, but suspect that they are currently on holiday break.

--

Jonathan Hui

On Thu, Mar 29, 2018 at 12:59 PM, C. Eldridge <celd...@sanjuansw.com> wrote:

Just checking in to see if there is any new news?

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.

[Jonathan Hui]

NXP recently submitted PR2753, which should resolve the issues described in this email thread.  Try out the latest master and let us know if this helps!

--

Jonathan Hui

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/adc2064f-69cc-4113-8da6-e13d5025eee1%40googlegroups.com.

[Carlos Caloca]

Thanks Jonathan,

I will try it today and let you know.

Cheers

On Wed, May 30, 2018 at 9:08 AM, Jonathan Hui <jon...@nestlabs.com> wrote:

NXP recently submitted PR2753, which should resolve the issues described in this email thread.  Try out the latest master and let us know if this helps!

--

Jonathan Hui

On Thu, Apr 5, 2018 at 12:37 AM xvh xvh <xvh...@gmail.com> wrote:

I've also opened an issue and the response was:
"I have investigated this and indeed there is one person working on this, nonetheless, due to the great work the applications team is having I do not have an estimated date to provide you. 

We will need to wait until they have the chance."

Dne pondělí 2. dubna 2018 18:02:17 UTC+2 Jonathan Hui napsal(a):

No update.  I pinged NXP again, but suspect that they are currently on holiday break.

--

Jonathan Hui

On Thu, Mar 29, 2018 at 12:59 PM, C. Eldridge <celd...@sanjuansw.com> wrote:

Just checking in to see if there is any new news?

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/bfa1f9fe-885d-4293-9e42-75433ede1614%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "openthread-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to openthread-users+unsubscribe@googlegroups.com.
To post to this group, send email to openthread-users@googlegroups.com.

[C. Eldridge]

It works great!

I did have to set the channel on the joiner to match the NCP channel before issuing 'joiner start J01NU5'.

Thanks for all your help!

[Jonathan Hui]

Ah, yes.  This is due to a different issue identified in the kw41z radio driver, described here.

Tom Frazel indicated that he would be submitting a PR for the fix soon.

--

Jonathan Hui

On Wed, May 30, 2018 at 9:49 AM C. Eldridge <celd...@sanjuansw.com> wrote:

It works great!

I did have to set the channel to match the NCP channel before issuing 'joiner start J01NU5'.

Thanks for all your help!

On Wednesday, May 30, 2018 at 9:08:29 AM UTC-7, Jonathan Hui wrote:

NXP recently submitted PR2753, which should resolve the issues described in this email thread.  Try out the latest master and let us know if this helps!

--

Jonathan Hui

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/03d30995-4d28-4618-88f9-847c62791542%40googlegroups.com.

[Carlos Caloca]

It's working fine now. Tried it multiple times using the kw41z as the NCP and a CC2538 as the joiner. 

[Jonathan Vervaeke]

I have the same problem, had to read through alot of topics to notice that you have to set the channel first!

Thanks for this tip, I wonder if there is news on the PR?

[Jonathan Hui]

I believe this issue was resolved by PR2757.

--

Jonathan Hui

On Tue, Oct 23, 2018 at 2:10 AM Jonathan Vervaeke <vervaeke...@gmail.com> wrote:

I have the same problem, had to read through alot of topic to notice that you have to set the channel first!

Thanks for this tip, I wonder if there is news on the PR?

On Thursday, May 31, 2018 at 4:47:36 AM UTC+2, Carlos Caloca wrote:

It's working fine now. Tried it multiple times using the kw41z as the NCP and a CC2538 as the joiner. 

--

You received this message because you are subscribed to the Google Groups "openthread-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To post to this group, send email to openthre...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/b9549d6d-8117-4e25-aaa7-64d968aa9560%40googlegroups.com.