My understanding is it is a code change in 6.0.4, and waiting for future 
versions of aircontrol probably won't fix it.
I just don't want to login to 300+ radios / access points to change firmware.  
Ugh!

I did notice you can do a broadcast from a manually entered device - but that 
does not appear to work - or it does
not find the equipment...


  ----- Original Message ----- 
  From: Troy Gibson, Byhalia.net,LLC 
  To: Ubiquiti Users Group 
  Sent: Thursday, August 31, 2017 12:58 PM
  Subject: Re: [Ubnt_users] aircontrol won't find 6.0.4 devices


  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> 
  Date: 8/31/17 1:25 PM (GMT-05:00) 
  To: Ubiquiti Users Group <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
  http://lists.wispa.org/mailman/listinfo/ubnt_users
_______________________________________________
Ubnt_users mailing list
Ubnt_users@wispa.org
http://lists.wispa.org/mailman/listinfo/ubnt_users

Reply via email to