Access the Internet over Thread from Android Things

RE: Access the Internet over Thread from Android Things

MSohm — Wed, 27 Feb 2019 15:58:36 GMT

I still get connect failed: ENETUNREACH (Network is unreachable) after running that command.

At this point, based on Google's comments that they are focusing Android Things on smart screens and smart speakers only, this project will adjust to use something other than Android Things. Thanks for all the help so far, but we don't need to continue this further.

RE: Access the Internet over Thread from Android Things

Jørgen Holmefjord — Thu, 14 Feb 2019 10:26:45 GMT

Can you try to add a route through the border router:

adb shell ip -6 route add default via <border-router-mesh-local-IP> dev wpan1

Note the 'via' keyword, and that the address should be that of the border router, not the website.

RE: Access the Internet over Thread from Android Things

MSohm — Thu, 31 Jan 2019 18:51:35 GMT

I tried changing the NAT64 prefix to 2001:db8:1:ffff::/96 and ran the commands below on the Android Things device, but behaviour didn't change.

adb shell su 0 ip route add table wpan1 64:ff9b::/96 dev wpan1 proto kernel scope link src fd45:5412:9874:0:667b:4209:4a08:d4b0 metric 1
adb shell su 0 ip route add table wpan1 2001:db8:1:ffff::/96 dev wpan1 proto kernel scope link src fd45:5412:9874:0:667b:4209:4a08:d4b0 metric 1

RE: Access the Internet over Thread from Android Things

Jørgen Holmefjord — Thu, 31 Jan 2019 17:01:51 GMT

It would appear that the packets are not correctly routed by the Android things device and do not leave the device over the mesh network. The network itself however appears to be establishing itself correctly in both cases.

Did you try changing the well known NAT64 prefix in border router settings from 64:ff9b::/96 to something else and setting the routing table in Android things device accordingly?

The NAT64 settings should be in /etc/tayga.conf in the border router. The packets with nat64 prefix should be routed to wpanX interface on the Android things device.

RE: Access the Internet over Thread from Android Things

MSohm — Wed, 16 Jan 2019 16:21:11 GMT

The network key is 4554ab2c58e2218ef5e4fec886100af7

RE: Access the Internet over Thread from Android Things

Jørgen Holmefjord — Wed, 16 Jan 2019 16:17:03 GMT

The traces seems to be encrypted. Can you provide decryption key, or provide new traces with key exchange included?

RE: Access the Internet over Thread from Android Things

MSohm — Wed, 16 Jan 2019 16:06:23 GMT

Here are the packet captures: https://drive.google.com/file/d/1SoW1s1qKjwlUE5mbkRILGJWxVmkCela1/view?usp=sharing

Local communication - Is from the Android Things device to a server running on the border router.

Internet communication - Is from the Android Things device to a public Internet server.

RE: Access the Internet over Thread from Android Things

Jørgen Holmefjord — Mon, 14 Jan 2019 15:44:43 GMT

Can you upload the sniffer traces?

RE: Access the Internet over Thread from Android Things

MSohm — Tue, 08 Jan 2019 18:33:09 GMT

I set up the 802.15.4 sniffer to check traffic. I see captures of both devices doing advertisements, but no other traffic when the Android Things device tries to connect to the Internet through the border router. I can see traffic captured when the Android Things devices talk to one another over Thread.

Nothing was captured before or after performing the "route add" command I posted above.

RE: Access the Internet over Thread from Android Things

Jørgen Holmefjord — Tue, 04 Dec 2018 09:30:06 GMT

Perhaps it is worth changing the well-known nat64 prefix from 64:ff9b::/96 to some other value on the border router and change route settings on the Android Things device accordingly.

Is any traffic visible on 802.15.4 sniffer?

It could also be used to verify if AT devices and border router are connecting properly.

RE: Access the Internet over Thread from Android Things

MSohm — Mon, 03 Dec 2018 14:24:38 GMT

I ran the following command on the Android Things device:

