nrF52 to Exosite

[amjabb]

I am trying to set up a nrF52 -> Rpi v3 -> Exosite through CoAp as in the nrF5 iot sdk. The nrF52 to rpi works as I am able to ping the nrF52 through its global link address and the second LED lights up. Has anyone recently tried doing this lately, it seems that the exosite portion of the nordic example is out of date. Below are the messages I get on the nrF52 repeated several times.

0> [APPL]: DNS query failed.

0> [APPL]: CoAP server IPv6 address not available, sending DNS query...

If anybody knows of a solution to this or another cloud interface that is feasible, I would be grateful.

[Jørgen Holmefjord]

Do you have IPv6 connection on your local network and from your ISP?

[amjabb]

Im assuming so, considering that i am on a corporate network in the united states.

[Jørgen Holmefjord]

You can test your IPv6 capabilities from a online test service like this one, or you can try pinging an IPv6-only webpage from the Rpi:

ping6 ipv6.google.com

[amjabb]

No IPv6 address detected [more info]

Good news! Your current configuration will continue to work as web sites enable IPv6.

You appear to be able to browse the IPv4 Internet only. You will not be able to reach IPv6-only sites.

Your DNS server (possibly run by your ISP) appears to have IPv6 Internet access.

This is what the online test service returns. Does this mean I dont have an IPv6 connection? If so is there a way around it? Thank you so much for your help.

[Jørgen Holmefjord]

Yes, this means you don't have IPv6 connection. There is a couple of solutions to make the devices connect to internet:

1. Setup IPv6 tunnelling. This will allow two-way communication with the devices from IPv6 internet. You can find a blog post providing some details on one alternative provider here.
2. NAT64: This solution run on the RPi and will translate the IPv6 packets from the IoT device into IPv4 packets. This allows your IPv6 enabled IoT devices to talk to IPv4 internet, but not to IPv6 internet. It is also not trivial to connect to the IoT devices from IPv4 internet, as this translation is more complex.

I would suggest going for the IPv6 tunnel solution until you get native IPv6 connection. This will make the transition simpler when you get access to IPv6 network.