Jump to content

Marco Rossi

Active Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by Marco Rossi

  1. First command can't associate: reaver -i mon0 -b A0:F3:C1:B1:3A:62 -e "myAP" -c 4 Output: [+] Waiting for beacon from A0:F3:C1:B1:3A:62 [!] WARNING: Failed to associate with A0:F3:C1:B1:3A:62 (ESSID: myAP) With -A pine can associate but never sends a pin reaver -i mon0 -A -b A0:F3:C1:B1:3A:62 -e "myAP" -c 4 Output: [+] Waiting for beacon from A0:F3:C1:B1:3A:62 [+] Associated with A0:F3:C1:B1:3A:62 (ESSID: myAP) [+] Starting Cracking Session. Pin count: 0, Max pin attempts: 11000 [+] 0.00% complete. Elapsed time: 0d0h12m15s. [+] 0.00% complete. Elapsed time: 0d0h22m23s. With -vv (-vvv has no effect): [+] Trying pin 12345670. [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred Checked a bunch of other ap's and I always get the same results. I'm in the same room but even if I go to another room it fails. Never changed txpower. My AP: 25-39dBm, quality lvl 100%
  2. Same here and still doesn't work. Tried internal / sd install. Disabled wlan1 (before starting mon mode / after mon mode but before starting reaver) Terminal or browser, it doesn't matter. Have not installed anything other than reaver, bully and wps infusion. Any idea?
  3. After another reset I installed reaver and bully on the sd card but either cannot associate or never sends a pin. mkdir /etc/reaver opkg update opkg -d sd install reaver ln -s /sd/etc/reaver/reaver.db /etc/reaver/ ln -s /sd/usr/bin/reaver /usr/bin/ ln -s /sd/usr/bin/wash /usr/bin/
  4. Wash and bully work with the disabled wlan1 tough I have to prevent wps lockout somehow. root@WIN7B2:~# bully mon0 -b A0:F3:B2:E4:3A:62 -e "myAP" -c 4 [!] Bully v1.0-22 - WPS vulnerability assessment utility [+] Switching interface 'mon0' to channel '4' [!] Using '00:15:25:94:44:11' for the source MAC address [+] Datalink type set to '127', radiotap headers present [+] Scanning for beacon from 'a0:f3:b2:e4:3a:62' on channel '4' [+] Got beacon for 'myAP' (a0:f3:b2:e4:3a:62) [+] Loading randomized pins from '/root/.bully/pins' [+] Index of starting pin number is '0000000' [+] Last State = 'NoAssoc' Next pin '44421090' [+] Rx( M5 ) = 'Pin1Bad' Next pin '50901098' [+] Rx( Auth ) = 'Timeout' Next pin '50901098' [+] Rx( Assn ) = 'Timeout' Next pin '50901098' [+] Rx( Auth ) = 'Timeout' Next pin '50901098' [+] Rx( Assn ) = 'Timeout' Next pin '50901098' [+] Rx( Assn ) = 'Timeout' Next pin '50901098' [!] Received M2D or out of sequence WPS Message [+] Rx( M5 ) = 'WPSFail' Next pin '50901098' [+] Rx( Auth ) = 'Timeout' Next pin '50901098' [+] Rx( Assn ) = 'Timeout' Next pin '50901098' [+] Rx( Assn ) = 'Timeout' Next pin '50901098' [+] Rx( M5 ) = 'Pin1Bad' Next pin '10541098' [+] Rx( Auth ) = 'Timeout' Next pin '10541098' [+] Sent packet not acknowledged after 3 attempts [+] Tx( Auth ) = 'Timeout' Next pin '10541098' [+] Rx( Assn ) = 'Timeout' Next pin '10541098' [+] Rx( Assn ) = 'Timeout' Next pin '10541098' [+] Rx( Auth ) = 'Timeout' Next pin '10541098' [+] Rx( M5 ) = 'Pin1Bad' Next pin '11481096' [+] Rx( Auth ) = 'Timeout' Next pin '11481096' [+] Rx( Assn ) = 'Timeout' Next pin '11481096' [+] Rx( M5 ) = 'Pin1Bad' Next pin '85851092' [!] WPS lockout reported, sleeping for 43 seconds ... [!] WPS lockout reported, sleeping for 43 seconds ... Current Disk Usage: Filesystem Size Used Available Use% Mounted on rootfs 3.2M 740.0K 2.5M 23% / /dev/root 11.8M 11.8M 0 100% /rom tmpfs 30.2M 124.0K 30.1M 0% /tmp tmpfs 512.0K 0 512.0K 0% /dev /dev/mtdblock3 3.2M 740.0K 2.5M 23% /overlay overlayfs:/overlay 3.2M 740.0K 2.5M 23% / /dev/sdcard/sd1 2.8G 106.0M 2.5G 4% /sd Current Memory Usage: total used free shared buffers Mem: 61804 43664 18140 0 6152 -/+ buffers: 37512 24292 Swap: 1000132 0 1000132 Here is my disk usage. Unfortunately reaver still gives me the same errors as before. Thanks for the help.
  5. Thanks for the quick reply. I'm gonna try as soon as I get home. What I can tell you now is that I have not installed anything other than wps infusion, reaver, bully so there should be enough space in internal but Im gonna check this too.
  6. I'm gonna try. 1. Reflash the firmware / format the sd card. 2. Install wps, reaver, bully (everything internal) 3. Start monitor mode on wlan1. 4. Scan works fine I find my ap and a bunch of others with wps but reaver can't even associate. wps log_1438129108.log [July 29 2015 00:18:52] [+] Waiting for beacon from A0:F3:B2:E4:3A:62 [!] WARNING: Failed to associate with A0:F3:B2:E4:3A:62 (ESSID: myAP) [!] WARNING: Failed to associate with A0:F3:B2:E4:3A:62 (ESSID: myAP) With the second option of the advanced menu (Do not associate with the AP...) my pine can associate but never sends a pin. [+] Waiting for beacon from A0:F3:B2:E4:3A:62 [+] Associated with A0:F3:B2:E4:3A:62 (ESSID: myAP) [+] Starting Cracking Session. Pin count: 0, Max pin attempts: 11000 Just hangs forever and I get the exact same results via terminal. Wash doesn't work either. It's just can't find anything. Finally bully: root@pine:~# bully mon0 -B -b A0:F3:B2:E4:3A:62 -e "myAP" -c 4 [!] Bully v1.0-22 - WPS vulnerability assessment utility [+] Switching interface 'mon0' to channel '4' [!] ioctl(SIOCSIWFREQ) on 'mon0' failed with '-1' [X] Unable to set channel on 'mon0', exiting Every piece of advice is appreciated.
×
×
  • Create New...