aprovpn / ics-openvpn

Automatically exported from code.google.com/p/ics-openvpn
0 stars 0 forks source link

LAN is inaccessible when OpenVPN is running on Android 4.4 #211

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start OpenVPN on the Android 4.4 device and establish a connection to a 
remote OpenVPN server (on the internet, outside of the LAN), with all internet 
traffic routed through the OpenVPN tunnel.
2. Start an FTP server on the same Android 4.4 device and try to access it from 
a machine on the same LAN, or
3. Try to access any service (Web, FTP, SSH) on the same LAN, from the Android 
4.4 device running the OpenVPN client.

What is the expected output? What do you see instead?
The expected result is being able to access the FTP server on the Android 4.4 
device, or being able to access any service on the LAN from the Android 4.4 
device. Both work on an Android 4.3 device, but not on an Android 4.4 device.

What mobile phone are you using?
2012 Nexus 7 very recently updated to Android 4.4 (the problems apply), and a 
Galaxy Nexus running Android 4.3 (no problems), on the same LAN, running 
OpenVPN 0.6.0, connected to the same remote OpenVPN server, using exactly the 
same settings.

Please provide any additional information below.
When the FTP server is running on the Android 4.4 device, WITHOUT OpenVPN 
running, nmap shows the FTP port (2121) as "open". When the FTP server is 
running WITH OpenVPN running on the Android 4.4 device, nmap shows port 2121 as 
"filtered". When the FTP server is not running, nmap shows port 2121 as 
"closed" in both cases.

The problems appeared only today, after I updated my tablet to Android 4.4 
yesterday evening.

Original issue reported on code.google.com by gcoca...@gmail.com on 26 Nov 2013 at 1:50

GoogleCodeExporter commented 9 years ago
Yeah. That is probably "work as expected". The VPNService got a major overhaul 
in 4.4 and things now work a bit different "behind the scenes".  There is 
nothing the app can do about this.

Original comment by arne@rfc2549.org on 27 Nov 2013 at 7:27