Can't connect trough vpn, no routes.

aprovpn / ics-openvpn

Automatically exported from code.google.com/p/ics-openvpn

0 stars 0 forks source link

Can't connect trough vpn, no routes. #235

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. Updated to v0.6.9

Found this line in log file:
Routes excluded: 0.0.0.0/1, 0.0.0.0/0, 128.0.0.0/1, 192.168.84.0/24, 
192.168.122.0/25, 192.168.122.128/25

192.168.84.0/24 is internal vpn subnet used by tun interface
192.168.122.0/24 is local network I'm using to access my remote vpn server

Tried rolling back to previous versions, problem disappeared after reverting to 
0.6.4 (no "Routes excluced" message, works fine)

Original issue reported on code.google.com by Black.Mi...@gmail.com on 17 Feb 2014 at 9:48

GoogleCodeExporter commented 9 years ago

That looks bad. Can you send me a complete log? The new version has a heurestic 
to check if networks should be included or excluded from the VPN.

Original comment by arne@rfc2549.org on 17 Feb 2014 at 10:23

GoogleCodeExporter commented 9 years ago

Log is in the attachment.
This one was generated with flag "Bypass VPN for local networks". If I disable 
that flag then local network routes are added to excluded routes list.

Original comment by Black.Mi...@gmail.com on 17 Feb 2014 at 11:22

Attachments:

ovpn.log

GoogleCodeExporter commented 9 years ago

Does this config work on other platforms? I just wondering because the clients 
gets "route-gateway 192.168.42.55" which is outside the tun network and 
therefore my clients assumes that the routes with that gw (including default 
route) are not to be routed over the VPN.

Original comment by arne@rfc2549.org on 17 Feb 2014 at 12:40

GoogleCodeExporter commented 9 years ago

Unfortunately I won't be able to check it on another platform till weekend, 
I'll send you any results as soon as I get them.
192.168.42.55 is default router for ovpn server's network. ovpn server has no 
external ip and is accessed via port forwarding, so it has two network 
interfaces one for 192.168.42.0/24 and another for 192.168.84.0/24

Original comment by Black.Mi...@gmail.com on 17 Feb 2014 at 8:20

GoogleCodeExporter commented 9 years ago

yeah. But you are pushing "route-gateway 192.168.42.55" to the client making 
that the default gateway for all route commands on the client. 

I think the client does the right thing now. The old behaviour of the client 
was to route every route to the tunnel regardless if it should be routed to the 
tunnel or not.

Original comment by arne@rfc2549.org on 17 Feb 2014 at 8:54

GoogleCodeExporter commented 9 years ago

yep, that was the cause. I've commented that push route. Can't check how it 
works via wi-fi since I'm inside my home network now, but via mobile isp it 
works fine. Problem was on the server side.

Thank you for your helping to resolve this issue 8)

Original comment by Black.Mi...@gmail.com on 17 Feb 2014 at 10:25

GoogleCodeExporter commented 9 years ago

Okay. Closing this as invalid since it was a configuration issue.

Original comment by arne@rfc2549.org on 17 Feb 2014 at 10:35

Changed state: Invalid