Closed GoogleCodeExporter closed 9 years ago
OpenVPN for Android does not install a default route, as can be seen in this
line:
2014-11-20 15:05:08 Instalované VPNService trasy: 10.5.5.110/32,
10.29.29.1/32, 93.185.97.4/32, 93.185.97.10/32, 93.185.97.18/32,
93.185.97.32/32, 93.185.97.33/32, 93.185.97.64/32, 93.185.97.102/32,
93.185.97.103/32, 93.185.97.110/32, 93.185.97.111/32, 93.185.97.112/32,
93.185.97.113/32, 93.185.97.114/32, 93.185.97.117/32
Maybe there is some bug with /32 in either your firmware or my app. Could you
test to check the option that ignores routes pushed by the server and set two
simple routes like 10.0.0.0/8 and 93.185.97.0/24 in the app?
Original comment by arne@rfc2549.org
on 20 Nov 2014 at 2:42
I did that, and another one with ignored and no custom routes. Logs attached.
Again for even simple routes ip rule contains 0.0.0.0/1 and 128.0.0.0/1 dev tun0
For no routes at all, those are not present, only standard routes on wlan0
Original comment by jkava...@gmail.com
on 20 Nov 2014 at 2:55
Attachments:
That is very strange behaviour. I fear this is a bug in the firmware. You try
another VPN app like OpenVPN Connect and see if the problem still occurs but
other than that I have no ideas.
Original comment by arne@rfc2549.org
on 20 Nov 2014 at 3:30
I tried OpenVPN Connect and OpenVPN Client Free. All the same, Internet stops
working on connecting. Connect adds one more route for my VPN IP-2 (VPN
gateway?) and Free let me switch "redirect gateway" on check box, it adds
0.0.0.0/1 and 128.0.0.0/1 to info about added routes when checked but they are
shown in ip route all the same for this and all other configurations (only
exception is your app with routes totally ignored).
Original comment by jkava...@gmail.com
on 20 Nov 2014 at 7:18
I fear that this is really a bug in your firmware then and the apps cannot
anything to fix it :(
Setting the bug to Invalid since the app is not a fault.
Original comment by arne@rfc2549.org
on 21 Nov 2014 at 9:12
:( still thank you for your time.
I will try to contact Lenovo probably, because as it seems it's not general
4.4.2 fault.
Original comment by jkava...@gmail.com
on 21 Nov 2014 at 9:24
Original issue reported on code.google.com by
jkava...@gmail.com
on 20 Nov 2014 at 2:22Attachments: