CODEWITHSUNDEEP
javaandroidsocketswifiiot
Starivore
Starivore

Reputation: 309

Android dealing with IoT devices with NO Internet connection

I'm trying to build a project where I must pilot an IoT device from smartphone via Wifi.

This device has the SPWF01 Wifi Module integrated, and is configured as an access point (that has no Internet access) with security type WEP. On this access point configuration we also have a TCP Socket Server that intercepts smartphone communications.

On the smartphone side, we have the part which scans and connects to our device's access point(which works, although i get the esclamation point on the wifi icon since it has no Internet access). After we've connected, we start the Client Socket which connects to the server on our IoT device(the ip address of the server socket is actually the gateway of the access point). And here is where the trouble starts, because the client socket won't start. Here is the code:

public void SocketInit(String ip, int port) throws IOException {
    InetAddress addr = InetAddress.getByName(ip);
    SocketAddress sockaddr = new InetSocketAddress(addr, port);
    nsocket = new Socket();
    nsocket.setReuseAddress(true);       
    nsocket.setTcpNoDelay(false);
    nsocket.setReceiveBufferSize(700);   //Must be less than 730byte witch is the module buffer
    nsocket.setSendBufferSize(700);
    nsocket.connect(sockaddr, 5000);     //5 second connection timeout
}

And here is the exception i get:

java.net.SocketException: socket failed: ENONET (Machine is not on the network)

And I get that error even before reaching nsocket.connect(), precisely on setReuseAddress.

Since the exception I get is ENONET, I thought that it must be because the access point has no internet access so I used the solution proposed here for testing purpose:

adb shell settings put global captive_portal_detection_enabled 0

This is a solution that can't be done programmatically without having root access, but I wanted to test if that was the problem. But although the exclamation mark on the wifi icon had disappeared, the client socket still gave me the same exception error.

Does anybody have a solution for this behaviour? Thank you in advance!

Sometimes the client socket manages to open, with a success rate of 1 out of 20 times. But when it does, i usually get another exception after a couple of messages sent:

java.net.SocketException: recvfrom failed: ECONNRESET (Connection reset by peer)

Here is the code I used to connect to the access point from the smartphone:

    WifiConfiguration wc=new WifiConfiguration();
    wc.SSID= host;
    wc.status = WifiConfiguration.Status.ENABLED;
    wc.priority = 40;
    wc.allowedKeyManagement.set(WifiConfiguration.KeyMgmt.NONE);
    wc.allowedProtocols.set(WifiConfiguration.Protocol.RSN);
    wc.allowedProtocols.set(WifiConfiguration.Protocol.WPA);
    wc.allowedAuthAlgorithms.set(WifiConfiguration.AuthAlgorithm.OPEN);
    wc.allowedAuthAlgorithms.set(WifiConfiguration.AuthAlgorithm.SHARED);
    wc.allowedGroupCiphers.clear();
    wc.allowedPairwiseCiphers.set(WifiConfiguration.PairwiseCipher.CCMP);
    wc.allowedPairwiseCiphers.set(WifiConfiguration.PairwiseCipher.TKIP);
    wc.allowedGroupCiphers.set(WifiConfiguration.GroupCipher.WEP40);
    wc.allowedGroupCiphers.set(WifiConfiguration.GroupCipher.WEP104);
    wc.wepKeys[0] = password;
    wc.wepTxKeyIndex = 0;

    int netId = mainWifi.addNetwork(wc);
    try {
        //mainWifi.setWifiEnabled(true);
        mainWifi.disconnect();
        mainWifi.enableNetwork(netId, true);
        mainWifi.reconnect();

        startConnectionCheck = true;
        System.out.println("enabled network");
    } catch (Exception e) {
        e.printStackTrace();
        System.out.println(e.getMessage());
    }

The access point's security type is WEP. That is because the Wifi module can't implement WPA.

Tests done on Marshmallow.

Upvotes: 26

Views: 2081

Answers (1)

Watachiaieto
Watachiaieto

Reputation: 422

I am not 100% certain if this issue is the same.

I had to do a project a whileback and used Java sockets.

When doing intial testing, I used the local loopback and used ports on the same computer and multiple threads. Eventually it worked well enough to test between two computers. I found it didn't work between two computers. After turning off all my firewalls and protections etc on the network and getting desperate enough to use direct connection ethernet cables, I figured out the issue.

Sockets cares which gateway you use. The solution was for me to use the gateway rather than the loopback... It is obvious looking back now...

Anyway, it is likely that your mobile gateway, wifi gateway, and local loopback are all different.

Here is an ugly code blurbe that I hope gives direction with very little inspiration...

Socket socket = null;
try {
    socket = new Socket(ip, port, InetAddress.getLoopbackAddress(), localServerPort);
}
catch (Exception e) {
}
if (socket == null) {
    try {
        socket = new Socket(ip, port, InetAddress.getLocalHost(), localServerPort);
    }
    catch (Exception e) {
    }
}
if(socket == null) {
    throw new Exception("Neither the loop back nor the host could find this sucker.");
}

Upvotes: 1

Related Questions