• State Verified Answer
  • Replies 2 replies
  • Subscribers 86 subscribers
  • Views 842 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 261291
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nordic openthread border router

nehal

Hi Nordic Community,

I follow the below link to create an openthread border router. I successfully send sensor data on things.io.

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fsdk_tz_v3.1.0%2Fthread_border_router.html

My Setup is  The border router and the phone/PC in the same local network(connect using  WIFI ), and are supported IPv6.

I want to communicate between phone/PC and node device.

is it possible to do that ping from the node FTD  to PC/phone? 

Any Suggestion!

Nehal....

Parents
  • +1

    Hi,

    From the ifconfig output you can see that in the wlan0 interface, the global IPv6 address of the border router only has a prefixlen of 64. The Thread specifications requires a /64 prefix itself in order to create a global IPv6 subnet for the Thread nodes. In order for the border router to achieve this, it needs a /62 or lower prefix address in order to further subnet the network to the Thread nodes. This is a typical problem with networking equipment/routers that they only provide /64 prefix addresses.

    You can still reach IPv4 internet from the Thread nodes and ping PCs/phones via their IPv4 translated addresses through NAT64, but it is harder to ping from the PCs/phone to the Thread nodes. See this post about pinging local IPv4 devices.

Reply
  • +1

    Hi,

    From the ifconfig output you can see that in the wlan0 interface, the global IPv6 address of the border router only has a prefixlen of 64. The Thread specifications requires a /64 prefix itself in order to create a global IPv6 subnet for the Thread nodes. In order for the border router to achieve this, it needs a /62 or lower prefix address in order to further subnet the network to the Thread nodes. This is a typical problem with networking equipment/routers that they only provide /64 prefix addresses.

    You can still reach IPv4 internet from the Thread nodes and ping PCs/phones via their IPv4 translated addresses through NAT64, but it is harder to ping from the PCs/phone to the Thread nodes. See this post about pinging local IPv4 devices.

Children
No Data
Related
Terms of service