Technical data
198 Meru System Director Configuration Guide © 2012 Meru Networks, Inc.
Modifying Detection and Mitigation CLI Settings
—
Last Reported Time The time the AP was last discovered. If this field is blank,
the AP has not been discovered yet.
5. To remove a blocked BSSID from the ACL, select the checkbox of the blocked AP
entry you want to delete, click Delete, and then click OK.
Configure Scanning and Mitigation Settings with the Web UI
To configure rogue AP scanning and mitigation settings, follow these steps:
1. From the Web UI click Configuration > Wireless IDS/IPS > Rogue APs.
The Rogue AP screen appears with the Global Settings tab selected. See Figure 29.
Figure 31: Web UI Rogue AP Global Settings
2. In the Detection list, select one of the following:
— On: Enables scanning for rogue APs.
— Off: Disables rogue detection.
3. In the Mitigation list, select one of the following:
— No mitigation: No rogue AP mitigation is performed.
— Block all BSSIDs that are not in the ACL: Enables rogue AP mitigation of all
detected BSSIDs that are not specified as authorized in the Allowed APs list.
— Block only BSSIDs in blocked list: Enables rogue AP mitigation only for the
BSSIDs that are listed in the Blocked APs list.
— Block Clients seen on the wire: Enables rogue mitigation for any rogue station
detected on the wired side of the AP (the corporate network, in many cases).
When Block clients seen on the wire is selected, clients seen on the corporate
network are mitigated. When Block clients seen on the wire is selected and
the BSSID of the wired rogue client is entered in the blocked list (see Alter the
List of Blocked APs with the Web UI) only listed clients are mitigated.
4. In the Rogue AP Aging box, type the amount of time that passes before the rogue
AP alarm is cleared if the controller no longer detects the rogue. The value can
be from 60 through 86,400 seconds.
5. In the Number of Mitigating APs text box, enter the number of APs (from 1 to 20)
that will perform scanning and mitigation of rogue APs.