Why is a fault generated regardless of the threshold set for detecting rogue APs with an defined RSSI value under IDS > Manage Network-Wide IDS Settings?
For example, the threshold is set for detecting a rouge AP with an RSSI value of greater than -80dBM, but alerts are being generated for a rogue AP with an RSSI value of -200 dBm. A. What happens is as follows: –First, a rogue is detected which has an RSSI value higher than the configured threshold. For example, it has an RSSI value of -60dBm and the configured threshold is -80dBm. –Then, the rogue is not seen for a while, and the WLSE marks it for deletion. (Rogue APs that are not heard from for a long time are candidates for deletion from the WLSE.) –The reporting APs are removed, and the rogue AP’s RSSI is tagged as -200dBm. (The -200dBm value is used internally to indicate “no observed signal.” This value is used for tagging rogues, which are candidates for deletion.
For example, the threshold is set for detecting a rouge AP with an RSSI value of greater than -80dBM, but alerts are being generated for a rogue AP with an RSSI value of -200 dBm. A. What happens is as follows: –First, a rogue is detected which has an RSSI value higher than the configured threshold. For example, it has an RSSI value of -60dBm and the configured threshold is -80dBm. –Then, the rogue is not seen for a while, and the WLSE marks it for deletion. (Rogue APs that are not heard from for a long time are candidates for deletion from the WLSE.) –The reporting APs are removed, and the rogue AP’s RSSI is tagged as -200dBm.
Related Questions
- Yes, any object defined in the data files can be placed on the map, regardless of which tileset it is normally associated with. Will the new map editor support extended upgrade values?
- Why is a fault generated regardless of the threshold set for detecting rogue APs with an defined RSSI value under IDS > Manage Network-Wide IDS Settings?
- What is a Rogue AP? Can the rogue APs in my wireless network be automatically blocked?
