This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

OpenThread - Pinging Google DNS

Hi,

I am trying to connect the Thread Devices to the Internet with the following setup:

  1. OTBR from GitHub (This is not Nordic's border router) running on a RPI4 with a NCP(nRF52840-Dongle)
  2. A mobile hotspot providing the IPv6 address to the Border-router.

Here are my observations:

  1. I did get an IPv6 address on the border-router (2409:xxxx:..........)
  2. On the CLI device, on giving "ipaddr" command, I get 4 IP addresses that start with: fd11, fd11, fd80, fd11. I didn't see an IPV6 Address that start with 2xxx:xxxx...... on the CLI device
  3. CLI Device "state" is "router"
  4. I can ping the border router from the CLI device and I can ping my laptop from the border router(Connected to the same mobile hotspot)

Here are the problems I'm encountering:

  1. But, when I try to "ping 64:ff9b::0808:0808", I didn't get any response at all. Not even "Done" or "Timeout"
  2. "dns resolve ipv6.google.com" from the CLI device always results in timeout.

I read several answers on this forum and most of them suggesting that the Internet router/ISp didn't provide /62 prefix IPv6 address to the border-router and one answer suggested the "dns resolve" is broken. I am not sure what's causing the issue. Can you please help me understand if it's the problem with the ISP or if this is being caused by the router(mobile hotspot)?

If this is a problem with the ISP, does this mean the OT-BR will never work with that particular ISP? I am happy to share the full IPV6 addresses in a private DM Slight smile

Thanks for the help.

  • Hello,

    Have you tried with a router that supports IPv6? Did you do any changes in the application on the nRF?

  • Hi Edvin,

    Thanks for the response. 

    1. Nope. My current ISP for home is still on IPv4 infrastructure. If I add a router that supports IPv6 I am not sure if it helps. I am not sure on this. Do you think it makes a difference?
    2. Nope. I didn't touch anything from the SDK examples.

    Thanks

  • Hi ,

    To give you some perspective, I am trying to understand if I can use Thread to build and sell smart home products. I am completely sold on Thread but am stuck with Border Router. I am trying to find answers to the following questions:

    1. Does the Border Router need to be connected to a router that supports native IPv6? This will be the biggest bottle-neck because most routers may not support IPv6. And I also read in DevZone that most of them have flawed implementation of the stack.
    2. For the border-router to work, does it also need the ISP to support IPv6? How can it get /62 prefix?

    Thank in advance. 

  • Hello,

    I see now that you wrote that you are using a RPi4, and using this, nothing in the thread network is working, is that what you are saying?

    What exactly are you running on the RPi4? Where did you find the FW image that is running on it?

    Do you have access to an RPi3/RPi3+? Can you test using that instead?

    Best regards,

    Edvin

  • Hi Edvin,

    Thanks for your response. 

    Here's the setup:

    Observations:

    Border Router

    • Border router got an IPv6 address that starts with 2409:xxxx.......
    • I can ping www.google.com from the border router. This validates that the border router has a working internet connection.

    CLI Device

    • CLI Device(52840) is connected to the border router successfully. 
    • CLI Device(52840) can ping the border router.

    Problems:

    CLI Device:

    • No response to "ping 64:ff9b::0808:0808" command. Not even "Done" or "Timeout"
    • "dns resolve ipv6.google.com" from the CLI device always results in timeout.
    • CLI Device didn't get an IPv6 address that starts with 2xxx:xxxx..... All 4x IPv6 addresses are starting with fxxx:xxxx.....

    Unfortunately, I do not have an RPi3/3+.

    Can you help me understand the following?

    1. Under what conditions does the the CLI device not receive IPv6 address?
    2. In my understanding, please correct me if I am wrong here, a Border router needs a /62 prefix address. Only then can it assign IPv6 addresses to the devices/sensors. Is my understanding right here?
    3. If ISP doesn't provide native IPv6 to border router, can the thread devices connect to the internet through the border router? 

    Please let me know if anything is not clear. Appreciate your help Slight smile

Related