Starting VPN with bind to IP prevents all external traffic!
Posted: Mon Feb 22, 2016 9:46 am
So I have a server with dual WAN and 2 public IP addresses.
I'm trying to bind OpenVPN to connect to one WAN and leave the other public. However, as soon as I start the OpenVPN service it kills all external traffic and I need to remote into another local server to stop the service and be able to log back in.
The VPN and everything connects and works fine. I just need to leave the other interface alone. I don't understand why starting the service is messing with traffic on both interfaces if it's only bound to one IP.
Server Info:
Debian GNU/Linux 7.9
openmediavault 2.1.28
Linux Kernel 3.2.0-4-amd64
I'm trying to bind OpenVPN to connect to one WAN and leave the other public. However, as soon as I start the OpenVPN service it kills all external traffic and I need to remote into another local server to stop the service and be able to log back in.
The VPN and everything connects and works fine. I just need to leave the other interface alone. I don't understand why starting the service is messing with traffic on both interfaces if it's only bound to one IP.
Server Info:
Debian GNU/Linux 7.9
openmediavault 2.1.28
Linux Kernel 3.2.0-4-amd64
Code: Select all
client
dev tun
proto udp
local XXX.XXX.XXX.XXX
remote XXX.XXX.XXX.XXX 2049
##username and password in file called pass
auth-user-pass pass
resolv-retry infinite
persist-tun
persist-key
ca ca.crt
tls-auth ta.key 1
cipher AES-256-CBC
ns-cert-type server
comp-lzo
verb 3