Failed to use android App as an external thread commissioning
329 views
Skip to first unread message
Jonathan Hui
Jun 15, 2020, 2:31:32 PM6/15/20
to xinfa deng, openthread-users
Just curious - were you able to get the Android app to work with OTBR on RPi?
Note that the current Thread Group Commissioning Android app has a bug regarding multicast that affects mDNS. Android does not allow apps to send multicast messages by default - the apps must first acquire a multicast lock. Because the multicast lock is system wide, opening any other app that uses mDNS allows the Thread Group Commissioner Android app to work. For example, in our demos, we were opening the Spotify app before using the Thread Group Commissioner app.
Hope that helps.
--
Jonathan Hui
--
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 view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/0461b874-3039-4f94-81ca-2b4868fd5434o%40googlegroups.com.
xinfa deng
Jun 16, 2020, 5:54:21 AM6/16/20
to openthread-users
Hi,
I don't have raspberry pie right now. I tried opening the Spotify app before using the Thread Group Commissioner app, but it didn't help.
Now I use the OT Commissioner as the external thread commissioner. Although It is possible to ping the otbr-agent in Ubuntu, the connection cannot be established using the commissioner-cli.
Can you help me with this problem?
otbr-agent on openwrt:
> datasetActive Timestamp: 1Channel: 14Channel Mask: 07fff800Ext PAN ID: 7b49aa36012d2ffaMesh Local Prefix: fda8:3ec6:c383:ea3/64Master Key: a4e04a77d6ee6720ed709b5985275dcaNetwork Name: OpenThread-bc51PAN ID: 0xbc51PSKc: 5bd2f61dda01146b5bcb7d313ee3b633Security Policy: 0, onrcbDone> ipaddrfd11:22:0:0:7d51:c649:9f88:ec0fda8:3ec6:c383:ea3:0:ff:fe00:fc00fda8:3ec6:c383:ea3:0:ff:fe00:bc00fda8:3ec6:c383:ea3:fb2c:a44f:1fa2:5de0fe80:0:0:0:607f:6f6d:43da:c134Done> deng@ubuntu:/work/work/custom/ot-commissioner/build$ ping6 fd11:22:0:0:7d51:c649:9f88:ec0PING fd11:22:0:0:7d51:c649:9f88:ec0(fd11:22::7d51:c649:9f88:ec0) 56 data bytes64 bytes from fd11:22::7d51:c649:9f88:ec0: icmp_seq=1 ttl=64 time=1.24 ms64 bytes from fd11:22::7d51:c649:9f88:ec0: icmp_seq=2 ttl=64 time=1.26 ms64 bytes from fd11:22::7d51:c649:9f88:ec0: icmp_seq=3 ttl=64 time=1.04 ms64 bytes from fd11:22::7d51:c649:9f88:ec0: icmp_seq=4 ttl=64 time=0.825 ms^C--- fd11:22:0:0:7d51:c649:9f88:ec0 ping statistics ---4 packets transmitted, 4 received, 0% packet loss, time 3007msrtt min/avg/max/mdev = 0.825/1.094/1.269/0.178 msdeng@ubuntu:/work/work/custom/ot-commissioner/build$ deng@ubuntu:/work/work/custom/ot-commissioner/build$ cat ../src/app/etc/commissioner/non-ccm-config.json | grep PSKc "PSKc" : "5bd2f61dda01146b5bcb7d313ee3b633"deng@ubuntu:/work/work/custom/ot-commissioner/build$ sudo ./src/app/cli/commissioner-cli ../src/app/etc/commissioner/non-ccm-config.json[sudo] password for deng: ____ ______ _ _ ________ ____ / __ \/_ __/ _________ ____ ___ ____ ___ (_)_________(_)___ ____ ___ _____ / ____/ / / _/ / / / / / /_____/ ___/ __ \/ __ `__ \/ __ `__ \/ / ___/ ___/ / __ \/ __ \/ _ \/ ___/ / / / / / / / /_/ / / /_____/ /__/ /_/ / / / / / / / / / / / (__ |__ ) / /_/ / / / / __/ / / /___/ /____/ / \____/ /_/ \___/\____/_/ /_/ /_/_/ /_/ /_/_/____/____/_/\____/_/ /_/\___/_/ \____/_____/___/
> > > start fd11:22:0:0:7d51:c649:9f88:ec0 49191IO_ERROR: NET - Reading information from the socket failed[failed]> > start fd11:22:0:0:7d51:c649:9f88:ec0 49191
^CCANCELLED: the CoAPs client was disconnected[failed]> > > start fd11:22:0:0:7d51:c649:9f88:ec0 49191
在 2020年6月16日星期二 UTC+8上午2:31:32，Jonathan Hui写道：
Just curious - were you able to get the Android app to work with OTBR on RPi?Note that the current Thread Group Commissioning Android app has a bug regarding multicast that affects mDNS. Android does not allow apps to send multicast messages by default - the apps must first acquire a multicast lock. Because the multicast lock is system wide, opening any other app that uses mDNS allows the Thread Group Commissioner Android app to work. For example, in our demos, we were opening the Spotify app before using the Thread Group Commissioner app.Hope that helps.--Jonathan Hui
On Mon, Jun 15, 2020 at 4:18 AM xinfa deng <dengxin...@gmail.com> wrote:
Hi,--I have been running otbr-gent on OpenWRT and using Android phones to access OpenWRT's wifi, but the thread App cannot find the border router.here is the debug log of app.
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 openthre...@googlegroups.com.
Kangping Dong
Jun 17, 2020, 1:29:52 AM6/17/20
to openthread-users
Hi,
About OT Commissioner CLI, could you try below command to connect?
> start fd11:22:0:0:7d51:c649:9f88:ec0%eth0 49191
xinfa deng
Jun 17, 2020, 2:33:09 AM6/17/20
to openthread-users
Hi,
Still an error.
otbr-agent
> datasetActive Timestamp: 1Channel: 15Channel Mask: 07fff800Ext PAN ID: 7f6b9dc5ee4ef2d2Mesh Local Prefix: fd01:e5dd:ae8c:c555/64Master Key: 8d23c1d84545d097f4111ccb368268f3Network Name: OpenThread-8473PAN ID: 0x8473PSKc: 59a7c729fd1c5e8d1844d917d0ca9c16Security Policy: 0, onrcbDone> ipaddrfd11:22:0:0:aa4a:5a49:7d2b:4c7afd01:e5dd:ae8c:c555:0:ff:fe00:fc00fd01:e5dd:ae8c:c555:0:ff:fe00:ac00fd01:e5dd:ae8c:c555:2e53:7790:84de:d019fe80:0:0:0:6c18:97df:a8d0:cdb2Donecommissioner cli:
deng@ubuntu:/work/work/custom/ot-commissioner/build$ ifconfigens33 Link encap:Ethernet HWaddr 00:0c:29:87:f9:ea inet addr:192.168.8.177 Bcast:192.168.8.255 Mask:255.255.255.0 inet6 addr: fe80::c0bf:c04f:ad81:9dc3/64 Scope:Link inet6 addr: ddbe:48ec:56c6:10:5b90:ca3:d4b0:dd5f/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15855 errors:0 dropped:4 overruns:0 frame:0 TX packets:14991 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9855160 (9.8 MB) TX bytes:12841029 (12.8 MB)
lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:7855 errors:0 dropped:0 overruns:0 frame:0 TX packets:7855 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:754622 (754.6 KB) TX bytes:754622 (754.6 KB)
deng@ubuntu:/work/work/custom/ot-commissioner/build$ cat ../src/app/etc/commissioner/non-ccm-config.json | grep PSKc "PSKc" : "59a7c729fd1c5e8d1844d917d0ca9c16"deng@ubuntu:/work/work/custom/ot-commissioner/build$ ping6 fd11:22:0:0:aa4a:5a49:7d2b:4c7aPING fd11:22:0:0:aa4a:5a49:7d2b:4c7a(fd11:22::aa4a:5a49:7d2b:4c7a) 56 data bytes64 bytes from fd11:22::aa4a:5a49:7d2b:4c7a: icmp_seq=1 ttl=64 time=1.02 ms64 bytes from fd11:22::aa4a:5a49:7d2b:4c7a: icmp_seq=2 ttl=64 time=0.910 ms64 bytes from fd11:22::aa4a:5a49:7d2b:4c7a: icmp_seq=3 ttl=64 time=1.11 ms^C--- fd11:22:0:0:aa4a:5a49:7d2b:4c7a ping statistics ---3 packets transmitted, 3 received, 0% packet loss, time 2007msrtt min/avg/max/mdev = 0.910/1.014/1.113/0.090 msdeng@ubuntu:/work/work/custom/ot-commissioner/build$ sudo ./src/app/cli/commissioner-cli ../src/app/etc/commissioner/non-ccm-config.json ____ ______ _ _ ________ ____ / __ \/_ __/ _________ ____ ___ ____ ___ (_)_________(_)___ ____ ___ _____ / ____/ / / _/ / / / / / /_____/ ___/ __ \/ __ `__ \/ __ `__ \/ / ___/ ___/ / __ \/ __ \/ _ \/ ___/ / / / / / / / /_/ / / /_____/ /__/ /_/ / / / / / / / / / / / (__ |__ ) / /_/ / / / / __/ / / /___/ /____/ / \____/ /_/ \___/\____/_/ /_/ /_/_/ /_/ /_/_/____/____/_/\____/_/ /_/\___/_/ \____/_____/___/
> > > start fd11:22:0:0:aa4a:5a49:7d2b:4c7a%ens33 49191IO_ERROR: connect socket to peer addr=fd11:22:0:0:aa4a:5a49:7d2b:4c7a%ens33, port=49191 failed: -82[failed]> > start fd11:22:0:0:aa4a:5a49:7d2b:4c7a%eth0 49191IO_ERROR: connect socket to peer addr=fd11:22:0:0:aa4a:5a49:7d2b:4c7a%eth0, port=49191 failed: -82[failed]>
在 2020年6月17日星期三 UTC+8下午1:29:52，Kangping Dong写道：
Kangping Dong
Jun 18, 2020, 1:59:23 AM6/18/20
to xinfa deng, openthread-users
Hi xinfa,
I will look into it. get back to you later.
BRs,
Kangping
To unsubscribe from this group and stop receiving emails from it, send an email to openthread-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/70af6fb3-ad77-403b-a00a-f208e9052e64o%40googlegroups.com.
Kangping Dong
Jun 18, 2020, 2:59:40 AM6/18/20
to openthread-users
Hi xinfa,
deng@ubuntu:/work/work/custom/ot-commissioner/build$ sudo ./src/app/cli/commissioner-cli ../src/app/etc/commissioner/non-ccm-config.json
____ ______ _ _ ________ ____
/ __ \/_ __/ _________ ____ ___ ____ ___ (_)_________(_)___ ____ ___ _____ / ____/ / / _/
/ / / / / /_____/ ___/ __ \/ __ `__ \/ __ `__ \/ / ___/ ___/ / __ \/ __ \/ _ \/ ___/ / / / / / /
/ /_/ / / /_____/ /__/ /_/ / / / / / / / / / / / (__ |__ ) / /_/ / / / / __/ / / /___/ /____/ /
\____/ /_/ \___/\____/_/ /_/ /_/_/ /_/ /_/_/____/____/_/\____/_/ /_/\___/_/ \____/_____/___/
>
>
> start fd11:22:0:0:aa4a:5a49:7d2b:4c7a%ens33 49191
IO_ERROR: connect socket to peer addr=fd11:22:0:0:aa4a:5a49:7d2b:4c7a%ens33, port=49191 failed: -82
[failed]
>
> start fd11:22:0:0:aa4a:5a49:7d2b:4c7a%eth0 49191
IO_ERROR: connect socket to peer addr=fd11:22:0:0:aa4a:5a49:7d2b:4c7a%eth0, port=49191 failed: -82
[failed]
>
1. Regarding this error, I can fixed it at my local by appending "%eth0" to the local IPv6 address. My setup is to have the OTBR and commissioner on separate raspberry pi linked to the same switch.
It looks like:
pi@raspberrypi:~/ot-commissioner/build $ commissioner-cli /usr/local/etc/commissioner/non-ccm-config.json
____ ______ _ _ ________ ____
/ __ \/_ __/ _________ ____ ___ ____ ___ (_)_________(_)___ ____ ___ _____ / ____/ / / _/
/ / / / / /_____/ ___/ __ \/ __ `__ \/ __ `__ \/ / ___/ ___/ / __ \/ __ \/ _ \/ ___/ / / / / / /
/ /_/ / / /_____/ /__/ /_/ / / / / / / / / / / / (__ |__ ) / /_/ / / / / __/ / / /___/ /____/ /
\____/ /_/ \___/\____/_/ /_/ /_/_/ /_/ /_/_/____/____/_/\____/_/ /_/\___/_/ \____/_____/___/
> start fe80::8dd1:5cf6:4bfd:612 49191
IO_ERROR: connect socket to peer addr=fe80::8dd1:5cf6:4bfd:612, port=49191 failed: -68
[failed]
> start fe80::8dd1:5cf6:4bfd:612%eth0 49191
[done]
>
2. The commissioner.log you updated shows that the connection succeed, could you confirm if this log is associated to the "IO_ERROR: connect socket to peer addr=fd11:22:0:0:aa4a:5a49:7d2b:4c7a%eth0, port=49191 failed: -82" error?
3. Could you help paste the output of command "ip a" on both OTBR and commissioner host? Thanks!
BRs,
Kangping
xinfa deng
Jun 18, 2020, 4:00:13 AM6/18/20
to openthread-users
在此输入代码...Hi kangping:
for 2:
When I perform "start fd11:22::a68:3741:104e:c3b6 49191" is generated "commissioner1.log".
When I perform "start fd11:22::a68:3741:104e:c3b6%ens33 491491" or "start fd11:22::a68:3741:104e:c3b6%ens33 491491" is generated "commissioner2.log".
deng@ubuntu:/work/work/custom/ot-commissioner/build$ sudo ./src/app/cli/commissioner-cli ../src/app/etc/commissioner/non-ccm-config.json[sudo] password for deng: ____ ______ _ _ ________ ____ / __ \/_ __/ _________ ____ ___ ____ ___ (_)_________(_)___ ____ ___ _____ / ____/ / / _/ / / / / / /_____/ ___/ __ \/ __ `__ \/ __ `__ \/ / ___/ ___/ / __ \/ __ \/ _ \/ ___/ / / / / / / / /_/ / / /_____/ /__/ /_/ / / / / / / / / / / / (__ |__ ) / /_/ / / / / __/ / / /___/ /____/ / \____/ /_/ \___/\____/_/ /_/ /_/_/ /_/ /_/_/____/____/_/\____/_/ /_/\___/_/ \____/_____/___/
> > start fd11:22::5a68:3741:104e:c3b6 49191IO_ERROR: NET - Reading information from the socket failed[failed]> > > > > start fd11:22::5a68:3741:104e:c3b6%ens33 491491IO_ERROR: connect socket to peer addr=fd11:22::5a68:3741:104e:c3b6%ens33, port=32739 failed: -82[failed]> > start fd11:22::5a68:3741:104e:c3b6%eth0 491491IO_ERROR: connect socket to peer addr=fd11:22::5a68:3741:104e:c3b6%eth0, port=32739 failed: -82[failed]> for 3:
on the otbr host:
root@GL-B1300:~# ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: miireg: <> mtu 0 qdisc noop state DOWN group default qlen 1 link/generic 3: gre0@NONE: <NOARP> mtu 1476 qdisc noop state DOWN group default qlen 1 link/gre 0.0.0.0 brd 0.0.0.04: gretap0@NONE: <BROADCAST,MULTICAST> mtu 1462 qdisc noop state DOWN group default qlen 1000 link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff5: bond0: <BROADCAST,MULTICAST,MASTER> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether a6:23:2e:1e:d5:9e brd ff:ff:ff:ff:ff:ff6: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000 link/ether ae:8e:e2:02:65:03 brd ff:ff:ff:ff:ff:ff7: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br-lan state UP group default qlen 1000 link/ether 5a:ea:55:b3:58:a9 brd ff:ff:ff:ff:ff:ff8: teql0: <NOARP> mtu 1500 qdisc noop state DOWN group default qlen 100 link/void 9: wifi0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 2699 link/ieee802.11 8c:88:2b:20:3c:0a brd ff:ff:ff:ff:ff:ff10: wifi1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 2699 link/ieee802.11 8c:88:2b:20:3c:09 brd ff:ff:ff:ff:ff:ff12: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 5a:ea:55:b3:58:a9 brd ff:ff:ff:ff:ff:ff inet 192.168.8.1/24 brd 192.168.8.255 scope global br-lan valid_lft forever preferred_lft forever inet6 ddbe:48ec:56c6:10::1/60 scope global noprefixroute valid_lft forever preferred_lft forever inet6 fe80::58ea:55ff:feb3:58a9/64 scope link valid_lft forever preferred_lft forever13: tayga-nat64: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 500 link/none 14: ath0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UNKNOWN group default link/ether 8c:88:2b:20:3c:0a brd ff:ff:ff:ff:ff:ff inet6 fe80::8e88:2bff:fe20:3c0a/64 scope link valid_lft forever preferred_lft forever15: ath1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br-lan state UNKNOWN group default link/ether 8c:88:2b:20:3c:09 brd ff:ff:ff:ff:ff:ff inet6 fe80::8e88:2bff:fe20:3c09/64 scope link valid_lft forever preferred_lft forever16: wpan0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 500 link/void inet6 fd11:22::5a68:3741:104e:c3b6/64 scope global valid_lft forever preferred_lft forever inet6 fd2f:feb4:2ea7:358:0:ff:fe00:fc00/64 scope global valid_lft forever preferred_lft forever inet6 fd2f:feb4:2ea7:358:0:ff:fe00:c800/64 scope global valid_lft forever preferred_lft forever inet6 fd2f:feb4:2ea7:358:fafb:25c1:805a:ceb4/64 scope global valid_lft forever preferred_lft forever inet6 fe80::4c8c:4848:935a:43d5/64 scope link valid_lft forever preferred_lft foreverdeng@ubuntu:/work/work/custom/ot-commissioner/build$ ip a1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:0c:29:87:f9:ea brd ff:ff:ff:ff:ff:ff inet 192.168.8.177/24 brd 192.168.8.255 scope global dynamic ens33 valid_lft 42691sec preferred_lft 42691sec inet6 ddbe:48ec:56c6:10::17a/128 scope global valid_lft forever preferred_lft forever inet6 ddbe:48ec:56c6:10:5b90:ca3:d4b0:dd5f/64 scope global noprefixroute dynamic valid_lft 42760sec preferred_lft 42760sec inet6 fe80::c0bf:c04f:ad81:9dc3/64 scope link valid_lft forever preferred_lft forever
Please let me know if you need any more information.I'll always be online.
Thanks,
Xinfa Deng
在 2020年6月18日星期四 UTC+8下午2:59:40，Kangping Dong写道：
xinfa deng
Jun 18, 2020, 4:19:07 AM6/18/20
to openthread-users
Hi kangping:
I'm sorry, the port is set wrong in the "start fd11:22: : a68:3741:104 e: c3b6 % ens33 491491" command.
Here is the correct log information:
deng@ubuntu:/work/work/custom/ot-commissioner/build$ sudo ./src/app/cli/commissioner-cli ../src/app/etc/commissioner/non-ccm-config.json ____ ______ _ _ ________ ____ / __ \/_ __/ _________ ____ ___ ____ ___ (_)_________(_)___ ____ ___ _____ / ____/ / / _/ / / / / / /_____/ ___/ __ \/ __ `__ \/ __ `__ \/ / ___/ ___/ / __ \/ __ \/ _ \/ ___/ / / / / / / / /_/ / / /_____/ /__/ /_/ / / / / / / / / / / / (__ |__ ) / /_/ / / / / __/ / / /___/ /____/ / \____/ /_/ \___/\____/_/ /_/ /_/_/ /_/ /_/_/____/____/_/\____/_/ /_/\___/_/ \____/_____/___/
> start fd11:22::5a68:3741:104e:c3b6%ens33 49191IO_ERROR: connect socket to peer addr=fd11:22::5a68:3741:104e:c3b6%ens33, port=49191 failed: -82[failed]> start fd11:22::5a68:3741:104e:c3b6%eth0 49191IO_ERROR: connect socket to peer addr=fd11:22::5a68:3741:104e:c3b6%eth0, port=49191 failed: -82[failed]> exit[done]
在 2020年6月18日星期四 UTC+8下午2:59:40，Kangping Dong写道：
Hi xinfa,
Kangping Dong
Jun 18, 2020, 5:11:23 AM6/18/20
to xinfa deng, openthread-users
Hi xinfa,
Could you please try the IP addresses (both IPv4 and IPv6) listed in below netif?
12: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 5a:ea:55:b3:58:a9 brd ff:ff:ff:ff:ff:ff
inet 192.168.8.1/24 brd 192.168.8.255 scope global br-lan
valid_lft forever preferred_lft forever
inet6 ddbe:48ec:56c6:10::1/60 scope global noprefixroute
valid_lft forever preferred_lft forever
inet6 fe80::58ea:55ff:feb3:58a9/64 scope link
valid_lft forever preferred_lft forever
Note: you only need to append "%ens33" for local Ipv6 address.
Please let me know if any of the addresses can work.
BRs,
Kangping
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/6abe7e5c-3f18-46e9-8993-e7fcd5ffff9co%40googlegroups.com.
xinfa deng
Jun 18, 2020, 7:36:32 AM6/18/20
to openthread-users
Hi KangPing:
It works!!!
Thank you very much for your help.
deng@ubuntu:/work/work/custom/ot-commissioner/build$ sudo ./src/app/cli/commissioner-cli ../src/app/etc/commissioner/non-ccm-config.json ____ ______ _ _ ________ ____ / __ \/_ __/ _________ ____ ___ ____ ___ (_)_________(_)___ ____ ___ _____ / ____/ / / _/ / / / / / /_____/ ___/ __ \/ __ `__ \/ __ `__ \/ / ___/ ___/ / __ \/ __ \/ _ \/ ___/ / / / / / / / /_/ / / /_____/ /__/ /_/ / / / / / / / / / / / (__ |__ ) / /_/ / / / / __/ / / /___/ /____/ / \____/ /_/ \___/\____/_/ /_/ /_/_/ /_/ /_/_/____/____/_/\____/_/ /_/\___/_/ \____/_____/___/
> > > > start ddbe:48ec:56c6:10::1 49191[done]
But now I have another problem, I operate according to official instructions :https://openthread.google.cn/guides/border-router/external-commissioning?comm=ot-commissioner.
the joiner device show "Join failed [Security]",
I will continue to look for the cause of the error, but if you know the cause, it will help me quickly complete the verification of this function.
thank you again.
in ot commisioner:
> joiner enableall meshcop J01NU5[done]> on the joiner device:
> ifconfig upDone> joiner start J01NU5 Done> Join failed [Security]regards,
Xinfa
在 2020年6月18日星期四 UTC+8下午5:11:23，Kangping Dong写道：
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/6abe7e5c-3f18-46e9-8993-e7fcd5ffff9co%40googlegroups.com.
Kangping Dong
Jun 18, 2020, 10:45:07 PM6/18/20
to xinfa deng, openthread-users
Hi xinfa,
Could you share the commissioner.log? Thanks!
BRs,
kangping
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/314a1774-c0c9-4c8c-b5a5-4b9e33b0f151o%40googlegroups.com.
xinfa deng
Jun 19, 2020, 12:28:33 AM6/19/20
to openthread-users
Hi Kangping:
在 2020年6月19日星期五 UTC+8上午10:45:07，Kangping Dong写道：
Here is the commissioner.log and the otbr-agent.log.
regards,
Xinfa
在 2020年6月19日星期五 UTC+8上午10:45:07，Kangping Dong写道：
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/314a1774-c0c9-4c8c-b5a5-4b9e33b0f151o%40googlegroups.com.
Kangping Dong
Jun 19, 2020, 6:32:55 AM6/19/20
to xinfa deng, openthread-users
Hi Xinfa,
otbr-agent[7739]: [INFO]-MESH-CP-: JoinerRouter::HandleUdpReceive
otbr-agent[7739]: [INFO]-MESH-CP-: Sent relay rx
otbr-agent[7739]: [INFO]-MESH-CP-: Sent to commissioner
otbr-agent[7739]: [INFO]-MESH-CP-: Sent to commissioner on c/rx
otbr-agent[7739]: [NOTE]-MESH-CP-: CoapSecure Transmit: NoBufs
This leads me to the root cause that the DTLS messages exceed the configured maximum DTLS application data length. I created this PR https://github.com/openthread/openthread/pull/5125 for this issue. I tested at my local raspberry pi and it works now.
You can pull this PR to your local and have a try (please note that this affects only the OTBR, so you should pull this PR into ot-br-posix/third_party/openthread/repo).
cd ot-br-posix/third_party/openthread/repo
git fetch origin pull/5125/head:increase-dtls-length
git checkout increase-dtls-length
cd ../../../
# Rebuild OTBR
./script/setup
BRs,
Kangping
To view this discussion on the web visit https://groups.google.com/d/msgid/openthread-users/ce66ebeb-3b97-40b8-a892-5f1c923e0d65o%40googlegroups.com.
JM
Jul 8, 2020, 3:04:27 AM7/8/20
to openthread-users
Dear all
I have a problem with external commission.
when I use nordic ncp device to do external commission with android App is work well.
but when I use ot-commissioner to replace android APP,I get a error.
Do anyone know why is the error happened?
Kangping Dong
Jul 8, 2020, 4:03:23 AM7/8/20
to openthread-users
Hi,
OT Commissioner always sends a MGMT_ACTIVE_GET to the leader to fetch the active dataset of the Thread Network when got connected.
The error message indicates that the response of MGMT_ACTIVE_GET request doesn't include expected TLV "Active Timestamp".
Could you help
1. upload the commissioner log file which is the commissioner.log file in the directory you launched the command?
2. If available, also share the log on the leader?
Reply all
Reply to author
Forward
0 new messages