Usually this is due to insufficient ram, but given that you are running commands and causing the system to lock I suspect you have the wrong drivers loaded for your network cards, and this is causing a kernel panic.
first of all i must say i am a german linux noob
first of all i've got wlan to work fine
but if i try injection with
aireplay-ng -1 0 -a ...[bssid]... -h ...[mac]... -e [essid] wlan0
i got the message
waiting for beacon frame (BSSID: ....) on channel 11
and the system freezes
so my question is what is wrong there?
i also tried this
h t t p ://trac.aircrack-ng.org/ticket/558
but still the same problem
any ideas?
ok... update...
notebook: asus x56t
Network controller: Atheros AR928X (rev 01)
the errormessage after launching aireplay
any ideas how to fix this?Kernel panic - not syncing: Fatal exception in interrupt
edit2
screenshot can be found here
h t t p ://img15.imageshack.us/img15/1876/snc00035.jpg
Usually this is due to insufficient ram, but given that you are running commands and causing the system to lock I suspect you have the wrong drivers loaded for your network cards, and this is causing a kernel panic.
So the problem is just the version of ath9k in the kernel. you can download the newest version from http://wireless.kernel.org/en/users/Download and you'll be good to go. But as far as the panic, I don't know...until I got the new ath9k my system would just freeze as you described initially.
BT4 always locks up when I try aireplay-ng's injection test, and I'm using a card with an Atheros 802.11n chipset and the ath9k driver. The driver seems otherwise perfectly stable, however.
Are there patches I haven't heard about? I thought the ath9k driver wasn't injecting yet.
http://www.aircrack-ng.org/doku.php?...rev=1235153705
---
Useful HowTo Threads <-- Why do people think I'm joking when I link this?
ok, i updated the driver but with the interface wlan0 the injection was still impossible (without freezing, it just didnt work)
the with the mon0 interface, which airmon creats the injection works
so i think updating the driver fixed the problem for me
Good point, you must use the mon0 interface. (jb64, are you testing after airmon-ng start? and then on mon0?)
As for updates to ath9k, there is a very active (maybe small, but active) development effort, you can signup for email updates here: https://lists.ath9k.org/mailman/listinfo/ath9k-devel
most of it is way over my head, but I'm sure some people here will be able to appreciate more of it.
so i am using the 1000he and going off of xploitz wep cracking guide video, and i still freeze. what commands should i replace mon0 from wlan0 to stop freezing?
solid.
i was wondering why when i went into monitor mode with my aspire one d250, my network connection on wlan0 dropped and apparently wouldn't support a concurrent connection while mon0+ were active. i'd also get a kernel panic when i had multiple monitor interfaces gathering packets and injecting.
after the update with the linux wireless drivers, my ath9k works GREAT and doesn't drop connection with wlan0 while mon0+ are active AND injects great too.
great success of using the search function! high five!