AirControl 1.0.0.6 lost connection to M5

[hatschi]

Hello,

I use Aircontrol 1.0.0.6 and 3 Nano M5 with FW 5.1. I've conneted all M5 and the green point in AirControl is on. But after a short time 2 M5 are offline (red point).

I don't get it. A fault?

this is the log of one:
Recent Events:
2010-01-14 21:28:00 No communication from device for 180 seconds.
2010-01-14 21:24:32 Provisioning complete.
2010-01-14 21:24:24 Provisioning scheduled.
2010-01-14 21:24:13 Device no longer managed
2010-01-14 21:24:03 Device operation failed: No communication from device after connect, please check connectivity from device to server
2010-01-14 21:23:53 Provisioning scheduled.
2010-01-14 21:23:43 Device no longer managed
2010-01-14 21:20:21 Failed to establish SSH connection: java.net.ConnectException: Connection timed out: connect
2010-01-14 19:59:49 Failed to establish SSH connection: java.net.NoRouteToHostException: No route to host: connect
2010-01-14 19:59:44 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect

[LHC]

Happens to me as well since upgrading to 5.1 across the board. Exact same error message and yet I can easily access each unit via browser, putty, telnet etc without losing connections..

I am wondering if I have a networking issue of some sort... I'll wait and see where this thread goes if anywhere

[UBNT-Thomas]

Which version of AirControl?

You see the issue for all units that are connected or some of them only?

[LHC]

Which version of AirControl?

You see the issue for all units that are connected or some of them only?

I'm using 1.07 and it happens for all units..

Going to setup a controlled experiment on a new independant network and see what happens.. I suspect my NAT router may be playing a role in this somehow.

[UBNT-Thomas]

If you get "No communication from device for 180 seconds." then devices may not be able to reach the AirControl server at the http port (default 9080). Make sure there is not firewall or NAT in the way. If AirControl is behind NAT, you need to enter the server external address under system settings.

[hatschi]

@UBNT-Thomas:
I have NAT in my AP (P_DB). And my client (S_DB) is connected to P_DB. Where should I enter the "server external adress under system settings"? I can't find what you mean! Thx

Problems are the same. Firewall is disabled! A other fault is, that sometimes only few Stations showing there signal!? The stations are available via browser!?

http://img706.imageshack.us/img706/966/aircontrol.png (http://img706.imageshack.us/i/aircontrol.png/)

This is the log from the red dots:
Recent Events:
2010-01-23 20:13:05 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 16:42:00 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 16:41:54 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 10:24:04 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 09:51:57 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 09:25:40 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 08:21:04 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-22 19:48:38 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-22 18:21:00 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-22 18:20:54 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect

This is the dot from the green dot:
Recent Events:
2010-01-23 20:14:01 Device communication has been restored.
2010-01-23 20:13:05 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 20:13:05 No communication from device for 300 seconds.
2010-01-23 16:43:01 Device communication has been restored.
2010-01-23 16:42:00 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 16:41:54 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 16:41:54 No communication from device for 300 seconds.
2010-01-23 10:25:01 Device communication has been restored.
2010-01-23 10:24:04 Failed to establish SSH connection: java.net.SocketException: Network is unreachable: connect
2010-01-23 10:24:04 No communication from device for 300 seconds.

The S_DB is the Nano which is always green!

Now I get a new idea. I have my notebook wireless to a WRT610n with dd-wrt and SPI firewall connected.

I've disabled the SPI and the firewall on my notebook.

I'll tell you the results.

[drwho17]

I have similar issues. I'm running PPPoE on the radios which assigns them a public IP, I also have an IP Alias on the wan port for each of these, my aircontrol box has an ethernet interface in this network 10.130.0.99/16. I have a public IP on the box as well which I use to access the interface. When AIRCONTROL is fired up it discovers several of the client radios via broadcast (but not all), I can scan the public IP ranges I assign to PPPoE and it will find radios (not all).

It appears to me that it always finds the backhaul and lower populated AP's, is there some timing value I can change which will allow it to discover them all on the management network? I want new radios to be discovered rather then me having to manually scan for them.

