(ARCHIVED) airControl - Get Started with Device Discovery

This article has been archived.

This article is current to the last version of airControl, but will not be updated further since airControl has been retired.

Readers will learn how to use airControl to perform a network scan to determine how devices are connected in a network. Find more airControl information in the airControl User Guide.

Topology Root:Topology root represents the starting point of your network topology which usually is also your airControl server.

Table of Contents

  1. Device Discovery
  2. Topology Resolution, Unplaced Devices and Ignored Devices
  3. Introduction of TCP-IP Range Scan Discovery
  4. Related Articles

Device Discovery

Back to Top

Devices can be discovered using any of the following methods:

  • Broadcast Discovery: Discover devices by scanning the network.
  • IP Range Scan: Discover devices by scanning a user-defined range of IP addresses using UDP protocol.
  • TCP IP Range Scan: Discover devices by scanning a user defined range of IP addresses using TCP protocol. Only available for devices with firmwares that support TCP IP Range Scan. Should be used when regular IP Range Scan does not yield results.

Topology Resolution, Unplaced Devices and Ignored Devices

Back to Top

Discovery started with the "Resolve Topology" option enabled should automatically determine device location in the network topology. Devices for which topology cannot be determined will end up under the "Unplaced Devices" folder. Administrators can move devices from the "Unplaced Devices" folder to the topology by editing device properties and selecting a new parent in the network topology.

Ignored Devices

An ignored device will not appear in discovery search results. This is useful when, for example, you do not know a device's password. You can just ignore the device to avoid having to re-enter the password. Only unmonitored devices can be ignored.

Introduction of TCP-IP Range Scan Discovery

Back to Top

Starting from firmware v6.0.4 (and v8.1.3 for 11AC) airOS discovery only answers to discovery requests sent from private IPs (https://tools.ietf.org/html/rfc1918#section-3). This is a security measure.

What this means for airControl is that a IP Range Scan will not find devices if discovery packets are sent with a public source IP. To mitigate this issue we implemented a new discovery method that uses TCP protocol. When using TCP Discovery you can find devices even if the server reaches them using public IP.

The discovery restriction was introduced in airOS v6.0.4 for airMAX M-series devices, but TCP discovery was added in v6.0.6. Please remember to keep your devices updated to the most current airOS version (https://www.ubnt.com/download/airmax-m).

Related Articles

Back to Top

airControl - Discovered Devices Fall into 'Unplaced Devices' Folder 

Was this article helpful?
0 out of 2 found this helpful
Can't find what you're looking for?
Visit our worldwide community of Ubiquiti experts for more answers
Visit the Ubiquiti Community