On 09/06/2015 01:29 PM, James Knott wrote:
On 09/06/2015 07:24 AM, Xen wrote:
TCP is also the option if you need to SSH tunnel, as you cannot (apparently.....) forward UDP ports.
Whenever possible, TCP should be avoided for a VPN. This is due to the flow control that's built into TCP. If you have a TCP VPN and run some TCP app over it, you may have performance issues, with 2 TCP sessions trying to control the same data stream.
How about running a TCP app over a TCP VPN over a TCP tunnel :P. However I think the TCP issues are exaggerated here because one of these links (or even two) happen between two single hosts and I think it all works out well. I do experience a lot of downtime in my internet connection. I cannot really pinpoint it to either the router, the VPN server, or the local wifi hotspot. Sometimes my internet will be down but I can SSH into the VPN server no issue. Sometimes when I close my VPN my internet is full back right again. I get the maximum download speed that my VPN can achieve though, which is a result of my ISPs upstream limit. I was more worried about the double encryption. Not that it really mattered (thus far) but the encryption takes about 20% of my VPN server's CPU time (which is a small unit). If I turn VPN encryption off, it goes down to about 25% or 20% for a full-bandwidth data stream. It's unfortunate that KDE 4 from 13.2 doesn't support no-encryption with its network-manager-applet, but a workaround was not hard to reach. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org