I think the reason I wasn't finding any AP's earlier when I did the test command was because I was on the wrong channel. Regardless, when I run the following command, I receive confirmation that my card can inject.
This is what my AP pings as:
aireplay-ng -9 ath0
So then I start up airodump-ng with the following command:
Ping (min/avg/max): 4.542ms/70.745m/95.948ms Power:50.5
Once that's started, I run the aireplay-ng command with the following attributes:
airodump-ng -c 1 --bssid (my AP's ssid) -w default ath0
Once I run that, I get a bunch of lines that looks like it's doing a lot. In Xploitz video, his terminal appears to show only one line, and the line just keeps updating. My screen gets flooded with lines. Here's an exact line from the last run I did:
aireplay-ng -3 -b (mac address of ap) -h (my ath0 mac address) ath0
So I look back at my other console, the one with airodump-ng running, and I see the following stats. PWR, depending on where I am, is about 60ish. Beacons seem to go up rather quickly. My #Data seems to jump at first, and #/s looks to be about 300 at first, but quickly falls. Usually, it hits 0 in a few seconds, and my #Data slows down around 1300ish. The CH is correct, the MB speed and ENC are correct, and the ESSID reads correct.
Read 72129 packets (got 260 ARP requests and 23405 ACKs), sent 46719 packets...(500 pps)
I've tried pinging a non-existing machine on my network from another computer to see if it helps, and it seems to have no effect. In addition, all the computers in my house seem to lose connection quite a bit while I'm running packet injection - is that normal?
Also, I ran the same test on another laptop, this one with an intel3954 a/b/g card, and I had the same results.