cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
13713
Views
5
Helpful
30
Replies

Devices keep disconnecting since WAP561

Michiel Beenen
Level 3
Level 3

Hello Cisco,

Now Im a big Cisco fan so i replaced our Airport access points in the house with the WAP561.

My main problem is that since i did that, once in a while (if i had to guess every couple of hours) I have our laptops, iphones disconnecting and then it takes the device a while to be able to reconnect to the access point (unless you manually disable wifi and enable it again).

Ive been trying to figure out how this would be possible but so far I have no clue. 
Running Firmware 1.0.4.4, The Radio is set to 20Mhz (also on 20/40 same result) with a static channel (6), there is no other wifi ssid's around us so that cant be it. We use WPA2 keys and all the other settings are pretty default. (No QOS, No VLAN, No guest)

We didnt have this problem at all with Airport express/extreme from Apple, all devices stayed connected forever.

I hope someone can help me cause this is seriously annoying.... i want my devices to stay connected.

The only thing i can find in the logs is this:

May 9 2014 10:46:37infohostapd[2135]wlan0: WPA STA 60:03:08:92:7a:00 pairwise key exchange completed (WPAv2) 
May 9 2014 10:46:37infohostapd[2135]wlan0: IEEE 802.11 STA 60:03:08:92:7a:00 associated with BSSID 18:9c:5d:39:67:00 
May 9 2014 10:46:37infohostapd[2135]wlan0: IEEE 802.11 Assoc request from 60:03:08:92:7a:00 BSSID 18:9c:5d:39:67:00 SSID Mnet 
May 9 2014 10:46:37infohostapd[2135]wlan0: IEEE 802.11 STA 60:03:08:92:7a:00 deauthed from BSSID 18:9c:5d:39:67:00 reason 3: STA is leaving IBSS or ESS 
May 9 2014 10:46:19infohostapd[2135]wlan0: IEEE 802.11 STA 54:e4:3a:2f:93:78 deauthed from BSSID 18:9c:5d:39:67:00 reason 4: Disassociated due to inactivity 
May 9 2014 10:46:14infohostapd[2135]The wireless client with MAC address 54:e4:3a:2f:93:78 has been successfully authenticated.
 
May 9 2014 10:47:02infohostapd[2135]wlan1: IEEE 802.11 STA 54:e4:3a:2f:93:78 deauthed from BSSID 18:9c:5d:39:67:10 reason 4: Disassociated due to inactivity
30 Replies 30

aeccles
Level 1
Level 1

Did you ever get to the bottom of this?  Experiencing similar issues where clients lose their DHCP address.  The latest firmware has not helped.  It seems like rebooting the units helps a lot for about a week.

Shannon Ward
Level 1
Level 1

Was this problem ever solved on the wap561?  I see switching to another product solved Michiel's problem, but that is not a solution.  

 

I am running 1.1.0.4 and I see BSSID disassociations for inactivity after 8 minutes???  Cisco, can you help with this problem?

I've tried changing just about everything possible in the settings and nothing has resolved the issue.  I've had a case open on this for a while (its taking some time due to the need to find service windows to implement recommended changes) and it was just escalated today.  I would urge you to open a case with cisco TAC as well.  If you search the forums long enough you will see that there are quite a few people with this problem.  Hopefully if enough of us open tickets they will finally release a fix.

Yep.  Got a cisco service contract.  Opened a case. 

Please update, so I can fix this exact issue. 

We're having the same issues at work. 

iPad's are connected then deauthenticated. 

station: 74:e1:b6:9a:a6:XX deauthenticated
Station 74:e1:b6:9a:a6:XX had an authentication failure, reason 16
Station 74:e1:b6:9a:a6:XX had an authentication failure, reason 22
Station 74:e1:b6:9a:a6:XX had an authentication failure, reason 22

What can be causing this????

 

Hi, My name is Eric Moyers. I am a Network Support Engineer in the Cisco Small Business Support Center. Thank you for using the Cisco Community Post Forums.

I am sorry to hear that you are experiencing this issue. 

  • Reason Code 16: Authentication failed due to a user credentials mismatch.
  • Reason-Code 22: The client could not be authenticated because the Extensible Authentication Protocol (EAP) Type cannot be processed by the server.

I see from your post that you mention IPads, are these the only ones having this issue? What is your Authentication Encryption set to? WPA, WPA2?

Eric Moyers
.:|:.:|:. CISCO | Eric Moyers | Cisco Technical Support |
Wireless and Surveillance Subject Matter Expert

Please rate helpful Posts and Let others know when your Question has been answered.

 

Michiel Beenen
Level 3
Level 3

I have seemed to fix most things by doing the following:

- Disable Bandwidth Utilization
- Set a static channel per radio (1,6,11)
- Disable Bonjour (leave that to the router and/or switch instead)

That's it. It all works perfectly fine now :)

Henry Unger
Level 1
Level 1

I was having the same symptoms with a pair of WAP321 devices and replaced them with WAP561 devices which seemed to have solved the problem until I upgraded my Apple iOS devices from iOS 7 to iOS 8. Since then it has degraded substantially with the devices receiving DHCP leases but being unable to access resources locally or on the Internet. I ended up unplugging both WAPs and then plugging them back in again and the symptoms seem to have subsided for now.

So basically, you rebooted.  Thanks for the post.

I'll be trying this issue tomorrow morning with our three WAP 561s. 

iPads (iPads only) will connect, may be connected for 5 - 20 minutes, then be stop being able to connect. 

Super frustrating to an employee that needs to work for an hour on end from their iPad. 

Station 74:e1:b6:9a:a6:10 had an authentication failure, reason 16

Station 74:e1:b6:9a:a6:10 had an authentication failure, reason 22

Station 74:e1:b6:9a:a6:10 had an authentication failure, reason 22

Michiel Beenen
Level 3
Level 3

   

kurian
Level 1
Level 1

I'm having the exact same problem with my WAP371 as well. What's actually happening is it's no longer bridged to the switch LAN. If I set a static IP on the iPhone I can connect to the WAP371's web interface, but cannot access anything on the switch LAN.

A R
Level 1
Level 1

Hi (sorry for my english), same problem, several device keep disconnecting, ipad, iphone, win 8 tablet, win 7-10 notebook. aps log a lot of authentication failure.

i have noticed some device start problems after about 30 sec, others devices after about 1 hours.

Tuning "broadcast key refresh rate" and "session key refresh rate" (default 300sec and 30 sec) on wireless->network-> Virtual Access Pint SSIDs->details seems workaround the problem. First i tried disabling them (setting value 0), after i tried setting higher values (36000sec and 3600sec) with good result

hope i help you.

Why not leave the key refresh rate at 0? This should fix most problems.

I would think you would want to auto-rotate keys at least once per day as a general security practice.