In our case, we used ConnectivityManager to bind to WLAN before creating our client socket.Ĭonnectivitymanager.bindProcessToNetwork(wlannetwork) ĬlientSocket. We have to bind the process to a required interface. bind did not work for us.ĬlientSocket.bind(wlanInterface.getInetAddresses().nextElement()) Ĭnnect (new InetSocketAddress( ip,port)) įinally, after all the exploration we came across ConnectivityManager which provides a way for processes to choose their communication interface. We tried making use of socket.bind() by passing WLAN interface and then also we were not able to connect with TCP server. In our case, Ethernet interface was the active interface and hence our client socket did not connect to TCP server. Wrote an App with a TCP Client Socket and tried to communicate with TCP Server running on Network 1.

Raspberry Pi’s WiFi interface was made to connect to Network 1.Īnother network called Network 2 was connected to Raspberry Pi through the Ethernet interface. We built TCP server running in Network 1. In order to check the feasibility of the project, we created a test setup. This was not possible out of the box because system would have chosen an active interface (Ethernet most of the times) and will not let us communicate over the other interface (WiFi in this case). I am running Arch Linux (on a Raspberry Pi 3) and tried to connect both the Ethernet and the Wi-Fi to the same network. Upload the above video recordings to Google Drive via Ethernet interface.Connect GoPro camera to Pi through WiFi and download the video recordings.This was important for us because we wanted to try working on a GoPro camera based project withthe below requirements. This looks different than you might think.

For example, Pi can make Ethernet interface as active and can only communicate with devices in that network. You can have both the reliability of wired Internet and the convenience of WiFi in your home at the same time. Generally, in these scenarios, Pi will make one of the interfaces as active interface and choose the same for all the network communications. In such a scenario Pi will have two IP addresses, one because of Ethernet connection while the other because of WiFi connection. This means you can connect Pi to an Ethernet and also to a WiFi network simultaneously. As most of you would know, AndroidThings supports both Ethernet interface and WLAN interface.

Wifi and ethernet same time