On Android, fails to connect to peer over offline Wifi

Setup

I’m currently running Dat v13.7.0 on two Macs (masOS 10.12.3 and 10.12.5) with node v8.1.3 on both and one Nexus 5x (Android 7.1.2) running Termux (v0.53) which I installed Node v6.11.1 into (see https://medium.freecodecamp.org/building-a-node-js-application-on-android-part-1-termux-vim-and-node-js-dfa90c28958f) and Dat v13.7.0 (the usual npm install -g dat). Lastly, I have a two routers set up, one with an Internet connection and one without.

Reproduce it

When the three devices are connected to the router that has an Internet connection, doing dat share, dat clone, dat sync back and forth between all the devices everything works as expected. When using the router without Internet and doing a dat share/dat clone between the two Macs, it takes a while to resolve but eventually everything works as expected. 👍

However while still on the offline router, when trying to dat share from the Android and then dat clone from one of the Macs or the other way around, the device trying to clone gets stuck on “Connecting to dat network…”. The funny thing is I see on the sharing device that “connections” count is increasing as expected, bet then it drops, and then comes back up, over and over without files being transferred.

[okdistribute]

Yeah maybe itd be great to have an option on the cli for which connections to use:

Default would be something like –discovery=dns,local,dht also supporting –discovery=local

[joehand]

May be related to the native modules missing on Android. Mafintosh is getting those built, so we can try again once those are working.

We should also add an --offline or --local option to only use local connections. That will make it easier to debug this as well.