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 [email protected] http://lists.wispa.org/mailman/listinfo/ubnt_users
