Bob_
-
Posts
6 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Bob_
-
-
ifconfig wlan0 down
airmon--ng start wlan0
wash -i mon0
Returns nothing
Using wash -i mon0 -C (Same with wash -i mon0 -C -s)
Returns [!] Found packet with bad FCS, skipping... (More than once)
I had the exact same problem, here's what i did to fix this. I made sure wlan1 (try wlan1 for this, btw) was unchecked in the web interface and wasn't connected to anything (because im a newb
). Went into ssh and made sure the adapter still showed in ifconfig (when it didn't show, i rebooted, this fixed it). Then i proceeded as normal with airmon-ng start wlan1, it seemed to work from there with no bad FCS messages. (as seen below)For some reason when i put the BSSID into Reaver it doesn't associate, what causes this (or better yet what are some fixes)?
root@Pineapple:~# bash root@Pineapple:~# airmon-ng start wlan1 Interface Chipset Driver wlan1 Realtek RTL8187L rtl8187 - [phy1] (monitor mode enabled on mon0) wlan0-1 Atheros AR9330 ath9k - [phy0] IEEE Unknown Unknown (MONITOR MODE NOT SUPPORTED) 802.11bgn Unknown Unknown (MONITOR MODE NOT SUPPORTED) Mode:Master Unknown Unknown (MONITOR MODE NOT SUPPORTED) Tx-Power=12 Unknown Unknown (MONITOR MODE NOT SUPPORTED) dBm Unknown Unknown (MONITOR MODE NOT SUPPORTED) wlan0 Atheros AR9330 ath9k - [phy0] root@Pineapple:~# wash -i mon0 -C Wash v1.5.2 WiFi Protected Setup Scan Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com> mod by t6_x <t6_x@hotmail.com> & DataHead & Soxrok2212 & Wiire & kib0rg BSSID Channel RSSI WPS Version WPS Locked ESSID -------------------------------------------------------------------------------------- 54:BE:F7:AC:34:08 1 -54 1.0 No The Target AP 6C:B0:CE:00:DC:83 1 -65 1.0 No Other AP 00:71:C2:8F:20:70 1 -59 1.0 No Other AP 44:32:C8:C4:A7:10 1 -67 1.0 No Other AP 10:0D:7F:66:F7:9E 3 -69 1.0 No Other AP 94:10:3E:54:36:6C 5 -47 1.0 No Other AP 90:EF:68:AF:27:E9 6 -59 1.0 No Other AP 00:26:B8:F4:1A:64 7 -66 1.0 No Other AP B4:75:0E:97:01:36 11 -62 1.0 No Other AP 20:76:00:90:89:C5 11 -57 1.0 No Other AP ^C root@Pineapple:~# reaver -i mon0 -c 1 -b 54:BE:F7:AC:34:08 -vv -S Reaver v1.5.2 WiFi Protected Setup Attack Tool Copyright (c) 2011, Tactical Network Solutions, Craig Heffner <cheffner@tacnetsol.com> mod by t6_x <t6_x@hotmail.com> & DataHead & Soxrok2212 & Wiire & kib0rg [+] Switching mon0 to channel 1 [+] Waiting for beacon from 54:BE:F7:AC:34:08 [!] WARNING: Failed to associate with 54:BE:F7:AC:34:08 (ESSID: The Target AP) ^C [+] Nothing done, nothing to save.In other news, what's up with getting an infusion for this? I think i went crazy a bit messing with all this stuff, and an infusion would make this 100x easier.
-
Sounds to me like wlan1 is in use, Reaver and Wash won't work if it is.
It seems to be working after fiddling about with airmon-ng for a while. I think the bug may lay there as i re-enabled mon0 on wlan1 multiple times immediately after restart and im not exactly sure what i did to make wash print APs. Anyways, it works fine for now, thanks for the help
-
I set up and installed as the OP said, but i keep getting hangs in Reaver and Wash. More specifically wash does not show any APs and Reaver says its waiting for a beacon response. Do any packages or dependencies for pixie have incompatibilities with any infusions possibly?
). Went into ssh and made sure the adapter still showed in ifconfig (when it didn't show, i rebooted, this fixed it). Then i proceeded as normal with airmon-ng start wlan1, it seemed to work from there with no bad FCS messages. (as seen below)
[Release] pixiewps 1.1 & reaver 1.5.2
in WiFi Pineapple Mark V
Posted
Im sure not that many changes will be necessary, the syntax and everything remains the same in reaver, it would only be a few features added or removed he would have to adjust for right?