cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1255
Views
1
Helpful
2
Replies

Rogue AP

hs08
VIP
VIP

In the WLC we can contain the Rouge AP, but how we can make sure our AP is not contained by neighbor WLC if the my AP located not to far with neighbor AP?

1 Accepted Solution

Accepted Solutions

Haydn Andrews
VIP Alumni
VIP Alumni

To start off containment is technically illegal in most countries, unless the rogue is connected to your network or broadcasting your SSID to be malicious.

You would see aWIPS events of Deauthentication Flood, but you need Catalyst Center for aWIPS. That being said you would see clients being dropped from your network as containment will send clients connecting to it deauthentication frames.

Easiest way to protect is to run MFP as mandatory

https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-5/config-guide/b_wl_17_5_cg/m_awips.html 

*****Help out other by using the rating system and marking answered questions as "Answered"*****
*** Please rate helpful posts ***

View solution in original post

2 Replies 2

Haydn Andrews
VIP Alumni
VIP Alumni

To start off containment is technically illegal in most countries, unless the rogue is connected to your network or broadcasting your SSID to be malicious.

You would see aWIPS events of Deauthentication Flood, but you need Catalyst Center for aWIPS. That being said you would see clients being dropped from your network as containment will send clients connecting to it deauthentication frames.

Easiest way to protect is to run MFP as mandatory

https://www.cisco.com/c/en/us/td/docs/wireless/controller/9800/17-5/config-guide/b_wl_17_5_cg/m_awips.html 

*****Help out other by using the rating system and marking answered questions as "Answered"*****
*** Please rate helpful posts ***

Rich R
VIP
VIP

how we can make sure our AP is not contained by neighbor WLC
You cannot control how the other WLC is configured, but if they break the law (illegal containment) you can report them to the regulator for regulatory enforcement (but a friendly chat with your neighbours might be the better option).  But like @Haydn Andrews says using MFP ensures that spoof de-auth frames (which is how containment is done) cannot be used.
https://en.wikipedia.org/wiki/IEEE_802.11w-2009
https://techsearch.watchguard.com/KB?type=Article&SFDCID=kA10H000000bqRZSAY&lang=en_US

------------------------------
Please click Helpful if this post helped you and Accept as Solution (drop down menu at top right of this reply) if this answered your query.
------------------------------
TAC recommended codes for AireOS WLC's   and   TAC recommended codes for 9800 WLC's
Best Practices for AireOS WLC's,   Best Practices for 9800 WLC's   and   Cisco Wireless compatibility matrix
Check your 9800 WLC config with Wireless Config Analyzer using "show tech wireless" output or "config paging disable" then "show run-config" output on AireOS and use Wireless Debug Analyzer to analyze your WLC client debugs
Field Notice: FN63942 APs and WLCs Fail to Create CAPWAP Connections Due to Certificate Expiration
Field Notice: FN72424 Later Versions of WiFi 6 APs Fail to Join WLC - Software Upgrade Required
Field Notice: FN72524 IOS APs stuck in downloading state after 4 Dec 2022 due to Certificate Expired
- Fixed in 8.10.196.0, latest 9800 releases, 8.5.182.12 (8.5.182.13 for 3504) and 8.5.182.109 (IRCM, 8.5.182.111 for 3504)
Field Notice: FN70479 AP Fails to Join or Joins with 1 Radio due to Country Mismatch, RMA needed
Field Notice: FN74383 APs Running 17.12.4/5/6/6a May Run Out of Flash Space Preventing Upgrades
How to avoid boot loop due to corrupted image on Wave 2 and Catalyst 11ax Access Points (CSCvx32806)
Field Notice: FN74035 - Wave2 APs DFS May Not Detect Radar After Channel Availability Check Time
Leo's list of bugs affecting 2800/3800/4800/1560 APs
Default AP console baud rate from 17.12.x is 115200 - introduced by CSCwe88390
Review Cisco Networking for a $25 gift card