Bugzilla – Bug 710
Monitor mode issues
Last modified: 2005-07-14 01:34:33
You need to log in before you can comment on or make changes to this bug.
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
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 ..)
Created an attachment (id=436) [details] fix patch
Fixed ! Thanks a lot, --Ivan
Mark as fixed.
Has this patch been merged in? Please don't mark as FIXED before the patch has been included upstream.
The patch is in 1.0.6. I changed it slightly as the one attached here.
Mark as fixed in 1.0.6.