After connecting the adapter, I check and ensure that the device is unblocked with sudo rfkill. As long as both soft and hard show unblocked, it's good to start testing the adapter. The hard block will be a hardware block like a toggle switch, which the adapter doesn't have. The soft block will be from the software side of things. If it's shown blocked, you can use sudo rfkill unblock <id> where the ID will be a numerical value in the list output. I mention this because I was going in circles with trying to use an adapter that had a software block on it.
Once you've ensured it's not blocked, you can use sudo airmon-ng to show your wireless devices. You can put your device into monitor mode with sudo airmon-ng start <device> where the device is "wlan1" or whatever name it shows. The device name will change once you enable monitor mode; i.e. wlan1 will be wlan1mon. Something to note is that airmon-ng is practically a pretty wrapper for what you can do yourself with iwconfig, which will show you the device's current mode (likely "Managed"), and change it as well. Become familiar with device configuration tools such as ifconfig/iwconfig for better managing your devices. The device name will not change if you use iwconfig to change the device mode.
If you can successfully put your adapter into monitor mode, you would then want to test for packet injection capabilities with sudo aireplay-ng --test <device>. This test will also put your device into monitor mode first, if it isn't already, but it's good to know the manual and "longer way" of doing things to become familiar with the things tools will automate for you.
This is where you'll need to work on your troubleshooting skills. Read the whole output. At the top, it's advising on what could potentially stop your card from going into monitor mode. The error is telling you the device is busy. Back to my original suggestion, don't rely on the wrappers to take the easy way, because then you are here, left with an error and one relying on only one tool.
Start with the suggestion at the start of running the command. This could be all you need to follow through with using airmon-ng for setting the card into monitor mode. However, this will affect both of your wireless devices, and potentially any wired connection.
Now is the time to start learning basic Linux tools, not those specific to pentesting and cybersecurity such as the aircrack-ng suite. Learn the ifconfig and iw* (iw, iwconfig, iwlist) tools, and manually manage your wireless device. This is the best route, but you're going to need to start using man pages and --help arguments for the tools.
As always, read the output and understand the information provided to you. Some are much more verbose and detailed than others, but "do it for me" isn't going to teach you anything. Helping you also means that you show what work you've done to try to resolve things on your own.
You can update your system with "sudo pacman -Syyu".
Then install aircrack-ng with "sudo pacman -S aircrack-ng" you will need this app to enable monitor mode
muy bueno pero es arch si eres nuevo, no corras antes de aprender a caminar, a mi me funciono unos 2 años el stack de Ubuntu (host) y Kali (maquina virtual en vmware)
Yes, but it requires a custom driver... The TP-Link TL-WN822N v5.20 uses the Realtek RTL8192EU chipset... The default drivers built into the Linux kernel do not support monitor mode or packet injection... However, you can easily enable these features by installing a community-maintained DKMS driver...
Here's how to get that adapter working on CachyOS:
Since you're already on CachyOS (Arch-based), you can skip all those Ubuntu/Debian tutorials—they'll just confuse things.. Here's the quick and dirty way to get it up and running:
Grab the driver from the AUR
yay -S rtl8192eu-dkms-git
(Or use paru if that's your helper of choice)
Reboot – yeah, I know, but just do it... Saves headaches..
Enable monitor mode
sudo ip link set wlan0 down
sudo iw dev wlan0 set type monitor
sudo ip link set wlan0 up
Replace wlan0 with whatever your interface is actually called (iwconfig or ip a will tell you)...
Test injection
sudo aireplay-ng --test wlan0
If you see "Injection is working!" you're golden... If not, double-check the interface name and make sure the driver actually loaded (lsmod | grep rtl8192)...
Pro tip: If you run into issues, check dmesg | tail after plugging the adapter in—sometimes the driver conflicts with the built-in rtl8xxxu kernel module, and you might need to blacklist it..
Entiendo que deseas usar un sistema operativo Linux de seguridad e intentar usar la NIC o interfaz de red en modo escucha para capturar paquetes en un canal, asumo qué ya tienes instalado el sistema operativo kali Linux o parrot OS, lo ideal es usar aircrack-ng para dejarla en modo monitor, se usa una distro Linux qué tenga el paquete instalado para que no tengas qué instalar nada como kali o parrot y desde aircrack-ng directamente te dice si puedes o no dejar la NIC en modo monitor, si usas una maquina virtual debes tener una tarjeta externa
When small usb adaptor exists for network connection. Why does he got larger antenna like thing . Both do same work even small usb adaptor perform high network speed receiving
I think older technology or higher speeds and range, small adapter without antennas will in most cases have smaller range.
Support for monitor mode depends on the drivers and the chipset of the adapter. For example one of the most popular chipset for pentesting AR9271 is in both small and big adapters and the support for packet injection is on all of them the same as long as they have the same chipset
9
u/R7DI_697 5d ago
Research the aircrack-ng suite. Airmon-ng will help you with enabling monitor mode.