Bugzilla – Bug 407
Missing association events with ipw2100-1.0.1
Last modified: 2005-10-04 13:09:50
You need to log in before you can comment on or make changes to this bug.
The ipw2100 driver used to generate an association event (iwevent) upon the radio being re-enabled using SW RF kill and other firmware restarts. These association events will cause wpa_supplicant to re-authenticate, which is needed if the firmware has been restarted etc. This is no longer true with ipw2100-1.0.1. No association event is generated when re-enabling the radio using '/bin/echo 0 > /sys/class/net/eth1/device/rf_kill' and no association event is generated upon a firmware restart caused by a hw_send_command timeout (bug #245).
Please run w/ debug level set to 0x3fff and attach the dmesg output that captures what the driver is trying to do from the point it handles the SW RF switch being set to 0.
Created an attachment (id=166) [details] dmesg output with debug=0x3fff
Ok, dmesg output attached. Reopening.
Created an attachment (id=242) [details] Sends disassociation event to user space on NIC reset This should correct the problem of not sending a disassociation event when the firmware is being restarted.
Fixed in 1.0.3
Reopening since this problem still exists in 1.0.3 (at least with the ipw2100-1.0.3-hang.patch).
Created an attachment (id=247) [details] Properly send disassociation events to user space With the help of logics in irc I have prepared a patch which properly sends disassociation events to user space when either ipw2100_reset_adapter() or ipw2100_down() is called.
Created an attachment (id=248) [details] Keep a 1:1 relation between associations/disassociations Updated patch.
Fixed in 1.0.4.
Verified.