Applications

Different applications can run in the controller. To activate or de-activate them, you have to put their name(s) in the poolfile of the controller.

They can be found in the applications directory of the controller.

Applications for Channel Assignmnent, able to modify the channel of the APs and their associated STAs. They also allow to obtain real-time statistics of the APs and their STAs.
SmartApSelection: It is a proactive application that is in charge of mobility management and load balancing simultaneously. It performs periodical scans, gets the information and, if needed, hands off STAs between APs. It has different modes for load balancing.
SimpleLoadBalancer: It makes a distribution of the STAs between the APs. It uses a round-robin algorithm. Its main limitation is that it is not coordinated with mobility management.
MobilityManager: It is a reactive application that is in charge of handoffs. When the STA moves, the origin AP reports this fact to the controller, and this triggers the whole proccess. The statistics obtained with the auxiliary wireless interface are used for selecting the best suited AP for the STA. A seamless handoff is run between the "origin" and the "destination" APs. It is not coordinated with load balancing.

DemoStatistics: It allows the user to select between the Wi-5 APs and the associated STAs, and get detailed statistics of each of them, and also about the wireless environment.
ShowStatistics: It gets the statistics from the APs, and periodically shows them by the screen of the controller.
FlowDetectionManager: It gets the information from the detection agent and shows it by the screen of the controller.
ShowMatrixOfDistancedBs: It builds a matrix of the "distance" in dB between Wi-5 APs. During a time interval, each AP sends beacons with a special SSID, and the rest of APs hear them. They can then calculate the average signal level. Both things (sending and receiving) are performed by the auxiliary wireless interface.
ShowScannedStationsStatistics: An AP uses its secondary interface to scan all the channels, and obtain all the frames heard, and their statistics. This is done with the auxiliary wireless interface.

HandoverMultichannel: It is able to make a kind of ping-pong of a STA between two APs. A period is defined, and the STAs periodically make a seamless handoff between the APs, as long as the minimum power threshold is accomplished.
OdinMobilityManager: It is an old version of MobilityManager. The entity that starts the handoff is the destination AP, when it feels a new STA approaching. It only works if the APs are in the same channel.

Some things to take into account

Some applications have an initial period in which they are idle, in order to let you start the agents. For example, MobilityManager has a line this.giveTime(30000); which stops the application for 30 seconds before calling init(). You MUST start the agents during this period, or they will not participate in the application algorithms.