AirControl Release Notes

For user guide please visit: http://www.ubnt.com/wiki/index.php?title=AirControl


1.4.x Changes

1.4.2-beta (2011-08-23)
1.4.1-beta (2011-07-11)
1.4-beta (2011-05-27)
NOTE: If you are running AC with more than 500 managed devices (or many CPEs in general), please see tuning info here: http://www.ubnt.com/wiki/AirControl#Server_Tuning

1.3.x Changes

1.3.8-beta (2011-04-11)
1.3.7-beta (2011-03-03)
1.3.6-beta (2011-01-19)
1.3.5-beta (2010-12-29)
1.3.4-beta (2010-11-24)
1.3.3-beta (2010-10-27)
1.3.2-beta2 (2010-09-21)
1.3.1-beta (2010-09-15)

For scheduling of recurring tasks, we recommend using device groups (instead of selecting specific devices or creating duplicates of the same task).

Device groups can be managed through the left side groups panel. You can use it to create your own device groups and use them for scheduling tasks. As an example, if you wanted to specify a backup task for all devices, select the "All Devices" group and then schedule. Or, alternatively create a custom group called "Backup Devices" with all the units you want to run the backup task for. Another example would be creation of a "Ping Devices" group, and then schedule a task for that group.

You will see the group name displayed in the schedule dialog and whenever the specified task runs, it will run for all valid members of the group at the time of execution. By using this method the list of devices becomes dynamic and can be changed by adding or removing devices from the group rather than recreating duplicate device tasks. Using device groups optimizes the processing of tasks in the system and will provide a single line summary in the system log.
1.3-beta (2010-08-15)

NOTE: UI modifications: Toolbar controls for device groups tree and device list are now at the top with drop down menu handle on the right side.

1.2.x Changes

1.2-beta (2010-06-24)

Scheduling

Existing dialogs (upgrade, device scan/add) and new reboot dialog now have a scheduling option. For recurring task, select start date and interval, end date is optional. Note that execution time for recurring tasks is always calculated relative to the start date/time. Existing scheduled tasks can be managed from "Schedule" tab (delete/edit), while new tasks are created from existing navigation path in device list main screen. Last modified date/time in schedule list will indicate either when a task was modified by user through UI or last time executed.

IPERF Speed Test Launcher

Run speed test from the AirControl UI, without having to log into multiple devices. This is particularly useful for testing multiple units in a row. The launcher is designed to launch client and optional server on local or remote hosts (via SSH). A typical usage scenario would be to launch the server on the AirControl host and the client on AirOS 5.x, or on a host connected to the wireless device for 3.x firmware. 

AirControl does not implement the speed test, it launches iperf and redirects iperf output to the UI. Therefore, interpretation of output and test results are specific to iperf and can be reproduced by running iperf manually when in doubt.

AirControl does not contain or install iperf. This needs to be already installed on both hosts that the test runs for. AirOS 5.x includes iperf, older AirOS versions do not. Distributions are available for Linux (often already installed), Windows etc. 

This speed test launcher does not inter-operate with AirOS speed test (tools menu in the AirOS web UI).

1.1.x Changes

1.1.01-beta (2010-04-28)
It was about time to label it version 1.1. Beta status remains - at this time our priority is to increase the feature set.

Known Issues and Limitations

1.0.x Changes

1.0.09-beta (2010-03-15)
1.0.08-beta (2010-02-06)
1.0.07-beta (2010-01-17)
1.0.06-beta (2010-01-08)
1.0.05-beta (2009-12-21)
1.0.04-beta (2009-12-03)
1.0.03-beta (2009-10-28)
1.0.02-beta
1.0.01-beta