You are not logged in.
I'm having this issue with OpenVPN where the routing table IS updated by the VPN server BUT doesn't route traffic to the new IPs. I'm using NetworkManager and OpenVPN CLI.
OpenVPN CLI
Sat Nov 22 23:48:10 2014 /usr/bin/ip route add 95.211.190.205/32 via 192.168.0.1
Sat Nov 22 23:48:10 2014 /usr/bin/ip route add 0.0.0.0/1 via 10.8.8.105
Sat Nov 22 23:48:10 2014 /usr/bin/ip route add 128.0.0.0/1 via 10.8.8.105
Sat Nov 22 23:48:10 2014 /usr/bin/ip route add 10.8.8.1/32 via 10.8.8.105
Checking routing table
/etc/openvpn » ip route show
default via 192.168.0.1 dev wlp3s0 proto static metric 1024
10.8.8.1 via 10.8.8.105 dev tun0 proto static metric 20
10.8.8.105 dev tun0 proto kernel scope link src 10.8.8.106
95.211.190.205 via 192.168.0.1 dev wlp3s0
128.0.0.0/1 via 10.8.8.105 dev tun0 proto static metric 20
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.105
192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.105 metric 302
The new routes have been added but if I go to www.dnsleaktest.com it will show my real IP.
I tried adding this
sudo ip route add default dev tun0
which I got from here, and it seems to have fixed the problem. www.dnsleaktest.com will now show the VPN server IP, but as the OP from the other post mentioned, I have to do this manually everytime I change server/reboot.
Is there a permanent solution to this?
Offline
You put:
Sat Nov 22 23:48:10 2014 /usr/bin/ip route add 0.0.0.0/1 via 10.8.8.105
But it's completely missing from your "ip route show" results - why?
Offline
Hah, I didn't notice that. Not sure why that's missing....
Offline
I've tried building from source and the problem persists. OpenVPN adds 0.0.0.0/1 but
ip route show
doesn't show it. Traffic seems to continue to be routed to
default via 192.168.0.1 dev wlp3s0 proto static metric 1024
instead of the new routes added.
Offline