You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CLIENT column stays empty. Even if i let wifite run for hours, and if i
connect / disconnect devices from my own access point while scanning right next
to them.
i have this problem too => https://code.google.com/p/wifite/issues/detail?id=82
maybe it have something to do with
# Do you have any idea what may have caused this bug? Guesses are helpful!
no i don't know
# What operating system are you running? Backtrack 5 R2? 32 or 64 bit?
Blackbuntu?
Raspbian (3.12.33+)
# What version of the wifite are you using?
WiFite v2 (r86)
# Please provide any additional information below. A paste of the error is
very helpful!
In Kismet and airodump-ng the clients are detected. I noticed, that kismet
finds a lot of clients for each access points, but airodump-ng only a few of
them.
I had success on my own network with this =>
http://www.aircrack-ng.org/doku.php?id=cracking_wpa , so aircrack-ng itself
seems too work.
other things like setting txpower to 30 or monitor mode works fine
aireplay-ng -9 wlan0 says packet injection is working too
no errors in dmesg
no -1 channel bug
####
Wifi-Card: ALPHA AWUS036H 1000mw
reproduced with Aircrag-ng 1.1 and Aircrack-ng 1.2 rc1 r2454
reproduced on distribution included rtl8187 driver and backports-3.18-rc1-1
no network-manager installed.
no ifplugd running
no wpa_supplicant running
no wpa_cli running
no dhclient running
PS: I LOVE YOUR PROJECT ! \m/
Original issue reported on code.google.com by [email protected] on 26 Nov 2014 at 12:51
The text was updated successfully, but these errors were encountered:
OK, i just see that this patch fixes the clients problem =>
https://code.google.com/p/wifite/issues/detail?id=139
i will test this evening if it fixes this too:
https://code.google.com/p/wifite/issues/detail?id=82
can be closed !
Original issue reported on code.google.com by
[email protected]
on 26 Nov 2014 at 12:51The text was updated successfully, but these errors were encountered: