How do I get rt73usb doing injection?

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4646

Dunkirk

03-03-2008 21:09:15

I've been chasing my tail for a week now, and I just keep going in circles. I've Googled till I'm blue in the face, and read everything I can get my hands on, and I'm still confused. I guess I need someone knowledgeable to simply tell me what I need to do.

1) Does the rt73usb driver that comes _with_ the 2.6.24.x kernel support injection, or do I need to somehow compile the rt2x00 snapshots available on the site? Are the drivers here the only ones patched for injection, or are the kernel sources "injection ready?"

2) Whether I have the proper (patched) driver in the kernel by default or I need to compile it, how do I get it actually _doing_ injection? I see a reference to a "mon0" interface. Is this what I should be using, or am I all wet?

3) Once injection is _supported_ and _activated_ (on either driver), can I use the stock aircrack-9.x series programs to perform the injection, or do I need to be using the 1.0-beta series? (Put another way does the "released" series support the new radiotap "method" of doing injection?)

I'm sorry to be so blunt and so ignorant, but I've done my level best to educate myself, and I'm just not finding this sort of information anywhere. Thanks for any hints, clues, pointers, or outright explanations you can provide!

IvD

03-03-2008 22:15:48

For the driver the version in 2.6.24 would be sufficient,
but like I said earlier it all depends on mac80211.

Another user on this forum reported that mac80211 supports it, but I seriously do not know which versions have injection enabled, and in which kernel that version would be. Neither do I know what software versions you are going to need for it.

echosix

23-03-2008 21:05:06

like I said earlier it all depends on mac80211.[/quote3hnailjv]The guys at remote-exploit.org have got it to work both on BT2 and BT3 beta.

I've tried cvs enhanced legacy drivers on 2.6.24-gentoo-r3 kernel for both rt2570 and rt73 and have been unable to get injection working on either -(

bofh1234

24-03-2008 17:58:46

Don't bother using serialmonkeys drivers for injection. I have spent almost 2 weeks trying to get 2.6.24.3 and 2.6.25-rc4, rc5, and rc6 to work with aircrack-ng beta 2 rev 100x and the results are disturbing to say the least.

I have a EdiMax usb wireless card that uses the rt73 driver. So I download 2.6.24.3 to try the new rt73 driver and it didn't work. After a little configuration (installing firmware) the interface came up but everything was slow. And no packet injection. So I read the linux-wireless mail list and see that a slightly updated driver is in 2.6.25-rcx so I try it. Slight faster but still not usable, and a hair more reliable, the interface doesn't stop responding after a few minutes of use. Still no packet injection. I go back to list and see that 2.1.4 is going to be in 2.6.26. Great I have to wait another kernel release (4 or 5 months at the very least) before I can get a decent driver. This morning I see a LED thread on linux-wireless and how support won't be in until 2.6.27, although LEDs aren't really important to me.

So I get over this, use the 2.6.25-rc6 kernel and aircrack-ng beta 2 rev 1009 and aircrack can't use the serialmonkey driver. Two weeks to figure this out. I ended up going back to using ASPj's driver from http//homepages.tu-darmstadt.de/~p_larbig/wlan/
but that driver isn't compatible with 2.6.24 or better. ASPj is working on it, but no ETA.

The other question I have is the ASPj driver doesn't appear to need a firmware like the serialmonkey driver. Why?

IvD

24-03-2008 18:18:15


I have a EdiMax usb wireless card that uses the rt73 driver. So I download 2.6.24.3 to try the new rt73 driver and it didn't work. After a little configuration (installing firmware) the interface came up but everything was slow. And no packet injection. So I read the linux-wireless mail list and see that a slightly updated driver is in 2.6.25-rcx so I try it. Slight faster but still not usable, and a hair more reliable, the interface doesn't stop responding after a few minutes of use. Still no packet injection. I go back to list and see that 2.1.4 is going to be in 2.6.26. Great I have to wait another kernel release (4 or 5 months at the very least) before I can get a decent driver.
[/quotezbdupjc3]

Check the linuxwireless website... There is a wireless-compat package that brings the latest mac80211 and latest driver versions to older kernels....
On the linux-wireless list that package has been discussed quite often, so undoubtly you will have seen the threads about it.


This morning I see a LED thread on linux-wireless and how support won't be in until 2.6.27, although LEDs aren't really important to me.
[/quotezbdupjc3]

1) I miss your point about bringing LED support into this discussion
2) please READ the mail before complaining about the LED support


So I get over this, use the 2.6.25-rc6 kernel and aircrack-ng beta 2 rev 1009 and aircrack can't use the serialmonkey driver. Two weeks to figure this out. I ended up going back to using ASPj's driver from http//homepages.tu-darmstadt.de/~p_larbig/wlan/
but that driver isn't compatible with 2.6.24 or better. ASPj is working on it, but no ETA.
[/quotezbdupjc3]

I still wonder what the benefit is for having 2 projects for the same driver and why the 2 projects cannot simply be merged....


The other question I have is the ASPj driver doesn't appear to need a firmware like the serialmonkey driver. Why?[/quotezbdupjc3]

Because the firmware is most likely compiled into the driver, which is a method which is considered a "Bad Thing" for Linux kernel drivers.

bofh1234

24-03-2008 21:47:55


Check the linuxwireless website... There is a wireless-compat package that brings the latest mac80211 and latest driver versions to older kernels....
On the linux-wireless list that package has been discussed quite often, so undoubtly you will have seen the threads about it.
[/quotene9kdvyt]

I have tried the wireless-compat package. The first time I tried (a couple weeks ago) it wouldn't compile. I waited a couple of days and next time I tried it compiled, but still no injection and aircrack keeps complaining about missing sysfs stuff or it can't find iw.


1) I miss your point about bringing LED support into this discussion
2) please READ the mail before complaining about the LED support
[/quotene9kdvyt]

Your right I shouldn't have brought this up. I apologize.


I still wonder what the benefit is for having 2 projects for the same driver and why the 2 projects cannot simply be merged....
[/quotene9kdvyt]

At this point we a working ASPj driver and a not so working serialmonkey driver. Please don't take offense but that is just the current state of the two drivers.


Because the firmware is most likely compiled into the driver, which is a method which is considered a "Bad Thing" for Linux kernel drivers.[/quotene9kdvyt]

OK. Thanks for the information,

Thanks,

IvD

24-03-2008 22:15:11



I still wonder what the benefit is for having 2 projects for the same driver and why the 2 projects cannot simply be merged....
[/quote2xak55o1][/quote2xak55o1]

At this point we a working ASPj driver and a not so working serialmonkey driver. Please don't take offense but that is just the current state of the two drivers.
/quote]

Well I accept the fact that the behavior between the 2 drivers is different. My point is something I should contact the author of that driver about, because having a single project for a driver just is easier for everybody. ;)