Thread border router configuration (RaspberryPi)

[daviddev]

Hello,

I have a problem witch border router (based on rpi) configuration. In rpi there is a wpan0 interface to thread and eth0 for ethernrt. I need to establish communication from computer connected to ethernet to thread nodes. For example to ping thread node from my pc and ping my pc from thread node. How to route ipv6 packets from eth0 to wpan0 ??. Is there another option. Im nod good in networking. I can ping from thread node for example a google server but ho to send packet in reverse direction?  Please help.

Best regards,
Mark

[Charlie]

Hi Mark,

Do you mean you are no able to ping your thread node from your google service? Have you go through the Wi-Fi Access Point Setup for OpenThread Border Router on your RPI.

When their connection build, you can run the CoAP examples to send and receive packages.

[daviddev]

I mean to use native IPv6 connection betwencomputer in my local network and a node in thread network.

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

I read:
Native IPv6 connection

• This option uses the built-in DHCPv6 client on the Border Router, which is able to receive prefixes from the Ethernet of the WiFi interface. If the received prefix is shorter than 63 bits, the 64-bit long subnet prefix is created and forwarded to the Thread network. In such a situation, devices create one more address based on the forwarded prefix, which allows them to be reached from the Internet (unlike in a pure NAT64 solution).

 But a cant to configure my router to advertise prefixes not equal 64 bits

Is this the reason to not be able to ping thread node ?

[Charlie]

Hi Daviddev,

Sorry for the late reply. I set up a similar environment as you did recently.

If your local router does not support IPv6, that means "Native IPv6 connection" is not valid. The thread note can not get an IP address with prefix same as your computer, they are in different local networks, so you can not ping from the network outside the Thread network.

With only NAT64 functional, the ping can only work in one direction. Just like you are not able to ping from a public server directly to your local network computer, but the network connection between a public server and your local computer still builds with the help of NAT in the router. For the thread node connected with this thread border router, you can use high-level protocols like udp/coap, tcp/MQTT to implement your application.