pkaplan1
I have configured an openvpn server on a Raspberry PI at home and am able to connect to it from a laptop from at least two public wifi hotspots so I'm certain that client and server are configured correctly and that my home router is port forwarding to the server correctly.
However, I need to be able to connect to the openvpn server from work when the laptop is behind a firewall to which I do not have admin access. Can someone point me to a HOWTO or provide detailed instructions to tunnel openvpn thru the firewall? I assume that it's possible using ssh since I can ssh to the openvpn server from behind the firewall, but I don't completely understand port forwarding mechanics, syntax or configuration.
Thanks
pkaplan1
I have configured an openvpn server on a raspberry pi and been able to connect to it from a laptop from two different public wifi hotspots. Therefore it seems that server.conf, client.conf and the keys are all setup correctly and my router is correctly port forwarding to the server.
However, I am trying to connect from the laptop while at work which has an enterprise firewall that I have no admin access to. I am able to ssh to the pi box so I know it's possible to tunnel through the firewall, but I am unable to figure out how to tunnel the openvpn connection. Can someone point me to a detailed HOWTO to tunnel the openvpn connection...ssh or otherwise...or provide detailed instructions. My difficulties may be in not completely understanding the syntax and configuration of port forwarding (or not!).
Thank you.
Traffic
Typically, people try HTTPS or DNS ...
pkaplan1
Please elaborate...how would I use https or dns to get openvpn to connect through the firewall?
My router has a dynamic dns address, so would I have openvpn connect to https://<server_address>?
Traffic
No .. you make your server listen on HTTPS or DNS port.
Be aware .. your work are likely to block your attempts.
DNS will simply be totally blocked and your enterprise router will provide site specific DNS.
HTTPS also likely be filtered by using deep packet inspection.
Your most likely course of action would be to ask for permission and help from your work.
Or you could run the gauntlet, probably get caught and even get fired ... :evil:
