New answers tagged openvpn
The approach I would recommend is to route all your traffic through the VPN except SSH; this provides much more protection for your privacy and significantly reduces the risk of any personal information leaking. This approach has several separate components. Torrent client rtorrent is an excellent torrent client for running in a headless environment. Run ...
I found a solution. In the OpenVPN configuration file /etc/openvpn/server.conf you can specify a script to run on up. If you take a look at the OpenVPN manual page man openvpn, you will see --up cmd. In the /etc/openvpn/server.conf configuration file, I added a line: up "/etc/openvpn/up.sh" This file is one that I created and will be executed when the ...
Looks like ssh uses upstart, but openvpn doesn't ... you might be able to force ssh to come up delayed by doing this, but it's untested (I don't want to mess up my install): update-rc.d ssh defaults 99 And as it's untested: CAVEAT EMPTOR
The problem is that squid is not a DNS proxy. So, if you want your clients to use a different DNS server (e.g. a dnsmasq instance you're running on your VPN machine), you should change their DNS settings. Also, don't forget to configure your VPN machine to use a 'clean' DNS server.
In your OpenVPN config files you are using tun interfaces, which operate at layer 3. That's fine, and probably what you want, but won't work with (ethernet) bridging because that requires layer 2 support. You can solve your problem in two ways. Either: use iptables to route traffic from your tun interface to the host of your choice, or use tap interfaces ...
I don't know about pfSense, but from the OpenVPN perspective the line of interest here is Options error: --server directive network/netmask combination is invalid This means that you've specified a VPN network address and netmask that do not combine. OpenVPN checks the network address to have zeroes where the netmask expects zeroes. E.g. 192.168.1.0 + ...
Top 50 recent answers are included