|
|
08-21-2012
, 05:17 AM
|
|
|
Posts: 135 |
Thanked: 292 times |
Joined on Aug 2012
@ Burgas, Bulgaria
|
#741
|
|
|
08-21-2012
, 11:11 AM
|
|
|
Posts: 3,837 |
Thanked: 5,594 times |
Joined on Mar 2011
|
#742
|
|
|
08-21-2012
, 11:17 AM
|
|
Posts: 822 |
Thanked: 1,043 times |
Joined on Feb 2011
@ The Netherlands
|
#743
|
mon0 is coming from wlan0 , thus when locking the master device will lock mon0 too.
and you have fully working injection on mon0? Just exit monitor mode and you will be able to connect
But why you should want to alter wlan0 and/or connect to ap when you have entered monitor mode?
| The Following User Says Thank You to mr_pingu For This Useful Post: | ||
|
|
08-21-2012
, 11:30 AM
|
|
Posts: 822 |
Thanked: 1,043 times |
Joined on Feb 2011
@ The Netherlands
|
#744
|
Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 down Nokia-N900:/home/user/MyDocs/MyScripts# iwconfig wlan0 mode monitor Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 up Nokia-N900:/home/user/MyDocs/MyScripts# aireplay-ng -9 wlan0 17:26:00 Trying broadcast probe requests... 17:26:01 No Answer... 17:26:01 Found 2 APs 17:26:01 Trying directed probe requests... 17:26:01 00:11:22:33:44:55 - channel: 11 - 'ESSID' 17:26:02 Ping (min/avg/max): 1.373ms/14.998ms/49.805ms Power: -90.72 17:26:02 29/30: 96% 17:26:02 Injection is working! 17:26:02 00:12:34:56:78:90 - channel: 11 - '' 17:26:03 Ping (min/avg/max): 2.014ms/13.966ms/67.474ms Power: -38.47 17:26:03 30/30: 100% Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 down Nokia-N900:/home/user/MyDocs/MyScripts# iwconfig wlan0 mode managed Nokia-N900:/home/user/MyDocs/MyScripts# ifconfig wlan0 up Nokia-N900:/home/user/MyDocs/MyScripts# airmon-ng start wlan0 Process with PID 7010 (udhcpc) is running on interface wlan0 Interface Chipset Driver wlan0 TI WL1251 wl12xx - [phy0] (monitor mode enabled on mon0) Nokia-N900:/home/user/MyDocs/MyScripts# aireplay-ng -9 mon0 17:28:32 Trying broadcast probe requests... 17:28:34 No Answer... 17:28:34 Found 2 APs 17:28:34 Trying directed probe requests... 17:28:34 00:12:34:56:78:90 - channel: 11 - '' 17:28:34 Ping (min/avg/max): 1.495ms/10.259ms/38.635ms Power: -43.38 17:28:34 29/30: 96% 17:28:34 Injection is working! 17:28:34 00:11:22:33:44:55 - channel: 11 - 'ESSID' 17:28:40 0/30: 0%
| The Following User Says Thank You to mr_pingu For This Useful Post: | ||
|
|
08-21-2012
, 11:53 AM
|
|
|
Posts: 135 |
Thanked: 292 times |
Joined on Aug 2012
@ Burgas, Bulgaria
|
#745
|
|
|
08-21-2012
, 11:56 AM
|
|
|
Posts: 1,565 |
Thanked: 1,873 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#746
|
I am really interested in this and I like coding but there are 2 clevenHelper.sh files one in /opt/cleven and the other in /home/opt/cleven which one should I edit?
|
|
08-21-2012
, 11:57 AM
|
|
|
Posts: 1,565 |
Thanked: 1,873 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#747
|
|
|
08-21-2012
, 12:07 PM
|
|
|
Posts: 135 |
Thanked: 292 times |
Joined on Aug 2012
@ Burgas, Bulgaria
|
#748
|
Actually /home/opt and /opt are pointing to the same location. That is, it is the same file you just look at it from different links.
| The Following User Says Thank You to tanago For This Useful Post: | ||
|
|
08-21-2012
, 12:08 PM
|
|
|
Posts: 1,565 |
Thanked: 1,873 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#749
|
I think I've found small glitch in Cleven's reaver implementation.
Using current command to invoke Cleven, after successful cracking of PIN, reaver x-term window just closes - without giving chance to actually verify found PIN or retrieved WPA PSK.
I've just checked it during real-test on my router, and reaver.db file *doesn't* keep retrieved WPA password (at least, using reaver from repositories, aka latest, compiled by Pali). Retrieved data is shown *only* on x-term window with cracking progress.
reaver have argument "-o" for providing output to file, but it prevents any info from appearing inside opened x-term window, where reaver is "working". Furthermore, using static path for -o, would result in further cracking attempts overwriting former ones.
IMO, it would be good idea to create new directory under /home/user/.cleven/keys, called - for example - wps (/home/user/.cleven/keys/wps). Then, some code in clevenHelper would read reaver's output, and react on "success" pattern, saving it (only relevant part, as whole log would be loooong) as retrieved WPS PIN and WPA PSK, vievable from "keys" tab from Cleven GUI.
What do you think, Saturn?
/Estel
| The Following User Says Thank You to Saturn For This Useful Post: | ||
|
|
08-21-2012
, 12:17 PM
|
|
Posts: 43 |
Thanked: 16 times |
Joined on Mar 2010
|
#750
|
I think I've found small glitch in Cleven's reaver implementation.
Using current command to invoke Cleven, after successful cracking of PIN, reaver x-term window just closes - without giving chance to actually verify found PIN or retrieved WPA PSK.
I've just checked it during real-test on my router, and reaver.db file *doesn't* keep retrieved WPA password (at least, using reaver from repositories, aka latest, compiled by Pali). Retrieved data is shown *only* on x-term window with cracking progress.
reaver have argument "-o" for providing output to file, but it prevents any info from appearing inside opened x-term window, where reaver is "working". Furthermore, using static path for -o, would result in further cracking attempts overwriting former ones.
IMO, it would be good idea to create new directory under /home/user/.cleven/keys, called - for example - wps (/home/user/.cleven/keys/wps). Then, some code in clevenHelper would read reaver's output, and react on "success" pattern, saving it (only relevant part, as whole log would be loooong) as retrieved WPS PIN and WPA PSK, vievable from "keys" tab from Cleven GUI.
What do you think, Saturn?
/Estel
![]() |
| Tags |
| aircrack, cleven, reaver |
| Thread Tools | Search this Thread |
|