vpnc is only "ready": routing table not correct

asked 2017-02-09 22:15:16 +0300

ausgeregelt gravatar image

updated 2017-02-10 09:24:23 +0300

I have configured vpnc through the GUI but it does not seem to actually "do it". When activating the connection I get the confirmation "connected" below the VPN-Name. But when browsing to a website I still get my local IP address and not the remote IP address. Furthermore I cannot access the private servers in the remote network.

Authentication seems to work fine because if I change usernames or passwords connection wont work.

When looking at the details of the connection I can see the remote IP address stated there, the status is only "ready" though, does this have a signification?

When using vpnc in the terminal I can access the private servers and the website show me the remote IP address.

edit retag flag offensive close delete

Comments

1
  • are you able to ping the next point behind tunnel?
  • does ip route show an default gw via an vpnx interface or still via wlan/gprs interface?
cy8aer ( 2017-02-09 22:23:54 +0300 )edit

  • When doing ping I get 100% packet loss.

  • When entering ip route I get

10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.226

10.0.0.1 dev wlan0 scope link

remote dev vpn0 scope link

remote dev vpn0 scope link

remote dev vpn0 proto kernel scope link src remote

remote via 10.0.0.1 dev wlan0

where remote are remote IP-addresses and masks.

ausgeregelt ( 2017-02-09 22:34:35 +0300 )edit

When I do ip route after having connected with command line vpnc I get:

default dev tun0 scope link

10.0.0.0/24 dev wlan0 proto kernel scope link src 10.0.0.226

10.0.0.1 dev wlan0 scope link

remote dev tun0 scope link

remote via 10.0.0.1 dev wlan0 src 10.0.0.226

ausgeregelt ( 2017-02-09 22:39:04 +0300 )edit
1

Ok, the problem is the p2p-connection itself. You cannot ping your peer inside the tunnel. But the default gateway is set. When running the tunnel: Is a ping to any site in bbi (bad bad internet) like 8.8.8.8 possible? Because the routing shows that everything is put into the non functioning tunnel. Try a ps and look for the vpnc call. As in openvpn the connman job seems to interpret configurations and builds up a call with setting the parameters. Do the parameters look like the ones you use in terminal?

cy8aer ( 2017-02-09 23:22:33 +0300 )edit
1

i have the same issue when using www.ipchicken.org it shows wlan IP of router instead of VPN connection say in Kansas USA using open VPN imported file TCP also does connect but doenst do anything.

DarkTuring ( 2017-02-10 03:43:10 +0300 )edit