search

gilestrolab / ethoscope

a platform from monitoring animal behaviour in real time from a raspberry pi
http://lab.gilest.ro/ethoscope/
GNU General Public License v3.0
17 stars 25 forks source link

ethoscope does not appear in the web interface #138

Closed ghost closed 2 years ago

ghost commented 3 years ago

Hello,

I am running the 20201127_ethoscope-node_pi4 image on a RPi4b and 20201126_ethoscope_000 on a RPi3b. Both devices are connected to my school's network (the node via ethernet, the scope via wifi) but the ethoscope is not getting detected by the node in the interface. Also adding the scope manually with its IP is not working. I have pinged the ethoscope from the node and vice versa with no packets lost. I am at a loss of how to troubleshoot this further. Any advice would be greatly appreciated.

Thanks, -Daniel Harvey

pepelisu commented 3 years ago

Hi Daniel, It could be that your university network is using a firewall and therefore the port 5353 (required to use avahi) is closed. Ethoscopes are discover automatically by the node using avahi/bonjour protocol. The recomended set up is to have a private network without internet access for the ethoscopes and node. Only the node is connected to internet through university network, that way:

  1. Ethoscopes are at least minimally protected to unwanted access.
  2. Ethoscopes can work without port restrictions and firewalls

Other ports needed for the sytems to work are 9000 and 8080 ( I think)

ghost commented 3 years ago

Thank you for this info. I will get in touch with my IT to see if these ports are open on our dedicated IoT network.

ggilestro commented 3 years ago

@Nocturtle you can try running the following command on the node: avahi-browse --all You should get the list of all the discoverable zeroconf devices on the network and if you see no output you'll know it's a firewall issue.

ghost commented 3 years ago

@ggilestro After first running that command I got a message that said "Failed to create client object: Daemon not running". Manually starting the daemon with 'avahi-daemon -D' seems to have fixed the issue. I can now see the ethoscope in the interface when it is plugged into ethernet, but not on wifi. Hopefully I will hear back from IT about getting those ports open. Thanks!