Re: Containment only prevents NEW client connections-Existing cl
Unfortunately, that will have no bearing on the fact that when you contain foreign, rogue APs, any of your trusted wireless clients that may happen to already be attached to them will not be knocked off of the rogue AP.
The point of the original post was this:
Don't assume that by implementing containment that you are knocking off clients who have already connected to a rogue AP. You will only prevent new clients from attaching.
Since there is no message from the WLC/WCS system stating that existing rogue clients will not be affected until they roam or disassociate/reassociate from the rogue AP, it is easy to assume (as I did) that containment "jams" existing wireless clients. This could easily lead to a false sense of security.
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
This is the start of a display filter cross reference between Wireshark
and OmniPeek. The 1st installment is a table of advanced filters. More
filters will be added as time allows. It is a living doc, so check back
for changes every so often Please feel f...
I have created a Powershell script to automatically add a Wireless Guest
User on Cisco WLCs. (tested on 2500 Series) The script should be
completely self explanatory. Prerequisites: Powershell SNMP Module
(Install-Module -Name SNMP) SNMP Write Access to y...