Fix "RepWifi connection not correctly reported to userspace apps" Issue #1792.HEADreplicant-6.0-0004-transitionreplicant-6.0-0004-rc6replicant-6.0-0004-rc5-transitionreplicant-6.0-0004-rc5replicant-6.0-0004-rc4replicant-6.0-0004-rc3replicant-6.0-0004-rc2replicant-6.0-0004-rc1replicant-6.0-0004replicant-6.0

When a WiFi connection is established using an external dongle via the
RepWifi app, although it's perfectly working, the framework still
presents the WiFi connection as disabled or disconnected to the
user-space apps. This misleads apps that rely on this mechanism, so
that they prevent the user from doing network-related tasks.
This patch solves the issue by modifying getActiveNetworkInfo() method
in ConnectivityService.java, adding a basic mechanism to check if the
WiFi interface is connected.
java.net.NetworkInterface.getByName() is used to look for either
"wlan0" (RepWifi) or "rndis0"(Tethering).
If any one of the two interfaces is present, getInetAddresses() is
called on it, to see if it has any IP address.
If the interface has an IP address in the "local" range
(e.g. 192.168.x.x), then it is considered to be connected. So an
instance of android.net.NetworkInfo is created, and its state is set
as "Connected".
Finally, that instance gets returned to the caller. The result should
be so that user-space apps are now able to "see" the internet
connection made via RepWifi or via reverse tethering.

Signed-off-by: Fil Bergamo <fil.bergamo@riseup.net>
Reviewed-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>

0 files changed, 0 insertions, 0 deletions