Arduino Yun & BridgeClient - deauthenticating message

Official Hardware Classic Yún
1

Hi.

I've been working with the BridgeClient and this morning I noticed a message on my LCD screen which said "deauthenticating from" which would of been from the WLAN. I don't even know how that would of been placed there.

I have some code which once a client is connected, it's reading the data from client (via "BridgeClient client;" -> client.read()) and displays it on the LCD. Why client.read() seen that WLAN message in the first place, I have no idea why?

Anybody seen anything like this before?

2

Why client.read() seen that WLAN message in the first place,

The client.read() method returns ONE character. So, it was not any ONE client.read() that caused that message to appear on the LCD. It was something that the server sent that caused it to appear. The simple solution is to make the server not send it.

3

So this is actually setup in Server mode

I keep the client open as long as possible, which speeds things up. Only one client will ever connect to this server. I know it wasn't the other Arduino YUN which sent this, because it never logged a WLAN authenticate message.

Slimmed down version:

#include <Bridge.h>
#include <BridgeServer.h>
#include <BridgeClient.h>


BridgeServer server;
BridgeClient client;


...

void setup() {
...
  Bridge.begin();
...
}



void loop() {

  if (!client.connected()) {
    client   = server.accept();
  }
  recvWithEndMarker();

  if (newData)
  {
    //in here, print "receivedChars" to screen
    newData = false;
  }


}


void recvWithEndMarker() {
  static byte ndx = 0;
  char endMarker = '\n';
  char rc;

  while (client.available() > 0 && newData == false) {
    rc = client.read();
    lastData = millis();

    if (rc != endMarker) {
      receivedChars[ndx] = rc;
      ndx++;
      if (ndx >= numChars) {
        ndx = numChars - 1;
      }
    }
    else {
      receivedChars[ndx] = '\0'; // terminate the string
      ndx = 0;
      newData = true;
    }
  }
}
4

It's working fine with no problem, and this is the first time I've ever seen the message pop up. I'll keep my eye on it popping up again though. It also caused the bridge.py to crash on the Linux side, so I had to kill that process as that was stopping at Bridge.begin()