Why are you still running 6.0.4? Rory
From: ubnt_users-boun...@wispa.org [mailto:ubnt_users-boun...@wispa.org] On Behalf Of Troy Gibson, Byhalia.net,LLC Sent: Friday, November 17, 2017 5:31 AM To: Ubiquiti Users Group <ubnt_users@wispa.org> Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices Beta 6 or 7 still does not find 6.0.4. I have had to go through my system to find missing CPE's or APs that were on 6.0.4 Downgraded to 5.6.15 for them to be found as I was unsure of the higher 6.0 firmware at the time. Troy Gibson Sent from my Verizon, Samsung Galaxy smartphone -------- Original message -------- From: RickG <rgunder...@gmail.com<mailto:rgunder...@gmail.com>> Date: 11/17/17 4:51 AM (GMT-05:00) To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>> Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices The beta works better. On Thu, Nov 16, 2017 at 1:48 PM, Phil Curnutt <pcurn...@gmail.com<mailto:pcurn...@gmail.com>> wrote: AirControl2 2.0.3 is found on Ubnt.com, Support>Downloads>AirMax>Utilities. Your have choices of Linux or Windows10 Servers and Clients and Mac Clients. I found our 900 radios on 5.6.9, but not the one on 6.0.4, but I was able to add the device manually using v 2.0.2. Phil On Thu, Nov 16, 2017 at 11:18 AM, Jan Van Kort <j.vank...@oregononline.net<mailto:j.vank...@oregononline.net>> wrote: I had an earlier version of air control installed and gave up trying to make it work over 2 years ago. Where do i go to get a current version of air control so I can try it again? I'm wandering around the ubnt.com<http://ubnt.com> website and can't find it. Does the current version have the 6.04 issue? On 08/31/2017 11:05 AM, James Craig via Ubnt_users wrote: Hi Guys, This is most likely due to this change in discovery in 6.0.4. We're adding CGN address space in 6.0.7, so moving forward, you will only be able to discover from RFC1918 and RFC6598 address. IP range scanning should still work. - Fix: Limit discovery response to queries from private subnets or multicast/broadcast On Thu, Aug 31, 2017 at 1:58 PM, Troy Gibson, Byhalia.net,LLC <t...@byhalia.net<mailto:t...@byhalia.net>> wrote: I'm on AC2.1 beta 7 and it won't find any 6.0.4 radios, XW or XM. I had some being monitored on beta 6, so those are still monitored, but show in devices not found column of discovery. TCP scan only showed prism radios too. I downgraded to 5.6.15 and it was discovered. I had to downgrade AP and CPE for it to discover the devices on AC. Now to search for the missing radios!! Troy Sent from my Verizon, Samsung Galaxy smartphone -------- Original message -------- From: CBB - Jay Fuller <par...@cyberbroadband.net<mailto:par...@cyberbroadband.net>> Date: 8/31/17 1:25 PM (GMT-05:00) To: Ubiquiti Users Group <ubnt_users@wispa.org<mailto:ubnt_users@wispa.org>> Subject: [Ubnt_users] aircontrol won't find 6.0.4 devices Been reading all about it in the ubnt forums - but anyone have any suggestions around this? Thought I'd post it here too - Haven't run aircontrol since about 18 months ago. About nine months ago I attempted to upgrade to the then current beta but it basically corrupted my database and would not even start the server service. Last night late I started over again from scratch. Ran into the 6.0.4 problem as one of my network segments (from a recent purchase) we have manually changed the ip addresses and put them all on 6.0.4 A different segment is still running 5.6.3. I was planning to move them all to 6.0.4 and also make a mass change of the username / password. Left discovering overnight, found all the devices on 5.6.3 on that particular network segment but did not find any 6.0.4 Today once googling and discovering this issue I downgraded an AP from 6.0.4 to 5.6.3 and discovery found it immediately. I don't want to do this to 300 devices. Aircontrol v.2.0.2.2874.170719.18353 is running on a public IP within our network. I tried to new feature tcp scan but no luck (probably because the server is in public ip space). I thought about temporarily changing the IP but then radios would be reporting to the wrong IP. I can manually add the device but have not found a way to do that in bulk. I don't know if it is easier for me to upgrade to something higher than 6.0.4 on all of my devices and use discovery or to manually add 300+ devices. I am hoping for another option. Bueller? Bueller? Thanks _______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org> http://lists.wispa.org/mailman/listinfo/ubnt_users _______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org<mailto:Ubnt_users@wispa.org> http://lists.wispa.org/mailman/listinfo/ubnt_users -- -RickG
_______________________________________________ Ubnt_users mailing list Ubnt_users@wispa.org http://lists.wispa.org/mailman/listinfo/ubnt_users