Bug 710 - Monitor mode issues
: Monitor mode issues
Status: VERIFIED FIXED
: IPW2200
Promiscuous mode
: 1.0.4
: IBM All
: P2 minor
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-06-21 13:12 by
Modified: 2005-07-14 01:34 (History)


Attachments
sample rfmon files in various driver states (6.95 KB, application/x-zip-compressed)
2005-06-21 13:15, Ivan Warren
Details
fix patch (1.60 KB, patch)
2005-06-22 04:30, Zhu Yi
Details | Diff


Note

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


Description From 2005-06-21 13:12:24
When the ipw2200 driver module is loaded with 'mode=2' or if it is loaded, then
turned to monitor mode with iwconfig, rfmon works according to specs..

If, however, the module is loaded but a WEP key is initially assigned - and
subsequently, monitor mode is turned on and the WEP key is disabled (via
iwconfig ethX mode monitor && iwconfig ethX enc off), rfmon mode doesn't work.

I marked this as "minor" since an easy work around is simply to recycle the
module (modprobe -r ipw2200 && modprobe ipw2200) which does the trick everytime.

NOTE : by not working I mean the following :
- I know the WEP key, yet none of the WEP decyphering tools I use (namely
aircrack's 802ether utility) are capable of decrypting the WEP data packets.
- A 'working' rfmon session shows IVs being issued pretty much in sequence and
the KeyID always being the same.. the non-working version shows totally random
IVs and random KeyIds (in the 0-3 range of course).

I am of course willing to provide any additional information should you find it
necessary to resolve this issue.

Thank you,

--Ivan
------- Comment #1 From 2005-06-21 13:15:14 -------
Created an attachment (id=435) [details]
sample rfmon files in various driver states

sample1* are working rfmon data (modprobe ipw2200 mode=2)
sample2* are bogus rfmon data (ifup eth1&&ifdown eth1&&iwconfig ..)
------- Comment #2 From 2005-06-22 04:30:21 -------
Created an attachment (id=436) [details]
fix patch
------- Comment #3 From 2005-06-22 12:43:14 -------
Fixed !

Thanks a lot,

--Ivan
------- Comment #4 From 2005-06-23 01:17:19 -------
Mark as fixed.
------- Comment #5 From 2005-07-13 16:41:54 -------
Has this patch been merged in?

Please don't mark as FIXED before the patch has been included upstream.
------- Comment #6 From 2005-07-13 23:41:11 -------
The patch is in 1.0.6. I changed it slightly as the one attached here.
------- Comment #7 From 2005-07-14 01:34:33 -------
Mark as fixed in 1.0.6.