Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'd like to tunnel a large amount of traffic from my local network to a server located in a datacenter, in a way that I don't have to make many changes to my local applications.

The two methods that I have come up with are 1) using a VPN (openvpn), or 2) a persistent SSH tunnel; either way I just need to change the port that my apps use and the traffic should be transparently redirected.

My questions are:

  • Which one oh these methods offers the lowest (protocol/network) overhead? My bandwidth is precious.
  • Are there other tunneling methods that I am not aware of?
share|improve this question
up vote 2 down vote accepted

I'd expect gzip in ssh and stunnel to be faster than lzo in openvpn, but..

Given that your bandwidth is so precious, I'd recommend you test your particular application and your particular data against ssh, openvpn and stunnel.

ssh, stunnel and openvpn all have support for compression. If your data is highly compressible, you may be able to trade CPU time in order to save some bandwidth, but this assumes you have sufficient CPU resources available at both ends.

On some systems, ssh makes it easier to configure strong, mutual authentication than stunnel and openvpn.

However, stunnel and openvpn might be much easier to run unattended and reliably (monitoring, reconnects, etc) which may influence your decision as well.

Finally, there's always the option of moving as much data as you can when nothing else is using your network, or make use of bandwidth throttling, if your environment allows it.

share|improve this answer

Your OS's integrated SSH is your best option. OpenVPN normally ads overheads compare to 'built-in' SSH

Make sure your firewall(s) and router give your SSH tunnel priority.

share|improve this answer

You could use SFTP as well.

share|improve this answer
SFTP is for file transfers, not generic network traffic. – becomingwisest Jan 27 '11 at 19:44
He didn't specify what the traffic was. – DanBig Jan 27 '11 at 20:30
Quote: "in a way that I don't have to make many changes to my local applications." – DutchUncle Jan 27 '11 at 22:17

You can also use stunnel for this kind of operation, the overhead is quite low

share|improve this answer
stunnel uses SSL/TLS, not SSH. Remarks about ssh protocol 1 are invalid in this context. – Alex Holst Jan 27 '11 at 19:54
thanks, changed to reflect that fact – lynxman Jan 27 '11 at 19:58

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.