Firewall issues?

Firewall issues are fairly uncommon with the Raspberry Shake since the requirement is only to allow out-going traffic. This is because the Shake is responsible for initiating communications with the Raspberry Shake community’s server, not the other way around, where it then pushes the data to the server. But sometimes users have super-closed firewalls that prohibit any and all communication with the outside world. So, if you do not see your station appearing on the StationView map and suspect this is because of firewall permission issues, inform your system administrator of these details:

  1. Raspberry Shake community server IP: raspberryshakedata.com
  2. NTP program requires port 123 (UDP)
  3. Meta-Data is sent to the Raspberry Shake community server through port 55556 (TCP), once at system start-up
  4. Continuous seismic data is sent to the Raspberry Shake community server through port 55555 (TCP), in one second packets over a continuously open socket with the server
  5. And, if you want to be able to use Swarm to see data from other Raspberry Shakes on the AM network, you will need access to port 16032 (TCP) to successfully communicate with the Raspberry Shake community server.