wurzelsepp
Hi,
I have subsribed to a vpn service. They distribute a client config
client
dev tun3
proto udp
remote .....
cipher AES-128-CBC
resolv-retry infinite
nobind
persist-key
persist-tun
mute-replay-warnings
ca /etc/openvpn/TrustedRoot.pem
verb 3
auth-user-pass /etc/openvpn/xxx.secret
route-noexec
route-up /etc/openvpn/connected.sh
script-security 2
reneg-sec 0
remote-cert-tls server
The connection is established, but the interface and routes do not work, so I disabled routing changes just to see what happens.
In fact, the server sends a reply with identical IP addresses on both side, like this:
PUSH_REPLY,dhcp-option DNS 208.67.222.222,dhcp-option DNS 208.67.220.220,topology subnet,ping 5,ping-restart 15,explicit-exit-notify,route-gateway 10.3.113.234,redirect-gateway,ifconfig 10.3.113.234 255.255.255.0
and the interface looks like
10.3.113.234 - ptp - 10.3.113.234
Now, when I want to try out the service by doing something like
route add -host someserver.com dev tun3
or
route add -host someserver.com gw 10.3.113.234 dev tun3
packets still go out via the default gw, and when I try to ping the tunnel end, I obviously ping the local end rather than the remote one.
How can I fix the problem?
