Data transfer protocol for seismic data

Technical Support
1

Hello!

We are facing some restrictions regarding the network protocols (can not connect to data server) and port with one of the internet providers and need to know what network protocol is RS using to send seismic data and metadata to data servers, namely:

raspberryshakedata.com

Is it using standard http/https or some proprietary protocol?

We need this information to send request to open the required ports and then properly set proxy variables in /etc/environment.

Thank you.

Best regards,
Gregor

2

Hello Gregor, and welcome back to the community!

You can find all the ports that required to be open and their relative standard TCP/UDP protocols at this page in our manual.

If, after opening the ports and adding (if necessary) exclusions to the firewall, the Shake still doesn’t connect, please download the logs from the Shake (so we can check more details on what is going on) and, if you can, SSH into the Shake itself to execute the following commands:

  • traceroute raspberryshakedata.com
  • nc -zvw5 raspberryshakedata.com 55555
  • nc -zvw5 raspberryshakedata.com 55556

Thank you!

3

Hi!

Thank you for a prompt reply. I am asking about the protocol because the provider only allows for http and https connections (updates work). Even outbound pinging is not allowed.

As expected, traceroute does not connect.

traceroute to raspberryshakedata.com (65.21.129.27), 30 hops max, 60 byte packet                                                         s
 1  192.168.211.1 (192.168.211.1)  0.879 ms  0.785 ms  0.897 ms
 2  10.80.143.1 (10.80.143.1)  0.572 ms  0.497 ms  0.457 ms
 3  10.255.1.238 (10.255.1.238)  0.834 ms  0.861 ms  0.838 ms
 4  * * *
 5  * * *
 6  * * *
 7  * * *
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

As well as Netcat.

nc: connect to raspberryshakedata.com port 55555 (tcp) timed out: Operation now in progress
nc: connect to raspberryshakedata.com port 55556 (tcp) timed out: Operation now in progress

I will retrieve log files in the upcoming week or so, but the problem is already known to us. This is a very restrictive network and we will not be able to establish a connection if the data protocol uses anything else than http/https. If it does, on the other hand, the administrator (who is very busy) only has to open the two ports (55555, 55556) in their proxy server.

If this does not work out, we will find another location.

Gregor

4

Yes, if the network is really as strict as you describe, those results do not surprise.

We use a standard socket protocol (no http/https) connection to send data from the Raspberry Shake to the server at that URL.

If the admin can, a quick port open test should be all that’s needed (don’t forget port 123 for the time service) to see if the Shake can communicate. Also, it could be worth adding the Shake IP/MAC addresses to the firewall exceptions.

Let me know if there is anything else I can help with.

1 Like