WEP fake authentication problem

[zoso10]

I recently bought a new wifi card and wanted to test it against WPA and WEP. I cracked my WPA with no trouble. I dusted off one of my old routers and set it up as WEP. I used the fake auth command:

aireplay-ng -1 0 -e 1337AP -a AP mac -h my mac rausb0

which returns the message:

23:55:17 Waiting for beacon frame (BSSID: 00:13:10:4A:6F:ED) on channel 9

23:55:17 Sending Authentication Request (Open System)

23:55:19 Sending Authentication Request (Open System)

23:55:21 Sending Authentication Request (Open System)

23:55:23 Sending Authentication Request (Open System)
……………………………………
Attack was unsuccessful. Possible reasons:

* Perhaps MAC address filtering is enabled.
* Check that the BSSID (-a option) is correct.
* Try to change the number of packets (-o option).
* The driver/card doesn’t support injection.
* This attack sometimes fails against some APs.
* The card is not on the same channel as the AP.
* You’re too far from the AP. Get closer, or lower
the transmit rate.

I went into the router settings and changed the authentication type was set to open system so I changed it to PSK. I tried the fake auth again and got the same message. I checked for all the problems it listed in the message and it's all fine. I googled and searched on the forum and found nothing. I've tried all I can think of, so if anyone can enlighten me what's wrong with the fake authentication, it would be much appreciated.

[imported_=Tron=]

You leave out one important piece of information, the make/model of your wireless card. Also perform an injection, aireplay-ng option -9, test to ensure that the card is able to inject using the current driver.

[zoso10]

Sorry, that probably would be important. Edimax EW-7318USG, I already tested injection prior and it works fine using the rt73 driver.

[secure_it]

1.Just attach dongle after properly booting UP BT3.
2.try to lower the injection rate using iwconfig rausb0 rate 1M
3.if you are using default supplied rt73 modified drivers then upgrade to latest one or downgrade to 2.01 as those default drivers have known scanning/injection bugs.

[zoso10]

Lowering the injection rate worked. I feel really stupid now because I completely forgot about trying that. Thanks secure_it for the heads up on the driver. I wondered if there were some bugs because I've had some odd things happen when scanning. Thanks for being helpful and patient.