search

bktruss / fern-wifi-cracker

Automatically exported from code.google.com/p/fern-wifi-cracker
0 stars 0 forks source link

fern-wifi-cracker deathentication, no action. #64

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.open fern-wifi-cracker,
2.select target network and password list,
3.deauthentication hangs.

What is the expected output? What do you see instead?
deauthentication started,working, wait, etc.
instead I see no action taking place, even after a few mins.

What version of the product are you using? On what operating system?
Im using ver. pre-installed on backtrack 5 r3 with no updates..cause i cant:(
Windows 7 home premium 64; backtrack 5 r3 Live usb.

Please provide any additional information below.

 I am running Backtrack 5 r3 on live usb. air-suite works fine but when i use fern wifi cracker against wpa, after i select my passwords list (its a .txt file),it hangs in the deauthentication phase. is it normal to take a while at this point or no...?

im booting from usb
cant connect to internet through backtrack, even though i can through windows 7,
so i cant update via 'apt-get'
and packet injection working...

any thoughts...?anyone?

Fedaru

Original issue reported on code.google.com by gundam.0...@gmail.com on 6 Apr 2013 at 9:24

GoogleCodeExporter commented 9 years ago 
could it be the 'password list' file type (.txt) is unaccepted in a linux OS? 
If so then what format should it be, and how to get it into Backtrack to use 
from windows, since i cant connect to internet from backtrack and download, or 
update for that matter?

Original comment by gundam.0...@gmail.com on 6 Apr 2013 at 9:28

GoogleCodeExporter commented 9 years ago 
Feels like the project is a bit dead. I experience the same problem. I start 
the attack , select the common.txt, then it infinitely hangs there without any 
feedback

Original comment by diegogu...@gmail.com on 3 Jun 2013 at 1:40

GoogleCodeExporter commented 9 years ago 
In that phase the program hasn't hanged, it either hasn't detected connected 
clients or is de-authenticating clients to obtain a handshake, which is 
necessary for the brute-forcing stage.. The project is also still active.

Original comment by savioboy...@gmail.com on 4 Jun 2013 at 4:14

GoogleCodeExporter commented 9 years ago 
I am experiencing the same problem - program hangs forever at the DEAUTH stage. 
"Forever" here means at least 12 hours - no progress, no updates - just trying 
to deauth the same MAC.
Tried it on Kali Linux 1.0.3 on 3 different notebooks, with Atheros / Intel 
based cards.
Any ideas ? Is there a way to see a logfile or an actual terminal window with 
aircrack ?

Original comment by valen...@gmail.com on 23 Jun 2013 at 4:39

GoogleCodeExporter commented 9 years ago 
This thread has been dead for a minute, but I'll throw this out there anyway.  
Savio, or anybody for that matter, what kind of times do you see with 
deauthentication?  Best time?  Worst time?  Just curious.  I understand what 
the process is attempting to accomplish and I understand that different devices 
will react differently, but I was just curious on ballpark time frames for that 
successful handshake.  Thanks in advance.

Original comment by jamcdan...@gmail.com on 1 Jan 2015 at 10:10