Please note: This project is no longer active. The website is kept online for historic purposes only.
If you´re looking for a Linux driver for your Atheros WLAN device, you should continue here .

Ticket #1930 (new defect)

Opened 10 years ago

Last modified 10 years ago

Sent 0 packets

Reported by: michaelraywilson@gmail.com Assigned to:
Priority: trivial Milestone:
Component: madwifi: tools Version: v0.9.4
Keywords: Cc:
Patch is attached: 0 Pending:

Description (Last modified by mrenzmann)

When trying to use the aireplay tool to do a arp-request replay it says "sent 0 packtes". The first time I tried to use this machine and nic to do this it worked successfully, but I can't get it to inject anymore.

Note: aireplay -9 says injection is working I am using airmon-ng start ath0 to start the card in monitor mode I have tried wlanconfig ath0 destroy/create wlandev wifi0 wlanmode monitor

Please let me know if there is something that I am missing.

lspci output:

04:00.0 Ethernet controller: Atheros Communications, Inc. AR2413 802.11bg NIC (rev 01)

dmesg:

ath_hal: module license 'Proprietary' taints kernel.
ath_hal: 0.10.2.2-ATHEROS (AR5210, AR5211, AR5212, AR5416, RF5111, RF5112, RF2413, RF5413, RF2133, RF2425)
wlan: 0.8.4.2 (svn r2834)
ath_pci: 0.9.4.5 (svn r2834)

Please let me know if you need the output of any other commands.

Thank you

Change History

(follow-up: ↓ 2 ) 05/07/08 06:42:12 changed by mrenzmann

  • description changed.

What exactly makes you believe that this issue is caused by MadWifi?

You say that aireplay worked the first time you used it - what has changed since then? Did you switch to a different version of MadWifi? Or did you change the setup? Or ...?

(in reply to: ↑ 1 ) 05/07/08 06:50:58 changed by michaelraywilson@gmail.com

Replying to mrenzmann:

I have discovered just recently that I can only use the arp replay on that one AP that I cracked the first time. It doesn't have to do with the channel of that AP since I tried other WEP's on that same channel.

I am using the exact same process to create the interface with airmon-ng with the following syntax:

airmon-ng start wifi0 6 (where 6 is the channel of the attack)

Please let me know if it is not the driver. I dont know why I would be able to inject arp at one ap and none other...

What exactly makes you believe that this issue is caused by MadWifi? You say that aireplay worked the first time you used it - what has changed since then? Did you switch to a different version of MadWifi? Or did you change the setup? Or ...?