Tag Info

Hot answers tagged

5

OpenVPN over TLS Your VPN is using TCP as a transport protocol. The stunnel instance is used to encapsulate the content of the TCP stream in TLS/TCP. You get this protocol stack: [IP ]<------------------------>[IP ] [OpenVPN]<------------------------>[OpenVPN] [TLS ]<~~~~~>[TLS] [TCP ]<->[TCP ...


2

ysdx's answer is great, and describes very well how the traffic will look on the wire. Left unmentioned, however, is that traffic analysis can go a long way toward identifying applications. Let's assume that your OpenVPN connection looks just like an https connection on the wire, so an attacker cannot read the byte stream and know what kind of ...


1

In case anyone else comes across this, here is the script I ended up using. It searches /var/log/messages for log in messages, then checks if the PID is still in use by pppd. It outputs just the user name and when they logged in. #!/bin/bash # Process each log in message grep "logged in" /var/log/messages | grep pppd | while read -r line ; do #echo ...


1

This line: proto tcp means that your client will communicate with your OpenVPN server through TCP. Your traffic (UDP & TCP) is already going through your OpenVPN TCP-based tunnel.


1

The issue - sharing ports - could be solved in the opposite direction, by making Apache listen on port, say, 10443 and forwarding requests from OpenVPN there with the port-share option. (via) port 443 port-share localhost 10443


1

Original link supporting the OpenVPN 2.x client-to-client feature: https://openvpn.net/index.php/open-source/documentation/howto.html#scope Uncomment this directive to allow different clients to be able to "see" each other. By default, clients will only see the server. To force clients to only see the server, you will also need to appropriately firewall ...


1

I had the same error when trying this on my Raspberry Pi 2. First I found that starting the OpenVPN with this command returns some useful information. sudo /usr/sbin/openvpn --config /etc/openvpn/mullvad_linux.conf This made it clear I needed to update the config file with the correct path for the other ca.cert, mullvad.crt, mullvad.key, crl.pem by ...



Only top voted, non community-wiki answers of a minimum length are eligible