When I manage a unit does it specify a URL/Port on a client radio? I believe it does, how is this discovered if I haven't specified that in the Aircontrol config? The client radios heartbeat back to the Aircontrol server right?

[hatschi]

AirControl lost the connection to some Nanos (red point).
When I connect the Nano M5 in AirControl, every dot is green. Every Nano is available with Browser. That's the reason for configure 2.140 / 2.150 / 2.160 Nano M5 as Bridge.
My network (Notebook) is isolated from the neighbor.
If you have better idea, welcome!
This is my enviroment:

Edit:
http://img10.imageshack.us/img10/6091/kobinetz.png (http://img10.imageshack.us/i/kobinetz.png/)

Hello,
isn't it possible to get a static connect to every station (with NAT)? I'm searching for a way that the stations doesn't lost connection wth AirControl!

A answer will be very nice!

Thaaanks!

[UBNT-Thomas]

There are two things you need to take care of:

AirControl server needs to be able to connect to device on SSH port. If devices are behind NAT, then you need to forward ports at the NAT router. As you say you can connect to the devices this should not be the issue.

Secondly, the devices need to be able to reach the AirControl server on the HTTP port (9080 being the default). If the AirControl server is behind NAT, then you need to port forward from a host with a public IP and configure this external address under Settings. It will be given to the devices at the time you connect to report status to the AirControl server.

If you see stations dropping off after they connected successfully and you can get them back into green status by doing a disconnect/connect, then most likely the second requirement is not satisfied.

[UBNT-Thomas]

When I manage a unit does it specify a URL/Port on a client radio? I believe it does, how is this discovered if I haven't specified that in the Aircontrol config? The client radios heartbeat back to the Aircontrol server right?

If you don't specify an external address under "Settings", then AirControl will give the local interface address to the radio for reporting that connects to the SSH port. This works in most cases, but not when AirControl is behind NAT and the local address is not public.

[hatschi]

Thank you so much, now it works!

My notebook, in picture Kobi_Noti has the static WLAN-IP 192.168.3.10.
The next NanoM5 with NAT is in picture S_DB_NanoM5. So I'm going in web interface Tab Network than I've enabled Port forwarding, the entry is:

http://img7.imageshack.us/img7/1442/3001z.png (http://img7.imageshack.us/i/3001z.png/)

Than I've setup AirControl -> Settings ->
http://img218.imageshack.us/img218/9646/3001.png (http://img218.imageshack.us/i/3001.png/)

If you can see, I've enter the WLAN-IP of the S_DB_NanoM5 (192.168.2.130).
That's the external IP-Adress.

Now it works!

Special thanks!!!!!!!!!!!

By the way, is that (Port forwarding) a risk for my private LAN with IP 192.168.3.x?

EDIT:

Hmm after a standby one of the M5 are with a red dot. Now they are sometimes green and sometimes red!?
Do you have a idea?

[hatschi]

After standby of my PC one NanoM5 are Errored (with the red dot) in AirControl.

Than after a long time the NanoM5 get the green dot for connected back!?

This is the AirControl Log from a Nano (1) who is connected the whole time (green dot):
http://img98.imageshack.us/img98/2967/30011.png (http://img98.imageshack.us/i/30011.png/)

This is the AirControl Log from the Nano (2) who is red:
http://img15.imageshack.us/img15/7276/30012.png (http://img15.imageshack.us/i/30012.png/)

And this from the same Nano (2) after a long time becomes green dot:
http://img15.imageshack.us/img15/4577/30013.png (http://img15.imageshack.us/i/30013.png/)

It isn't stable.

I've changed the times (for faster tests):
http://img532.imageshack.us/img532/5193/30014.png (http://img532.imageshack.us/i/30014.png/)


There are sometimes some Nanos red and in next moment becomes green!?

But the most time they are green.
That seems like a other problem.

At the moment some becomes for a second red and than directly green again.

And a other problem is that the Nanos lost their Traffic Data. That's also a new problem since port forwarding and setting in AirControl. Normally lost the Nano the traffic with reboot but I didn't reboot any Nano.


Any idea?

Thanks!

[hatschi]

Sorry for the new post but there are only 4 images allowed in 1 post.

Edit2:
After every standby (AirControl Webserver is running the whole time and firefox is opend the whole time) my NanoM5 which is direct connected and setup in AirControl under settings and has the port forwarding (192.168.2.130) is red in AirControl. All others are green.
This is the log in AirControl for this station:
http://img503.imageshack.us/img503/5983/30015.png (http://img503.imageshack.us/i/30015.png/)

[hatschi]

The same problem, AirControl isn't solid. But I don't know exactly what should I setup.

Sometimes the Stations are green, after a PC standby (Aircontrol is running on it) the stations are red (sometimes green). Sometimes it works, sometime it doesn't work.

Can someone explain exaktly what I should setup?

My home network 192.168.3.x.
My PC 192.168.3.10 (WLAN) - AirControl 1.0.08 is running (AirControl Server Adress: 192.168.2.130
than a wrt610n (only AP-mode)
the Nano M5 directly on wrt610n over WLAN

I've setup port forwarding in the Nano M5 192.168.2.120 (NAT-mode):
PrivateIP: 192.168.2.120 | PrivatePort 9080 | TCP | PublicPort 9080

I don't know what the problem is?

Need help, pls!

Thx

[UBNT-Thomas]

If the PC running AirControl goes into standby, devices will give up reporting to AirControl after a few attempts. They are not going to resume reporting until AirControl connects next time. When your server comes out of standby, the timeout will kick in and it will attempt to connect to the units that have not been reporting. This also seems to happen according to the log, around 18:53 your box must have come online again and after that it shows that no TCP connection can be established.

What is the IP number of that station in AirControl (look at the device details panel) or click the launch web UI link). This address is where AirControl attempts to connect to.

Can you ping that same IP address from the machine where AirControl is running during the time when the SSH connect attempt fails?

[hatschi]

Thanks!

That's happen today at morning (in Log, second picture red = today morning). All stations have the right time stamp in "last connect" after standby my PC (IP 192.168.3.10) with running AirControl (AircontrolServer adress: 192.168.2.130) on that PC.
Aircontrol has set up a global ip after NAT, who is every Nano M5 available. I think it is right.

You asked:
"What is the IP number of that station in AirControl (look at the device details panel) or click the launch web UI link). This address is where AirControl attempts to connect to."

you asked:
"Can you ping that same IP address from the machine where AirControl is running during the time when the SSH connect attempt fails?"

Yes, I can ping in every direction (my internet is coming over that Nanos M5):
ping 192.168.3.10 (that ist my PC with running AirControl) works
ping 192.168.3.1 (that is LAN at Nano M5) works
ping 192.168.2.130 (that is Nano M5 WLAN) works


Ok, that is the station how is make the problems after standby. The LAN-IP of this M5 is 192.168.3.1 and the WLAN-IP is 192.168.2.130 (NAT). So I've setup in Network -> only possible in LAN, "Port forwarding ->
PrivateIP: 192.168.2.120 | PrivatePort 9080 | TCP | PublicPort 9080

But strange why is the Nano M5 (S_DB) offline after standby, that is the Nano who my PC is connected (trough a AP).

http://img268.imageshack.us/img268/2484/0902.png (http://img268.imageshack.us/i/0902.png/)

http://img251.imageshack.us/img251/9788/09021.png (http://img251.imageshack.us/i/09021.png/)

Thanks!

[hatschi]

After reconnect the M5 S_DB the traffic is shown but the last contact isn't available!?
!! The lan-traffic is changing the whole time when I use the internet, it works!!!

But why isn't the last contact available?

http://img8.imageshack.us/img8/876/09023.png (http://img8.imageshack.us/i/09023.png/)

[hatschi]

Today I've setup a WRT54GL with DD-WRT SP2 between my Nano M5 (192.168.2.130) and my home-network. So I've changed my M5 from Router to Bridge Mode and the WRT make the NAT.

In AirControl I've setup the WAN-IP from WRT (=the same range like the other M5) and in WRT-NAT I've setup port from 9080 to 9080 and the host IP from my pc who is running AirControl.

Now all stations are static green. Fort forwarding seems to work.

I can see the last contact times are the same the whole time, that means they are change after 2 minutes together!

And that wasn't before. There was every time one station who has a other Last Connect time.