Use multiple network interfaces in an app

Question

I wrote an app that is triggering a Sony qx smartphone attachable camera over wifi. However I need to transfer the images off the phone over another local network in real time. Since the wifi card is being used for qx connection I need to be able to use ethernet over usb for transferring images off the phone. Http requests will be used to trigger the camera and send the images off the phone.

Is it possible in one android app on a phone with two network interfaces setup to specify for certain http requests to use one network interface and for others to use another network interface ? Does this need to be done through routing tables, not java?

The phone I'm using is a rooted nexus 6p.

Update:

Currently, I was able to get an Ethernet adapter working with the device (Nexus 6P). The device is connected to a local network over Ethernet. When the Wi-Fi interface is off, I can ping all devices on the local network the device is connected to over Ethernet. However, I am unable to access the web servers (Not using DNS) of any of the devices on that network (which I know they are running), i.e. Http via a browser app. The nexus 6p is connected to the network over Ethernet via a Ubiquiti Station. This seems to be a routing issue.

I can tether(usb interface) and use Wi-Fi in one app, so that leads me to believe it is possible to use Ethernet and Wi-Fi.

Update2:

After more testing, it seems to be that it is a permissions issue. Since when I ping the network the device is connected to over Ethernet without first running su in the terminal the network doesn't exist. However, when I run su then ping, I can ping the network. Thus it seems my app needs to get superuser permission before accessing Ethernet. I've granted it superuser access, but nothing has changed. I read that simply running su isn't enough from one of the comments in this post. This is because su just spawns a root shell that dies. This also explains why I couldn't access any of the web servers on this network via a browser app. Is it possible to grant my app access to the Ethernet interface when making HTTP calls like give HttpURLConnection root access, if that makes any sense (running su doesn't work)? There seems to definitely be a solution since HttpURLConnection can make calls over the USB tethering interface (Nexus 6P calls it rndis0) fine.

Update 3:

I found online here , that I can make my app a System app (thought this might grant the app eth0 access). I just moved my app to /system/app and then rebooted. However, this didn't seem to give the app anymore privileges (thus not solving the problem) , or there is something else required to make the app system than just copying it to /system/app.

Update 4:

So I was able to get Ethernet working on every app without root permissions! It seemed to be that it only works over DHCP and does not like static connections, which I was using. It works with Wi-Fi enabled, however, I cannot contact any of the devices on the Wi-Fi network when Ethernet is enabled. Is there a way around this? Does it have to do with setting two default gateways?

score 5 · Accepted Answer · answered Jun 24 '16 at 03:31

5

Since you were programming in Nexus 6P, you can try to use the new API added in ConnectivityManager to select the ethernet as your preferred network connection for your process.

Since I can't build the similar environment like yours, I am not sure if it works. It's just a suggested solution, totally not tested and verified.

ConnectivityManager connectivityManager = (ConnectivityManager) getSystemService(CONNECTIVITY_SERVICE);
Network etherNetwork = null;
for (Network network : connectivityManager.getAllNetworks()) {
    NetworkInfo networkInfo = connectivityManager.getNetworkInfo(network);
    if (networkInfo.getType() == ConnectivityManager.TYPE_ETHERNET) {
        etherNetwork = network;
    }
}
Network boundNetwork = connectivityManager.getBoundNetworkForProcess();
if (boundNetwork != null) {
    NetworkInfo boundNetworkInfo = connectivityManager.getNetworkInfo(boundNetwork);
    if (boundNetworkInfo.getType() != ConnectivityManager.TYPE_ETHERNET) {
        if (etherNetwork != null) {
            connectivityManager.bindProcessToNetwork(etherNetwork);
        }
    }
}

answered Jun 24 '16 at 03:31

alijandro

11,627
2
58
74

So I just tried this method. `connectivityManager.getAllNetworks()` seems to only return the Wi-Fi interface (length =1), when I have Ethernet and Wi-Fi on, and it returns nothing when just Ethernet is on(length=0). The device clearly has the interface up since running `ifconfig` returns `eth0` as an interface, and I can ping devices as I stated above. I even tried moving my app to a system app. However, I feel like I missed a step when making the app system since moving it to `/system/app` seemed to do absolutely do nothing. – dylan7 Jun 24 '16 at 04:27
Switch to root, modify the APK's user and group owner to root. then change the permission of APK to 644. `su`, `chown root.root /system/app/your.apk`, `chmod 644 /system/app/your.apk`. Then might have permission to access eth0 device in your code. – alijandro Jun 24 '16 at 10:26
If you think there is a problem on making system app, check logcat. You will get a permission error when app tries to run shell commands. – ekilic Jun 24 '16 at 10:36
So I can now see the Ethernet device using the code above (from Update 4 above). I can connect to wireless AP's too while Ethernet is on, but I cannot connect to the devices on the Wireless network while Ethernet is on (thus can't use the two interfaces simultaneously in one app). Does it make sense to use the above code to switch back and forth between Ethernet and Wi-Fi? There is a lot of multi-threading going on in the app different Threads need to use different network devices. – dylan7 Jun 24 '16 at 18:05

