Corporate firewall settings to connect to remote Raspberry Pi

wjs 2018-01-29 15:24:09 UTC #1

I have a Raspberry Pi that I am trying to connect to from inside a corporate network. To be clear, the Pi is outside of the company network and successfully connects to remote3.it servers. However, the company firewall blocks my connections to the proxyX.weaved.com servers when I want to SSH into the Pi, because of the ports in use. What range of port numbers are used so that I can request that outgoing connections to those ports be allowed?

Funkanzan 2018-01-30 04:31:49 UTC #2

Generally speaking you should enable outgoing UDP on ports 5959 through 5970.

Also you may need to whitelist the proxy servers *.yoics.net, *.weaved.com, *.remot3.it.

wjs 2018-01-30 10:22:29 UTC #3

I believe that is for the Pi to connect to remot3.it servers, which isn't my problem - wish it was that easy.

When I get a URL for an SSH connection to the Pi, it looks like proxyXX.weaved.com and the port number is somewhere around 33000-34000. What I want to know is what range of port numbers are used there. Could it be 0-65535, or some fixed range? That range needs to be opened on the company firewall so that I can connect from my computer to the remote Pi.

The connection between the Pi and remot3.it works fine, the problem is the firewall blocking my computer's connection to proxyXX.weaved.com because the required ports aren't open. I need to know which range of ports to use, as the IT department will not enable outgoing connections on all ports.

mycal 2018-01-30 18:25:30 UTC #4

port proxies are on ports 30000-40000, these are the TCP endpoints. The UDP connections should be on the same port from the pi to the proxy server.

If your using P2P to connect, then the P2P client will try to use the same UDP port as the TCP port you specify for the localhost connection. But if your behind a NAT there is no telling what this port is to the real world.

It looks like your connection is being setup correctly, but your firewall is blocking the TCP outbound to the proxy server.

You could try a P2P connection, we do not know how your corporate firewall is setup, but we have seen many corporate firewall cases where p2p connections (based on UDP) work where TCP is heavily restricted. This may not be your case but you could give it a shot.

wjs 2018-01-31 10:12:06 UTC #5

Thanks for the information mycal. Could you please explain what you mean by P2P connections and P2P clients?

Funkanzan 2018-01-31 14:34:20 UTC #6

P2P is the peer-to-peer connection method which requires you to use a daemon on the client side.

A Linux script showing its use specifically for a single SSH connection (sshw.sh) is available here: