Re: Storming and age

KC wrote:
> Addition: instead of
> 
>  > ipw2200: U ipw_deinit Disassociating during shutdown.
>  > ipw2200: U ipw_send_disassociate Disassocation attempt from
>  > 00:11:22:33:44:55 on channel 6.
> 
> it now cycles through association -> storming -> age with a different 
> output right after assoc:
> 
> ipw2200: U ipw_associate_network associating: 'Al' 00:11:22:33:44:55
> ipw2200: I ipw_rx_notification AUTH_SEQ_1
> ipw2200: I ipw_rx_notification disassociated: 'Al' 00:11:22:33:44:55
> ipw2200: U __ipw_send_cmd SCAN_REQUEST_EXT command (#26) 96 bytes: 0x00000023
> 
> Any ideas?

Storming is essentially a fixed association backoff that keeps the
driver from going into a tight loop trying to associate to a single AP,
failing, trying, failing, etc.  So it puts a 3s timeout between
association attempts to any one AP.

Age means you haven't received a beacon or probe response from that
network for > 25 seconds.

The 'AUTH_SEQ_1' notification means the authentication sequence during
association is failing, most likely due to a timeout in not receiving
the response from the AP.  Association fails.

What is the signal strength of the network when seen via 'iwlist scan'?

The above would indicate that the AP is likely providing a weak signal,
is under heavy load, or you have a saturated or RF noisy network that is
preventing consistent communication betweeen the AP and your client.

Are there other 802.11 networks on that channel?  Bluetooth devices in
use?  Does anyone use a 2.4Ghz wireless / cordless phone within 300 feet
of where you ware?   Wireless keyboard and/or mouse?

James



> 
> KC wrote:
> 
>>Hi,
>>
>>I noticed that with certain access points the card sometimes connects 
>>normally and then disassociates either due to storming or age. What exactly 
>>does it mean and why does it happen? I think it is something about the 
>>configuration of the access points because some of them always have this 
>>problem, others work just fine (unfortunately, the ones that give trouble 
>>are not controlled by me so I cannot check or change any configurations 
>>there). Attached is dmesg of one such case. Apparently it associated 
>>successfully once, but then disassociated and complained about storming, 
>>after another few minutes it complained about age. Is there something I can 
>>tweak to make it work?
>>
>>Regards,
>>
>>KC
>>
> 
> 
> 
> _______________________________________________
> ipw2100-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipw2100-devel