I'm testing my home network's security, and no matter what I try,
sudo airmon-ng start wlp3s3
Found 2 processes that could cause trouble. If airodump-ng, aireplay-ng or airtun-ng stops working after a short period of time, you may want to kill (some of) them! PID Name 2619 wpa_supplicant 2697 dhcpcd Process with PID 2619 (wpa_supplicant) is running on interface wlp3s3 Process with PID 2697 (dhcpcd) is running on interface wlp3s3 Interface Chipset Driver wlp3s3 Intel 2200BG ipw2200 - [phy0] (monitor mode enabled on mon0) mon0: ERROR while getting interface flags: No such device
lo no wireless extensions. eth0 no wireless extensions. wlp3s3 IEEE 802.11abg ESSID:"wilrout" Mode:Managed Frequency:2.457 GHz Access Point: 00:18:E7:E2:D4:72 Bit Rate:48 Mb/s Tx-Power=20 dBm Sensitivity=8/0 Retry limit:7 RTS thr:off Fragment thr:off Power Management:off Link Quality=72/100 Signal level=-56 dBm Noise level=-88 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:9
TELL me how to fix it and I'll be back in a week, same problem.
TEACH me how to fix it, and I'll be good from then on.
Oh, and WHY the fix works would also be appreciated.
Not all wireless cards can handle packet injection, which will be needed when using the aircrack-ng suite.
Two things stand out:
It appears that you are using your internal wireless card,(Intel 2200BG chipset) which may not support packet injection. Some chipsets won't work at all, some can be patched.
Simple fix: grab a wireless card (usb) from ebay that is known to work. My favorite is the netgear WG111v2, about $10.00 U.S.
It seems you are connected to the internet:
wlp3s3 IEEE 802.11abg ESSID:"wilrout"
Mode:Managed Frequency:2.457 GHz Access Point: 00:18:E7:E2:D4:72
You don't want to be connected for this.
The best place to start for you would be http://www.aircrack-ng.org/documentation.html
You can check your chipset and find any patches you may need, as well as follow their tutorials.
You tube also has a lot of video tutorials.
Edit: this may be of interest, note the "mon0: ERROR while getting interface flags: No such device" errors.
Last edited by rfk1ll (2013-02-17 07:24:10)