Technical data

Configuring Rogue AP Detection Using the CLI

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.

6. In the Scanning time in ms text box, enter the amount of time Mitigating APs will

scan the scanning channels for rogue APs. This can be from 100 to 500

milliseconds.

7. In the Operational time in ms text box, enter the amount of time Mitigating APs

will spend in operational mode on the home channel. This can be from 100 to 5000

milliseconds.

8. In the Max mitigation frames sent per channel text box, enter the maximum

number of mitigation frames that will be sent to the detected rogue AP. This can

be from 1 to 50 deauth frames.

9. In the Scanning Channels text box, enter the list of channels that will be scanned

for rogue APs. Use a comma separated list from 0 to 256 characters. The complete

set of default channels are

1,2,3,4,5,6,7,8,9,10,11,36,40,44,48,52,56,60,64,149,153,157,161,165.

10. In the RSSI Threshold for Mitigation text box, enter the minimum threshold level

over which stations are mitigated. The range of valid values is from to -100 to 0.

11. Click OK.

Configuring Rogue AP Detection Using the CLI

These CLI commands configure rogue detection; for a complete explanation of the

commands, see the Meru System Director Command Reference.