adb shell su 0 tcpdump -i wpan1 &

And then attempted to make a public connection, nothing was shown in the tcpdump.

The route command isn't available on Android Things, but running:

adb shell su 0 ip -6 route show

Gives empty results as well.

I attempted to manually add a route. The command below removes the "android.system.ErrnoException: connect failed: ENETUNREACH (Network is unreachable)", but seems to hang connecting:

adb shell su 0 ip route add table wpan1 64:ff9b::/96 dev wpan1 proto kernel scope link src fd45:5412:9874:0:a859:d2c0:52c6:3d36 metric 1

Instead, it gives: java.net.ConnectException: failed to connect to /64:ff9b::686c:6a10 (port 80) from /:: (port 59152): connect failed: ETIMEDOUT (Connection timed out)

So does it seem that Android Things is not correctly picking up the default route from the Border Router?

RE: Access the Internet over Thread from Android Things

Jørgen Holmefjord — Mon, 03 Dec 2018 13:22:21 GMT

Hi,

I got some more information from our developers and some proposition to help resolving this issue:

It is important to find out at what point frames to public IP address get lost. We can observe the 802.15.4 traffic using this sniffer software: https://github.com/NordicPlayground/nRF-802.15.4-sniffer

Also we need to observe traffic at the border router and Android Things network interfaces using tcpdump. Interfaces of interest: wpanX, nat64, wlanX or ethX.

This is the proposed setup:

I am not familiar with Android Things but I suppose the tcpdump should be launched like this:

adb shell tcpdump -i wpanX &

Then we should ping a server and see the traffic on tcpdump and 802.15.4 sniffer.

If there is no traffic visible then the first thing to check would be the routing table:

adb shell route -6

This should help us pinpoint the location of the issue and move further.

Best regards,
Jørgen

RE: Access the Internet over Thread from Android Things

MartinBL — Tue, 27 Nov 2018 08:42:58 GMT

No, problem. I'm sorry we couldn't be of more help.

RE: Access the Internet over Thread from Android Things

MSohm — Mon, 26 Nov 2018 14:37:12 GMT

Understood, thank you for looking into this one.

RE: Access the Internet over Thread from Android Things

MartinBL — Mon, 26 Nov 2018 10:48:00 GMT

Hi,

I have been in contact with the Thread team, but unfortunately they don't know why you get those exceptions and they are short on resources these days and don't have time to dig into it. I don't have the necessary HW to reproduce it myself either, so I'm afraid you are on your own on this one.

-Martin

RE: Access the Internet over Thread from Android Things

MSohm — Mon, 19 Nov 2018 14:37:52 GMT

I didn't get any further along getting the Android Things (AT) device to connect to the Internet. For now I'm considering having the app on the AT device connect to an app on the Border Router, which then relays data to the destination server. But that isn't the ideal setup.

RE: Access the Internet over Thread from Android Things

MartinBL — Mon, 19 Nov 2018 09:46:54 GMT

Hi,

Sorry for the delayed response. Bjørn is traveling at the moment, but I'll try to help you out from here.

Have you made any progress? I have asked for a comment from the Thread team. I'll keep you posted.

RE: Access the Internet over Thread from Android Things

MSohm — Mon, 12 Nov 2018 14:53:06 GMT

That example is Bluetooth, so a bit different from what I'm trying. Since the Android Things device is connected to the Thread network Border Router, it should be able to access the Internet directly.

I could create something like what is shown in that example, where there is a server (Node.js for example) listening on the Border Router that acts as a gateway application to the Internet. However, the Border Router should be able to do this on it's own as that is what it is designed to do.

RE: Access the Internet over Thread from Android Things

Bjørn Kvaale — Mon, 12 Nov 2018 14:02:29 GMT

Would it be a possibility to use this demo to use the Raspberry Pi as an internet gateway (link 1, link 2, link 3)? It should work out of the box with a Nordic Thingy:52, but could most likely easily be tweaked to work on a 52840 dk.