View Full Version : Update IP address from ???
valonino
12-01-2009, 07:52 AM
Why does Aircontrol updates IP address ? In this case correct ip is 10.29.0.67 but when I connect to a device for the first time it updates and then it stays like that.
82.114.66.249 is the address of the machine where Aircontrol is installed.
DEVICE_CONNECT_FAILURE 2009-12-01 16:45:42 John Smith 00:15:6D:D2:BD:52 Failed to establish SSH connection: java.net.ConnectException: Connection refused: connect
DEVICE_DISCOVERED 2009-12-01 16:45:41 John Smith 00:15:6D:D2:BD:52 Update IP address from 10.29.0.67 to 82.114.66.249
UNKNOWN 2009-12-01 16:45:31 John Smith 00:15:6D:D2:BD:52 Device operation failed: No communication from device after connect, please check connectivity from device to server
DEVICE_PROVISIONING_SCHEDULED 2009-12-01 16:45:12 John Smith 00:15:6D:D2:BD:52 Provisioning scheduled.
DEVICE_DISCOVERED 2009-12-01 16:44:23 John Smith 00:15:6D:D2:BD:52 New device <unkown> discovered
UBNT-Thomas
12-01-2009, 08:54 AM
This happens when data are received from the device and the connecting address is different than the address on record (DHCP lease expired, configuration change etc.). In your case, it is very strange why the remote address would be the servers address. Can you send me the HTTP access log from the logs directory (send me a private message through forum)?
gunther_01
12-04-2009, 07:32 PM
This is happening to us as well. Except that the IP that is being listed is our head end router that NATs everything.
Currently we are routed through the NAT router for monitoring (which I know isn't the best) but keeps our primary server open to do other things. Without being behind that same edge router.
It would be nice if Aircontrol queried the radio directly for the CPE's IP and did not change it. As it stands, every one of our CPE's in Aircontrol would show up with the same IP. And doesn't help with individual CPE management at all.
UBNT-Thomas
12-05-2009, 10:12 AM
The current IP handling mechanism supports direct connection and port forwarding (the device IP is the address of the forwarding machine) as well as other bidirectional tunneling mechanism such as VPN. NAT is not supported, but I will see to make the changes to support your routing scenario for the next release.
The reason why the address may change at at the time of reporting is dynamically assigned IPs - AirControl needs to use the last assigned IP.
gunther_01
12-05-2009, 06:38 PM
It seems a bit strange that Aircontrol can still get the stats from the radio but doesn't show the actual IP that the device is obviously at was all. I understand the reasoning now.
Maybe a global setting in AirControl, or a setting per sub group so all methods could be used to function depending on the users needs. It would be nice if Aircontrol didn't read the IP from the traffic, but rather the device. If I asked the software to do that.
In all fairness our set up should not work any way in a true NAT environment. But it does.. At some point I will get another NIC in that server for monitoring direct after the NAT router (maybe) We use this one server to monitor inside and outside of our network. So that becomes tricky, and may cause some loops if we can't isolate which NIC the monitors go out of.
sep78
12-10-2009, 01:29 PM
We have been able to get devices talking to the Air Control server when the server is behind a NAT Device (port forwarding for 9080)
You have to log into (ssh) the UBNT device and tell it what the IP of your NAT gateway is like this
mca-ctrl -t connect -s http://NAT.ROUTER.IP.x:9080/heartbeat
Works like a charm !
valonino
12-21-2009, 04:46 AM
Ok guys, I updated the firmware and now it works fine for me. Thank you Thomas for making the patch for our topology so the Aicontrol can operate properly even behind a Nat router.
skyhigh
01-08-2010, 10:14 PM
I have a very werid thing happen to me today with air control. My main router with lan ip address of 192.168.0.1 went down and I had to change out the router with a new one. The replacement router lan ip address was 10.10.0.1. Air control was able to see all Ubiquiti device but for some reason half of them show up in air control as 192.168.0.1 and one of them was 192.168.1.20. I'm not able to connect to them via the web portal in air control. I tried removing them and than scan for them again but they still show up as the ip range of 192.168.0.1. I have check with my customer to see if they we still connected and they said that they are connected with go internet speed. I don't understand how air control or me cannot connect to the device but the my customer are still connected. Can anyone tell me what I did wrong? Thanks,
