02-05-2025 04:47 PM
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?
Solved! Go to Solution.
02-05-2025 05:24 PM - edited 02-05-2025 05:25 PM
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
02-05-2025 05:24 PM - edited 02-05-2025 05:25 PM
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
03-18-2025 07:49 AM - edited 03-18-2025 07:50 AM
> 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
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide