search

aidanjohnson / dt7816

Acoustic Array for Tracking Coordinated Flight of Foraging Bats
GNU General Public License v3.0
0 stars 0 forks source link

Connection to the Board: Inconsistent Non-success #16

Closed aidanjohnson closed 6 years ago

aidanjohnson commented 6 years ago

This issue is just to serve as a progress update. Despite trying various standardised instructions for connecting the board via Ethernet, my inconsistent non-success in establishing a reliable NFS and Internet sharing connection continues to vex me. In my last attempt the board and computer successfully connect in a local network (confirmed with ping 10.0.0.1 and 10.0.0.2). However, it fails to share the Internet connection the laptop has. In addition, the NFS connection inconsistently automatically establishes during and post- boot up.

In the meantime, I will have to copy the project files over to the board, without clock synchronisation and a reliable NFS link, and just run them locally so that testing can begin. This, though, remains to be attempted as I have enough trouble as is to establish the NFS link and I have never tried running the project program locally--I worry that the board's library structure will give us trouble (of course, this remains to be seen).

I will keep everyone updated. (Sorry that this has become such an annoying bug, with no end in sight. It seems prolonged USB-Serial connection results in the virtual console bugging out on me so I'm letting the board rest.)

aidanjohnson commented 6 years ago

UPDATE (2018-07-26 10h15): The board and laptop now seem to reliably connect to each other via local network. Thus, the NFS works. However, there seems to be an issue with accessing the internet. It appears that it is a DNS issue on the board. Fixing this will resolve this bug.

Specifically, what needs to be fixed--after the board rests for awhile as the virtual console bugging out 😖again--is the file /etc/resolv.conf on both the client (board) and host (laptop) need to be edited to have nameserver 208.67.222.222, or some other DNS besides OpenDNS (e.g. Google's 8.8.8.8). Then further debugging can occur using traceroute since the local network (with the IPs of host being 10.0.0.1 and client 10.0.0.2) is functioning. It may also be necessary to run the command ip addr add default via 10.0.0.1 dev eth0 on the client.

aidanjohnson commented 6 years ago

UPDATE (2018-07-26 11h40): The bug has been resolved. See the instructions wiki for details on the fixes.