Thread Border Router v0.11.0) ping to PC on IPv4 network

[tak-jp]

- nRF5 SDK for Thread v0.11.0

  - Thread Border Router ... RaspPi_Thread_Border_Router_Demo_v0.11.0-1.alpha.zip

  - Thread NCP Example

  - Thread CLI Example

  - Raspberry Pi connect through an Ethernet cable to my switch that provides IPv4 connectivity with the DHCP service.

I'd like to perform ping from Thread CLI Example(?) to my PC(MSWindows, 172.27.131.50), which is on IPv4 network.

Referencing the Note from this :

---

Note

    0808:0808 is in fact the Google DNS server address "8.8.8.8" in hex representation. In that way, you can reach any IPv4 cloud by replacing last 32 bits of an IPv6 address with a correctly encoded IPv4 address.

---

, I run the following command:

panid 0xabcd

ifconfig up

thread start

state

ping fd00:0064:0123:4567::ac1b:8332

 

After running the last command, I don't have any responses.

# I don't have an error message.

# Doesn't NAT64 feature work properly?

Does anyone know how to fix this?

Thank you.

[Jørgen Holmefjord]

Hi,

Have you tried pingin the PC directly from the border router, to make sure there is connection? Could you provide output of ifconfig on the BR and ipaddr of thread node?

Best regards,
Jørgen

[tak-jp]

Hi Jørgen,

I've tried pinging the PC directly from the BR, then I've found there was no connection. So that, I've tried turning off and on the BR, confirmed configuration via The LuCI configuration panel(?) or terminal application many times. During these processes, pinging the PC from the BR has come to work properly. I couldn't figure out what happened.

Anyway, your advice is very useful for me. Thank you very much.

[Jørgen Holmefjord]

Great, did you manage to ping the PC directly from the Thread node as well when connectivity between BR and PC worked properly?

[tak-jp]

Pinging the PC directly from the Thread node performed well when connectivity between BR and PC worked properly. So far, so good.