• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 749
  • Last Modified:

Cisco WLC 2504 - How can I log if someone is actively trying to BRUTE FORCE their way into my WLAN?


I have a Cisco WLC 2504 Controller with a Cisco 1602i AP (1).  Switch is a Cisco SG-300.

I have (4) VLANs:
  100 - DMZ
  101 - Data (
  102 - Voice (
  200 - WLAN (

The WLC is on VLAN 200,  
The AP (Aironet 1602i) is on VLAN 200,  The AP is on a TRUNK port.
DHCP for clients is being passed by a Windows server on the data subnet.
The AP joins the WLC fine, and is under management.

I suspect that my WLAN is under attack / brute force.  However, when I look at logs, I see logs of ROGUE AP's, I see logs of UNKNOWN AP's, but nothing about BAD PASSWORD, even when I intentionally authenticate badly against the AP.  

Can anyone tell me how to audit / log / review if there are extensive bad authorizations on my WLC?  All of the clients that I see on the AP are clients I expect...there is nothing unexpected ASSOCIATED already, but I suspect an attack.  Here's why:

On the VOICE NETWORK, voice was very choppy.  pings to the voice switch management interface get 1 in 10 drops and 20-30ms latency on a medium sized LAN.  I reviewed the voice switch, and it was catching 75-100% activity consistently from port 1, the WLAN AP (The AP is in this switch because it is the only POE switch, an AdTran 1234).  I moved the AP into the core switch (Cisco SG-300) with a POE injector, and now the switch is happy, voice is back to normal, and I'm not dropping packets to the voice switch anymore.

Any insight into how to log this would be very helpful.

1 Solution
Craig BeckCommented:
First, unless you're using APs in FlexConnect (what used to be called H-REAP) mode you should connect the APs to an access port, not a trunk port.  All traffic is tunnelled to the WLC in CAPWAP so no user traffic hits the switch on user VLANs.

You can use WIPS to detect suspected intrusions, but generally rogue APs are normal.  The prerequisite for WIPS though is that you need an MSE as well as a WLC and Prime.

If you are using a preshared key you'll just see association failures but nothing for authentication failures.  If you're doing RADIUS-based authentication you'll see AAA failures.

Voice traffic should be using QoS on the WLAN and the wired network.  In the WLC you can configure the Voice SSID to use the Platinum QoS profile - that will tell the WLC to prioritize voice traffic on the Voice SSID.
jkeegan123Author Commented:
The closest answer was:  "If you are using a preshared key you'll just see association failures but nothing for authentication failures".  The question was close to answered in this way, but it was not exactly what I was looking for.  I was looking for a way to LOG failed attempts at association.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now