Weblog entry #40 for Utumno

Fun with Intel 4965 wireless + kismet +aircrack-ng
Posted by Utumno on Sun 20 Jul 2008 at 09:28
Tags: ,

I thought I'd share with you how the latest iwl4965 wireless drivers are doing w/ respect to kismet, monitor mode, packet injection etc.

1) Stock Debian 2.6.25-2-486 kernel, kismet 2008-05-R1 ( from Debian unstable ) , ThinkPad X61 with

utumno# lspci | grep 4965
03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61)

Results: managed, ad-hoc mode - works, monitor mode - works, kismet is able to see management packets but no data packets. No matter what I do, it will not see clients nor data packets.

Coming out from monitor mode is kinda problematic: I press 'Q' in kismet, then it either segfaults leaving my card in an unknown state ( rmmod iwl4965; modprobe iwl4965 fixes that ) or sometimes exits cleanly but warns me that resetting the card failed. I still have to rmmod+modprobe to use the card in Managed mode.

Packet injection does not work. Trying out the latest compat-wireless-2008-07-19 + packet injection patches ( tutorial: http://aircrack-ng.org/doku.php?id=iwl4965&DokuWiki=b0f74a175e2ec1e58a11d7d3bfdb5650 ) does not work either: such compiled driver does not even work in managed mode, and rmmoding it results in a hard freeze ( there's nothing I can do apart from pushing the reset button )

2) Stock 2.6.26 kernel from kernel.org, latest ( 2008-07-19 ) compat-wireless with packet injection patches for iwl4965 and mac80211 , the same kismet 2008-05-R1 and ThinkPad X61:

Managed, ad-hoc mode fully work. Kismet is now able to see data packets and clients. Exiting it sucks even worse now, though: I press 'Q', it will always hang. The only way to recover is press 'Ctrl-Z' to put it in the background, kill -9 it and rmmod+modprobe the drivers.

Packet injection with AirCrack-ng works, at least the injection test passes. I haven't tried any more sophisticated attacks yet.

Side note: with 2.6.26 also the LED in my laptop (signifying that wireless is being used) started working. So progress in all fronts, except exiting kismet :)

 

Comments on this Entry

Posted by Anonymous (82.29.xx.xx) on Sun 20 Jul 2008 at 23:31
Thanks for sharing :) Wifi can be a pain.

I noticed you mentioned resetting the system by the reset button. Just incase you aren't aware but you can use Alt+SysRq key on your keyboard when you get a hard lock. Holding down these keys and typing R-E-I-S-U-B will safely shutdown/reset your system, instead of pressing the reset button on the case.

:)

http://en.wikipedia.org/wiki/Magic_SysRq_key

sno

[ Parent | Reply to this comment ]

Posted by Utumno (60.248.xx.xx) on Mon 21 Jul 2008 at 10:23
[ Send Message | View Utumno's Scratchpad | View Weblogs ]

Actually with Intel wifi chipsets ( and I've tried 2200, 3965 and 4965 ) I never had problems with managed mode. Stock debian kernels always worked right out of the box. Monitor mode + packet injection is a totally different story, though.

Thanks for the SysRq tip!

[ Parent | Reply to this comment ]

Posted by Anonymous (24.122.xx.xx) on Sat 2 Aug 2008 at 04:05
To exit Kismet, try this :
ifconfig wlan0 down
iwconfig wlan0 mode managed
ifconfig wlan0 up

Then, in my Kubuntu (kind of debian, anyway), I go to control panel and Desactivate, then immediatly I Reactivate it. Then it's back. No crash, no bug, just a bit long!

[ Parent | Reply to this comment ]

Posted by Anonymous (89.136.xx.xx) on Fri 29 Aug 2008 at 08:38
Just for the general public: currently, injection and monitor mode works wihout any problems ( fakeauth attack doesn't, but there are workarounds ). For info, check out the aircrack-ng page.

[ Parent | Reply to this comment ]

User Login

Username:

Password:

[ Advanced Login ]

Register Account

Quick Site Search