Bug 701 – "iwpriv sw_reset" can not reset driver from monitor mode

Bug 701 - "iwpriv sw_reset" can not reset driver from monitor mode

Summary:

"iwpriv sw_reset" can not reset driver from monitor mode

Status:	VERIFIED FIXED

Product:	IPW2200
Component:	Wireless Tools
Version:	1.0.4
Platform:	All Fedora Core 2

Importance:	P2 normal
Assigned To:	Zhu Yi
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-16 23:57 by Yan, Yechun
Modified:	2005-10-31 23:22 (History)

Attachments
dmesg from load to sw_reset (20.27 KB, application/octet-stream) 2005-06-17 01:51, Yan, Yechun	Details
Dmesg output with version 1.0.5 (124.43 KB, text/plain) 2005-07-14 12:13, Salwan Searty	Details
fix patch (522 bytes, patch) 2005-07-14 23:28, Zhu Yi	Details \| Diff
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description From Yan, Yechun 2005-06-16 23:57:18

Steps:
1. associate NIC with AP, manage mode;
2. iwconfig eth1 mode monitor;
3. iwpriv eth1 sw_reset
4. iwconfig

step 4 shows that NIC under managed mode, but cann't associate with any AP, even
if we set the channel and essid... unless reload the driver.

in dmesg, full filled by: "Unknown management packet: 64" ...

------- Comment #1 From Yan, Yechun 2005-06-17 01:51:48 -------

Created an attachment (id=425) [details]
dmesg from load to sw_reset

dmesg from load to sw_reset.

------- Comment #2 From Zhu Yi 2005-06-17 03:35:33 -------

please verify in 1.0.5

------- Comment #3 From Salwan Searty 2005-07-14 12:13:15 -------

Created an attachment (id=460) [details]
Dmesg output with version 1.0.5

Verification failed in 1.0.5 using the same repro steps above. Dmesg output
from load to sw_reset is attached.

------- Comment #4 From Zhu Yi 2005-07-14 23:28:33 -------

Created an attachment (id=464) [details]
fix patch

------- Comment #5 From Zhu Yi 2005-07-14 23:31:28 -------

mark as fixed

------- Comment #6 From Salwan Searty 2005-07-20 15:31:57 -------

Hi Yi,
Did you mean to mark it as TESTED_PATCH_EXISTS? (instead of FIXED)

------- Comment #7 From Salwan Searty 2005-07-20 15:36:18 -------

With above patch applied to 1.0.6, the above scenario works correctly. (I was 
able to associate correctly after step 4 above.)

With 1.0.6 unpatched, problem exists.

Setting to TESTED_PATCH_EXISTS for this to be picked up by developers.

------- Comment #8 From Zhu Yi 2005-08-08 22:17:31 -------

patch merged.

------- Comment #9 From Salwan Searty 2005-08-12 07:30:33 -------

Setting target milestone to 1.0.7.

------- Comment #10 From Mi, Jun 2005-10-31 23:22:50 -------

Verify this bug on 1.0.8.
step 4 shows that NIC under managed mode associate with any AP.