EvilZone
Hacking and Security => Hacking and Security => : sanju4883 May 26, 2012, 06:20:24 PM
-
While Cracking WPA or WPA2 password of wifi on backtrack, then WPA Handshake could not be done or establish.. any Help please... !!!
I have also getting problem og <Hidden> Essid... help me please..
-
Make sure you set the channel on the monitor interface. If not the channel hopping can cause you to lose parts of the handshake.
Make sure airodump-ng is capturing all packets not just ivs
To find a hidden ssid deauth a client associated with the AP. Not sure how to discover without an associated client.
edit: what are you using to crack the handshake?
-
Make sure you set the channel on the monitor interface. If not the channel hopping can cause you to lose parts of the handshake.
Make sure airodump-ng is capturing all packets not just ivs
To find a hidden ssid deauth a client associated with the AP. Not sure how to discover without an associated client.
edit: what are you using to crack the handshake?
------------------
The following command i am using to crack WPA...
(((TB = target BSSID, TC = Target channel, CM = station))))
airmon-ng
airmon-ng start wlan0
airodump-ng mon0
airodump-ng -w wep --bssid TB -c TC mon0
aireplay-ng --deauth 1 -a TB -c CM mon0
etc.......
-
Shouldn't mon0 be the wlan0?
-
------------------
The following command i am using to crack WPA...
(((TB = target BSSID, TC = Target channel, CM = station))))
airmon-ng
airmon-ng start wlan0
airodump-ng mon0
airodump-ng -w wep --bssid TB -c TC mon0
aireplay-ng --deauth 1 -a TB -c CM mon0
etc.......
I would use 'airmon-ng start wlan0 TC'
I don't think that setting the channel in airodump-ng will keep the interface from channel hopping
Does airodump-ng confirm that it has detected a WPA handshake? I ask because for me airodump-ng would say that everything was captured correctly. But when attempting to crack pyrit was coming back saying that the capture file did not include a complete handshake. Drove me crazy until I found a patch for it. To make sure everything was working correctly I used a spare laptop to manually connect to my own WAP to ensure I had a valid handshake, once I made that work I moved on.
-
I would use 'airmon-ng start wlan0 TC'
I don't think that setting the channel in airodump-ng will keep the interface from channel hopping
Does airodump-ng confirm that it has detected a WPA handshake? I ask because for me airodump-ng would say that everything was captured correctly. But when attempting to crack pyrit was coming back saying that the capture file did not include a complete handshake. Drove me crazy until I found a patch for it. To make sure everything was working correctly I used a spare laptop to manually connect to my own WAP to ensure I had a valid handshake, once I made that work I moved on.
================================
thanks dude.. i am getting little bit you.. can u share terminal CODE here.. means by TC.. should i get type the Target channel.. so i think i have to first scan it.....???
-
Shouldn't mon0 be the wlan0?
means i turn my wlan0 into monitor mode.. and this same is happen in Gerix wifi cracking tools in Backtrack 5
-
================================
thanks dude.. i am getting little bit you.. can u share terminal CODE here.. means by TC.. should i get type the Target channel.. so i think i have to first scan it..... ???
I've been really busy for a bit, you still interested in the term session? I don't have it saved or anything like that but I will do it again if you want
-
I've been really busy for a bit, you still interested in the term session? I don't have it saved or anything like that but I will do it again if you want
ok thanks..
-
I would use 'airmon-ng start wlan0 TC'
I don't think that setting the channel in airodump-ng will keep the interface from channel hopping
Does airodump-ng confirm that it has detected a WPA handshake? I ask because for me airodump-ng would say that everything was captured correctly. But when attempting to crack pyrit was coming back saying that the capture file did not include a complete handshake. Drove me crazy until I found a patch for it. To make sure everything was working correctly I used a spare laptop to manually connect to my own WAP to ensure I had a valid handshake, once I made that work I moved on.
SO on which TC (Channel) i should set mon0, only the target channel or any other else?
-
I would suggest for capturing only the target channel because you want just the packets on that channel by victim AP and of course the clients who wants to connect to the AP.