Wifite Android Apk

0 views

Skip to first unread message

Elvisa Schimke

unread,

Aug 3, 2024, 4:21:10 PM8/3/24

to intotena

I'm having the error "airplay-ng exited unexpectedly" when running an WEP attack with Wifite. In order to fix the issue i need to direct to the wifite code, which is by one sources saying, located in /usr/bin/wifite.

I use Gnome DE and after I use wifite, the wifi symbol just vanishes and you can't connect to the wifi using GUI. I tried it on many desktop environments and most of them have this problem (except deepin)

You can apt-get install the individual tool vs the whole wifi tool chain, as wifite itsself should be fairly small install. Also might need reaver and pixie, but those 3 tools together work well. I'm sure dependencies will need to be installed, but that should happen automatically for you when installing them in Kali.

I have installed Wifite and all the depedencies it mentioned, such as reaver, cowpatty etc. I didn't install pixie. I will give it a try. I think that something else is causing the problem. If I find a free wifi I will install all of them to be sure.

Not sure. Might need to do apt-get clean and/or fix if anything failed to install properly, but possibly couldn't find it is legit 404. Might have got disconnected when doing so. Question, is this a VM? Are you on intel 32-bit, or AMD 64bit?

It not a VM. It is a clean installation of Kali 2017.1 light x86. My laptop has a Core Duo cpu, it supports x64 instructions, even Kali suggested installing x64 version during installation, but I always prefer x86 versions as it has only 2GB of RAM.

There was no disconnection when downloading packages. All packages where downloaded except some of them like the one I mention above. I did my own checks and I saw that these packages do not exist. I do not know where did Kali find them.

see in the attached file what did I see this morning after running ""apt-get install kali-linux-wireless --fix-missing". Downloaded packages where not installed. They are just waiting to be installed. The point is how.

yeah, looks like something is wrong with the repo names, the files are definitely there, just not the naming convention in your text file. Only thing I can say is apt-get update again(first) upgrade, and if you feel lucky, dist-upgrade, then try reinstalling them. Something seems like it has the wrong URL's somewhere. you can see the files there if you look manually - just the naming convention is a bit diff than what I see in your txt file. If this is a true bug, then it needs to be posted on bugs.kali.org if there are some bad entries somewhere.

Yes, the only line is sources.list is the one you mention. I ran update, nothing updated. I ran upgrade and many packages were upgraded. I ran apt-get install kali-linux-wireless --fix-missing and now the command ran with no errors. All packages were installed. I rebooted but my main problem still exists. Wifite refers the same problems. Nothing changed. What should I do anyway?

Try the following, airmon-ng start wlan0, then try wifite. If you have no connected wifi card, may be why it's throwing the error, which looks like it fails when it tries to get the wifi cards locla MAC address.

I never told that it is a VM. It is a clean installation. I have a HP 620 laptop with a 320GB hdd. The disk has 5 partitions. One 450MB, the hidden windows 7/8/8.1 partition, one 128GB for windows, another one 128GB for files etc, a swap linux partition and a linux ext4 partition. The last one has Kali linux. I do not have any USB wifi device. I only have the built-in laptop's wifi card which works fine when connecting to wifi networks. Kali is using it just fine so there is no problem with it. I started feeling that I have to deal with an incompatibility issue. I will try Kali 2016.x as soon as I return back from vacation.

That said, the internal wifi card might work fine for connecting, which is in managed mode, but does not mean it is capable of injection and monitor mode. You need to determine if this is the case, and versions of Kali shouldn't make a difference in this regard. Newer versions of Kali should have better driver support vs older ones as they add more drivers.

Not all cards can do all modes, some are only connection capable in Linux via managed mode(default). Bring up the card with "airmon-ng start wlan0" and if it can't, that is your first issue to work around, which would need a different wifi card. iwconfig will show the new interface in monitor mode if it worked, then start wifite. If airmon-ng can't start the card, you need to get a compatible USB wifi card like the Atheros and TP-Link USB cards. Also, some other programs can cause issues, before brining up the card, run "airmon-ng check kill", then "airmon-ng check" to make sure nothing is listed.

If you get a TP-LINK TL-WN722N card, make sure it's a revision v1, anything later will not work. If you get a AWUS036NEH you might have a hit or miss with the card, seems there are some variations out there. The Alfa AWUS036NH is one of the more reliable ones(at least by users of the card). Some of these work better on native hardware, and don't work well at all in a VM, but you shouldn't have that issue since you're on a native install.

Now, I noticed something, "usefull" I think. After rebooting, Kali connected with my android phone's wifi (tethering, no cable, just tethering). I ran wifite in command line and now the second line after "[+] scanning for wireless devices..." is "[+] enabling monitor mode on wlan0... done" and after that the same errors as in my first post follow. After that, I lost connection with my phone and I had to use the USB cable enabling tethering via USB to be able to have internet access again. I cannot connect to my phone's wifi anymore (unless I restart Kali again). Also, now running wifite again is not reporting the new second line about monitor mode. I hope this helps...

Yeah, you can't be online with the same card when set to monitor mode unless it has two radios/antennas/mimo capabilities, so you can do both wlan0 and wlan0mon at the same time, or get an extra card. Alternative, use a wired connection with eth0 when using monitor mode on wlan0mon.

Once you're done with wifite or any other wifi tools(try some others like airodump-ng to test the card and aireplay-ng) you can then put the card back in managed mode with "airmon-ng stop wlan0mon" and then "ifconfig wlan0 up". Once back up, you can try "dhclient wlan0" and see if you can reconnect, or restart the machine if you can't figure out how to get back on your router. Installing wicd will also make connections with wifi easy-peezy though and has a GUI interface to manage and scan for other AP's and can save settings for each AP you have.