You're wrong.
While with most drivers it is wlanXmon, some don't have VIF and just turn the interface in monitor mode
Type: Posts; User: Mister_X
You're wrong.
While with most drivers it is wlanXmon, some don't have VIF and just turn the interface in monitor mode
They are present in the repo, no need to recompile.
sudo apt install hcxtools hcxdumptool
And there is no need for the root stuff, just use sudo.
You need root to run apt-get, and you currently are a regular user. Using sudo as explained by Rasalom is the way to go.
Anything in dmesg about it?
Looks short in memory, it may not be usable with a GUI. Definitely go with the 32 bit version if you insist.
If the CPU doesn't support PAE, you'll have to recompile the kernel.
You got the wrong driver (which is for an old 802.11g device), this is a mediatek chipset, and the driver is built in the kernel; you may just be missing the firmware, which would be indicated in...
Wait a few month for the driver to be in the kernel probably.
What's the output of lspci and lspci -n? Just need the lines for the card, as it may be using another chipset.
anything in dmesg about the issue?
Try 2020.1, and use airmon-ng to also put it in monitor mode instead of manually doing it.
What's the exact error?
You'll probably need to set-up an AP if you want to connect wirelessly to the RPi. Use hostapd for that. Otherwise, if you're connecting to an AP, skip this.
Here is the docs explaining how to...
No idea. What chipset does the wireless adapter have? Anything in dmesg about missing firmware?
It was because you use single quotes. It should be backticks, `, or as JumgleJim45 mentions, enclosed in $()
It may be down. Interfaces that are down aren't displayed by ifconfig, you have to append the -a parameter.
Make sure your source.list looks like this: https://www.kali.org/docs/general-use/kali-linux-sources-list-repositories/
Then run "apt update"
Have you looked at the file referenced on that screen? Look up any error in google first.
You plugged it on a USB 3.0 port (you can see that with xhci-hcd at the top). Try plugging it on a USB 2.0
Without knowing what isn't working, there is no way to know how to fix it.
What is the error? Not just the last line, the full output.
Try OwnCloud
Anything in dmesg when you plug it? Clear dmesg before plugging (reboot if you already plugged it) using dmesg -c, plug it, then hit dmesg again
Set the VM to automatically attach new USB to it, then plug it when the VM has focus.
Tell virtualbox to attach the adapter to the virtual machine.
anything in dmesg when you plug the card? Clear it first (dmesg -c), plug the card, and then run dmesg again.
If I'm understanding the output correctly, it just can't tell what processes are running on it. At first look, I don't see anything wrong.
What does hashcat -I (uppercase i) report?
Your sources.list is messed up. Check the kali docs, the defaults are provided.
The station is just not associated/connected to any AP (or your card isn't able to capture its traffic (such as using 802.11g card with 802.11n or ac traffic)
I've seen similar behavior happen on VMware, with USB 3.0 ports. Switching to 2.0 solved the issue. Try plugging to a USB 2.0 and report back.
Keep waiting, it will finish.
There are a few mirrors, and you'll be redirected to the fastest mirror (with the entry in sources.list). You can override this and select a mirror: http://http.kali.org/README.mirrorlist
ACKs are typically sent at a lower rate, so they are received further. It may very well be that the devices are too far away (not in range). If it's not that, you'll have to be more precise on why...
You need to fix the time on your system. Even if it's correct, the timezone may be incorrect; you need to fix that first before setting the time.
It is indicated on the VM comments: root/toor.
It's all virtual, even the interfaces. You get one virtualized interface, and you can see that in lspci. VMware/VirtualBox choose the best interface for internet and does NAT by default.
If you...
@AParthenopaeus94, open a different thread, and the answer is in another thread.
That's a wired Ethernet card as stated by "Gigabit Ethernet controller". Further research with exact chipset as (RTL8111, and others) confirms that as well (search one of them and click images or go...
How much disk did you assign to the VM?
Have you checked the output of the console when that happens?
Any reason you're installing it? There are prebuilt VM provided.
Have you tried plugging it? AFAIR it uses carl9170 driver
Does airmon-ng report anything?
What wireless adapter do you have?
Have you added any extra repo?
If no, then "apt update && apt-get -f install" may fix it.
You forgot to kill network managers prior to putting your card in monitor mode: airmon-ng check kill
Well, looks like the driver's there, so it should work.
It's not in the debian testing repo, and it's not really for pentesting, so it won't be in the packages. You'll have to compiling it from sources
https://wiki.archlinux.org/index.php/HiDPI#Xfce
how did you install it?
What wireless adapter do you have? Run it live and run 'airmon-ng' and 'lspci' then post that output
The current kali now uses XFCE, that script isn't needed.
Check out https://kali.training, it contains a free ebook for learning Kali.
You can use it, it's just more convenient.
Yes, you can just install any ISO, it will work just fine. Make sure to install the vmware tools as well.
As a side note, compat-wireless hasn't been updated in years, you tried to install drivers that are almost 10 years old.
What chipset is it? Plug it and run airmon-ng. If it returns nothing, run lsusb -v and paste the output here.
What plugin are you trying to use? Have you read their documentation?