Create an SSH tunnel between the client machine and the OpenVPN Server, and forward from remote:1194 to localhost:1194. This is done by changing the "remote" line of the server to `remote localhost 1194`Ĥ. Change the OpenVPN client config to connect to localhost rather than the remote server address. You can do this by changing the line proto udp to proto tcp-client in the client config file.ģ. Set the OpenVPN client config file to use TCP rather than UDP. This is done by changing the line `proto udp` to `proto tcp` in the server config file (normally located at /etc/openvpn/nf).Ģ. Set the OpenVPN server config file to use TCP rather than UDP. So, on to the technical part of the procedure. You’ll need root access to the OpenVPN Server, as you have to change some of the server config files You can, of course, get a much more in-depth and accurate account of what SPI does/doesn’t do from Wikipedia, however that it’s really the purpose of this post. An SPI firewall is able to distinguish between one packet type and another, without just checking the port that is in use. This is useful if you are behind a restrictive firewall that uses SPI to block services rather than plain old port blocking. I have recently discovered that it is fairly easy to tunnel OpenVPN through SSH. Tunneling OpenVPN Through SSH Mon, Nov 12, 2012
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |