invalid server's version string

[succeednet]

Am getting this on both NSM5 and Rocket.

2009-12-14 10:51:16 Failed to establish SSH connection: invalid server's version string

Dave

[UBNT-Thomas]

Have not seen this before.

What firmware version?

Are you able to login to the device through SSH?

[succeednet]

Running all latest versions 5.1 beta and 3.5.

Although I think I may have found the issue. Air Control is unable to SSH to any of the devices even though I am able to ssh and get to the WEB UI. After readin the posts on the NAT issue I think I understand the reasoning for the issue.

We have several different networks running close to 1000 customers. About 20% of those customers are behind a NAT'ed network using a Netscreen. That network is running mostly Old Karlnet gear. We are looking to use that same network for the Ubiquiti's we roll out.

What is happening is the Air Control can initially scan the subnet we tell it to and see the devices but once the devices are in Air Control whether by manual input or discovery it does the following:

2009-12-15 09:07:04 Update IP address from xxx.xxx.xxx.xxx to xxx.xxx.xxx.xxx

or

2009-12-14 10:57:27 Update IP address from 10.0.0.8 to xxx.xxx.xxx.xxx

Doesn't matter which IP we use on that network it all gets automatically changed to the netscreen pulbic IP. Which it then uses to try and access either when clicking on the Launch WEB UI link or when it tries to ssh or connect to the device.

Partially easy solution would be to build a server for the Air Control and put it on the 10.0.0.x network so its behind the Netscreen with the rest of the devices. But.... would rather see the Air control correcting connect to the WLAN ip. I am unsure why its changing the ip it finds to another one as there is no reason for it to do this. Why does it not just automatically see the WLAN IP it shows and keep it there. Whats with the auto updating.

Any ideas?

[UBNT-Thomas]

Thanks for update and detailed investigation.

This issue has been addressed and the fix will be part of the next build. In the meantime please download the update following the instructions on http://www.ubnt.com/forum/showpost.php?p=51414&postcount=1

The net change is that AirControl will only recognize IP address updates where the connecting address is one of the interface addresses of the device, which is necessary to deal with dynamic IP scenarios. In cases such as port forwarding etc. where a different address was entered initially it won't be automatically changed.

See also http://www.ubnt.com/forum/showthread.php?t=16021

Does this address your problem?

[succeednet]

Not sure if there is a change since Friday but I downloaded and installed the product from that post on Friday the 11th.

[succeednet]

And out of curiosity when is the next update due for arrival?

[succeednet]

Ok just a quick update.

I went ahead and installed Air Control on a new debian server and put it directly on the private network with the Ubiquiti equipment.

Problems I see that this will not work with our network since we run a nat'ed network.

I had to turn off NAT on all the Ubiquiti Routers in order to get Air Control to run and connect to the CPE Devices. Otherwise the IP address of the CPE would update to that of the WLAN IP of the router and the ssh connection to the CPE would fail.

Technically I should be able to install the Air Control on any server in our network and be able to run it and it should connect but whatever issue it has it won't work at all with NAT. And yes I am aware of this being a known shortcoming, bug, flaw or whatever you want to classify it as. An no we will not do away with our NAT network.

Also all this trouble to get the devices and Air Control to talk to each other but I see no way to control or make changes to the devices from Air Control other than Firmware updates. I am assuming that since this is beta that the device control is eventually coming.

Other than that so far it looks Awesome.

[UBNT-Thomas]

If you took the full installer the fix for the IP address update that I already mentioned is not part of it. Please see my earlier reply.

Firmware update, reporting and status monitoring are the things you can currently do with AirControl - http://www.ubnt.com/downloads/aircontrol/aircontrol_guide.html

And yes, there is more to come in the future.

You can manage your devices through NAT as long as they are reachable through a forwarded port or tunnel. But you need the management IP update fix, otherwise it won't work. It will be part of all installers with the next build (expect it in a few days), in the meantime install the update manually.