Latest working kernel version: Patch from aircrack-ng Earliest failing kernel version: 2.6.28-rc4 Distribution: Debian (sid) Hardware Environment: Lenovo Thinkpad T61 Software Environment: aircrack-ng 1.0rc1 Problem Description: First time I run aireplay-ng -9 mon0 01:24:36 Trying broadcast probe requests... 01:24:36 Injection is working! 01:24:37 Found 3 APs 01:24:37 Trying directed probe requests... 01:24:37 *:*:*:*:*:* - channel: 6 - '*****' ^C/20: 5% After running aireplay-ng -3 or -1 Injection stops working aireplay-ng -9 mon0 01:34:30 Trying broadcast probe requests... 01:34:32 No Answer... 01:34:32 Found 0 APs
What kernel version worked? What driver are you using?
It worked with 2.6.26 with some patches. I am using iwlagn for 4965AGN.
So, you needed extra patches on 2.6.26? And now the patches don't work anymore? I think you need to report that problem to whomever wrote those patches (presumably the aircrack guys)...
No that's not what I wrote. With new version of driver which went to kernel mainline, there is no need for patching. And software reports that it works first time and second time that it does not. That's a obvious bug. Forget about patches, latest iwlagn does not need patching for that and aircrack is just one of programs that show that something is wrong.
Could you please provide debug logs for driver at the point when aircrack fails? Ensure your driver is compiled with debugging (you will know it is when in dmesg the driver version has a "d" after the version number). During runtime, at the point where aircrack fails, you can enable debugging like so: echo 0x43fff > /sys/class/net/wlanX/device/debug_level
I do not work with packet injection, but i recently saw something that may be relevant to your problem. Please see http://sourceforge.net/mailarchive/forum.php?thread_name=b170af450901060931h3fa99fc7xfbb1873515c0c996%40mail.gmail.com&forum_name=ipw3945-devel You need to use airmon-ng to start the interface. This is when the mon0 interface is created.
Two months since we hard from reporter. Can this bug be closed?