BUG: CSCud65237 - IMPACTING ASCOM 802.11N HANDSET
Friday, December 21, 2012 at 11:26AM
George

I received 2 emails from colleagues who were hit by this bug while using the Ascom i62. 

Apparently there is a BA ack issue, as noted in the bug. Its not clear if this is only impacting Ascom as the bug id references 802.11n handsets. I asked for frame captures and will post the result when I have them. 

 

CSCud65237 Bug Details

Encryption key corruption on BA ack with wrong ID
Symptom:
Voice disruption after roaming

Conditions:
Third party 11n phone
This is triggered by wrong TID sent on Block ACK by client. AP is incorrectly handling the invalid frame

Workaround:
roam to another AP



 Status Status 
Open 
(More) 
Severity Severity 
2 - severe 

Last Modified Last Modified 
In Last 3 Days 

Product Product 
Cisco IOS software 

Technology Technology 
Wireless, LAN (WLAN) 

1st Found-In 1st Found-in 
7.0(230.0)
7.4(1.54) 


Component(s) Component 
ap-ampdu 

Update on Tuesday, December 25, 2012 at 11:25AM by Registered CommenterGeorge

A follow up to this blog post: There is a TID issue which is the result of a bug in the Ascom phone while using 802.11n. Cisco has modified code and Ascom is working on a fix. Another work around is to disable 802.11n on the infrastructure.   

Article originally appeared on my80211.com (http://www.my80211.com/).
See website for complete article licensing information.