You are not logged in.
I didn't find anything which deals with this issue so I'm posting here a way to deal with this problem.
Basically, if we run openvpn client.conf , even if on server side there is the push "redirect-gateway def1 option the client will still use it's wlan0/eth0 default gateway and the OpenVPN connection will be used only for OpenVPN subnets...
To fix this you have to specify
redirect-gateway def1
on your client.conf file and the defualt gatway will be added like :
$ ip route
0.0.0.0/1 via 10.3.3.1 dev tap0
where 10.3.3.1 is the openvpn default gateway and 0.0.0.0/1 includes practically anything.
In order to not put everytime the user and password while you login, you can define the credentials like
auth-user-pass /etc/openvpn/p.txt
where p.txt is
username
password
pay attention to space.
For the DNS issue, if you need to resolve OpenVPN intranet domains, you can stick with : https://wiki.archlinux.org/index.php/OpenVPN#DNS
openresolv, or simply use a configuration like:
Public DNS , Public DNS, Private DNS , Private DNS on network-manager / Wicd
8.8.8.8 8.8.4.4 10.10.10.10 192.168.5.5
By this config, you will be able to resolve domains when you are not connected, and will be able also when you are connected in VPN. Obviously the private DNS's should be after the public ones, otherwise you will have to wait the timeout while you are not connected in VPN until the DNS can reach a server.
Tested with openvpn 2.3.2-1
Last edited by r0b0t (2013-10-19 04:26:28)
Offline