FreeBSD 9.0 ath driver injection with aireplay_ng returns
input/output error in AHDemo and Monitor mode
merlin at merlinsbox.net
Mon Feb 6 18:53:12 UTC 2012
On Mon, Feb 6, 2012 at 5:35 PM, Bernhard Schmidt <bschmidt at freebsd.org> wrote:
> On Monday 06 February 2012 15:32:42 Merlin Corey wrote:
>> Like some a year before me, from a thread two years before me (
>> http://forums.freebsd.org/showthread.php?t=10042 ), I am interested in
>> making my (pun intended) penultimate pen-testing netbook on my
>> favorite operating system, FreeBSD; alas, I am not able to make use of
>> the atheros card in said netbook for the purposes of injection.
>> It is perhaps worth nothing that I started this project on FreeBSD
>> 8.x, but my card (AR9285 card=0x10891a3b chip=0x002b168c rev=0x01 hdr=
>> 0x00) was only working at what seemed half power and would constantly
>> take itself up/down. I have since updated the system to 9.0-RELEASE
>> and experienced what appeared to be fully functioning wireless until
>> In the thread linked above, there is a mention of a kernel patch which
>> allows writing in monitor mode - I desperately applied this patch
>> after finding that the instructions to patch aircrack itself seem to
>> have already been applied either in ports or upstream.
>> Now, I can run airodump just fine, but when I try to do injection test
>> with aireplay in either ahdemo or monitor mode, I simply end up with a
>> bunch of "wi_write(): Input/output error" messages.
>> I am not really sure how to proceed in further debugging this issue;
>> should I turn wlandebug on, and if so, which bit is best, or should I
>> just throw them all? Perhaps something else entirely?
>> Is this maybe a problem with my card itself?
>> Any push in the right direction would be greatly appreciated.
> Can you set a channel and ssid before starting any kind of injection? Something like
> ifconfig wlan0 create wlandev ath0 wlanmode ahdemo
> ifconfig wlan0 channel 1 ssid foobar up
Yes, apologies for not being clear about my methods. I have tested
both with setting the initial channel and ssid before attempting to
inject as well as not.
> If I remember correctly, the interface will otherwise scan indefinitely trying to find an open network to connect to. Setting a channel/ssid will ensure that the interface moves into RUN state (you can verify that with wlandebug +state) which should allow injection. Trying to do so while in eg. SCAN state is really too racy due to all the channel changes going on.
You might be surprised to learn that in the case of NOT setting the
channel it successfully finds APs on each channel and attempts
injection, but fails with a write error every time.
Thank you for wladebug +state, I will test this in a little bit to see
if it is indeed stuck in the SCAN state instead of the RUN state.
> Basically, injection is a real mess currently and neither monitor nor ahdemo mode are really that well suited for that purpose. Monitor mode is designed to be totally mute while ahdemo is adhoc mode without mgmt frames but a lot of unnecessary logic behind it. Guess we should really think about a new mode specially designed to handle those needs, or re-enable injection in monitor mode which would break it's initial purpose.. thoughts?
Regarding re-enabling write in monitor mode, I have lready done this,
but it does not seem to have solved the problem, as I still receive an
input/output error (as opposed to permission denied, which the thread
indicates I will receive in monitor mode if I do not have the ability
I am all for a new mode and willing to test it from CURRENT or
whatever I may do to help it along.
More information about the freebsd-wireless