dylan7 · Answer 2 · 2016-06-24T22:28:10.287

Just to give a little more explanation on how this finally got solved.

Utilizing @alijandro's answer I was able to switch back and forth between Ethernet and Wi-Fi in one app. For some reason for the Ethernet to work it required the network gateway to supply DHCP address, not static. Then since the bindProcessToNetwork, used in @alijandro's answer is per-process, I decided to split communications with the QX camera into a Service that runs in a separate Process. The main Application (another process) would post images over Ethernet to a local network. I was successfully able to contact the devices on the local network via HTTP over Ethernet while simultaneously triggering the QX over Wi-Fi. Currently, I used Messenger to communicate using IPC to tell the QX triggering Service what methods to call.

score 0 · Answer 3 · edited May 23 '17 at 12:03

0

Most of android tv boxes can use wifi and ethernet together. In my device, i can enable ethernet from this path --- Settings -> More ... > Ethernet --- But your device wont have a menu like that as i understand. So you should make an app to do that. This application needs to access some system specific resources so your device needs to be rooted or application needs to signed with system signature. Also this topic can help you link

edited May 23 '17 at 12:03

Community

1
1

answered Jun 24 '16 at 00:54

ekilic

83
8

It seems that the Nexus 6P doesn't have access to `getSystemService("ethernet")` as it says to use in the post you linked. – dylan7 Jun 24 '16 at 03:06

score 0 · Answer 4 · answered Feb 20 '21 at 19:11

There is an easy way to do this that will answer the OP's original question about how to do this with a single application (not two separate app processes) using ConnectivityManager.requestNetwork().

The docs for ConnectivityManager.requestNetwork() allude to this:

... For example, an application could use this method to obtain a connected cellular network even if the device currently has a data connection over Ethernet. This may cause the cellular radio to consume additional power. Or, an application could inform the system that it wants a network supporting sending MMSes and have the system let it know about the currently best MMS-supporting network through the provided NetworkCallback. ...

For OP's scenario of using Wi-Fi for some traffic and ethernet for other traffic one only needs to call ConnectivityManager.requestNetwork() twice with two separate requests. One for TRANSPORT_WIFI and one for TRANSPORT_ETHERNET. The operative item here is we need a way to uniquely identify these networks. For OP's scenario, we can use transport type.

final NetworkRequest requestForWifi =
  new NetworkRequest.Builder()
  .addTransportType(NetworkCapabilities.TRANSPORT_WIFI)
  .build();

final NetworkRequest requestForEthernet =
  new NetworkRequest.Builder()
  .addTransportType(NetworkCapabilities.TRANSPORT_ETHERNET)
  .build();

final ConnectivityManager connectivityManager = (ConnectivityManager)
  context.getSystemService(Context.CONNECTIVITY_SERVICE);

final NetworkCallback networkCallbackWifi = new NetworkCallback() {
  @Override
  void onAvailable(Network network) {
      // Triggers when this network is available so you can bind to it.
  }

  @Override
  void onLost(Network network) {
      // Triggers when this network is lost.
  }
};

final NetworkCallback networkCallbackEthernet = new NetworkCallback() {
  @Override
  void onAvailable(Network network) {
      // Triggers when this network is available so you can bind to it.
  }

  @Override
  void onLost(Network network) {
      // Triggers when this network is lost.
  }
};

connectivityManager.requestNetwork(requestForWifi, networkCallbackWifi);
connectivityManager.requestNetwork(requestForEthernet, networkCallbackEthernet);

Then, once the callbacks trigger, you can then in the pertinent code (e.g. OP's code for transferring images), listen for onAvailable(Network network) and use the provided Network with Network.OpenConnection() to connect to an HTTP server using that network.

This would allow you to connect to two separate Networks from the same application.

Use multiple network interfaces in an app

4 Answers4

Linked