I am dealing with these networking issues at work, I can put my 2 cents on this topic...
Well, in fairly organized companies or universities (in terms of Internet security), there are NO open ports to the Internet, even though one can surf on the Internet from the company computers...
Access to HTTP and HTTPS URLs over the Internet is granted through a proxy server installed at the edge of the company network, the proxy server has access to the Internet and behaves as a connection relay.
The proxy server is then able (depending on its technology level) to :
- log every single request to the Internet (i.e. what internal IP address accessed to what Internet URL),
- block the access to spedcific URLs based on a black list of IP addresses,
- analyse on the fly the content of the HTTP data stream looking for malware activity.
These features are providing some protection against Internet threats and also Internet access logging for later analysis in case of problems.
Last point, the company computers are not usually synchronizing their real-time clock directly from Internet time servers, but from a trusted internal NTP server...
Concerning the RPi Shake network, there are common issues generated by the use of this company/university network :
1/ Connecting the RPi Shake would not allow data forwarding as TCP ports 55555 and 55556 are not standard WEB ports -and as such- not handled by the company proxy. The use of port 80 or 443 (HTTP and HTTPS) would not help much as the RPi should be able to direct the connexion to the proxy and not directly to the OSOP server (I believe the use of proxy it is not possible as of today in the shake firmware). More, depending on the proxy security features, the data stream from the RPi shake would likely be blocked by the proxy as the content is not plain WEB data and can be suspected to be generated by some spyware/malware...
Also, the RPi shake would no get NTP synchronisation from the Internet (unless one can configure RPi to use company internal trusted NTP server.
2/ On the other hand, accessing to the StationView and EQView WEB pages from the company/university network is not fully functional as the fancy GEMPA application initiates a TCP 18081 connection to get RPi stations information (the map and RPi triangles are properly displayed though).
I would say that point 1/ shouldn't be a real problem, but it needs some arrangement in the company/university to get an Internet connection at the right place (basement) with the proper TCP ports open. Usually, the company/university provide dedicated network access with specific firewall rules for instruments of the kind.
Point 2/ is a bit more of a problem to me, as the Shakers are entitled to have a look at their favorite StationView page from their desktop and expect full fonctionality... This can probably be addressed by Gempa by means of a standard port if it is considered a problem.
I believe that most of the RPi Shakes are/will be connected to home Internet routers and OSOP already designed the shake network architecture to comply with that kind of Internet access (i.e. the shake is just an Internet client, and doesn't need a static public IP address nor ingress connection from the Internet to the RPi shake). This is smart.
Another pragmatic solution to make the RPi shake run from the company/university basement (or outside shelter) is to install an ADSL line and "home" router at the right place, is does not interfere with the company/university networks and as such can be seen as a safe solution (in addition to be an adequate solution with respect to the shake architecture).
Hope this helps,
Patrick