AnsweredAssumed Answered

Unable to ping for Thread Border router using Linux + KW as Host Controlled Device with Serial TAP

Question asked by Kunal Kotecha on Jan 8, 2019
Latest reply on Jan 11, 2019 by Juan Carlos Pacheco

Hello Juan Carlos Pacheco 

 

Thank you for guiding through the steps mentioned in Thread Border Router using Linux + KW as Host Controlled Device with Serial TAP for DHCPv6-PD. We are following the steps provided by you, however, we are still facing the issue.

 

Setup:

a) Linux PC (Ubuntu 14.04)

b) FRDM KW41Z flashed with a Host controlled device application

c) FRDM KW41Z flashed with a router eligible end device (REED)

d) OpenWrt Router configured with ULA prefix.

 

FRDM version:
a) CONNECTIVITY FRAMEWORK: v5.3.6
b) IEEE 802.15.4 MAC: v5.3.6
c) NXP Thread: v1.1.1.20

d) Thread SDK: SDK_2.2.0_FRDM-KW41Z_LINUX

 

We have done bridging of eth1 and threadtap0 interface. I am not able to ping Router's IPv6 address 2001:2002:2003::1 from Linux PC, but still able to ping from REED. However, after some time ( approx. 50-60 ping response are received), ping response does not come from REED as well.

 

I have attached a log.zip file for reference, which contains:

a) steps.txt: steps used for configuring Linux machine as a border router.

b ifconfig.txt: output of "ifconfig" command.

c) IPv6Netstat.txt: output of "netstat -rn -A inet6" command.

d) routerEligileEndDevice.txt: console of router eligible end device.

e) linuxBRMachine.txt: log of ping command in Linux machine configured as a border router.

 

Regards,

Kunal

Attachments

Outcomes