I bought an Alfa AWUS1900 WLAN device for education purpose with Aircrack, because it has Linux support and some posts/reviews confirms that. Sadly I can't get the driver working in monitor mode, especially on the new 5er Kernel. ## My setup The notebook runs Ubunu 18.04.3 LTS with VirtualBox where I created a VM with the [latest Kali Linux](https://www.kali.org/downloads/) , which is 2019.3 at the time of writing. VirtualBox has the extension pack installed for USB 2 support. It runs as root for USB forwarding: ## My chipset Since I read reviews about users getting different chipsets for the same device type, I plugged the device in and verified to have the RTL8814AU chipset: root@kali:~# lsusb | grep -E "Realtek*" Bus 001 Device 002: ID 0bda:8813 Realtek Semiconductor Corp. RTL8814AU 802.11a/b/g/n/ac Wireless Adapter ## Not working drivers A snapshot was created before any driver was installed and after each non-working driver, I went back to the vanilla snapshot to have a clean system and make sure that no older driver influence the current one. ### zebulon2/rtl8814au [This driver](https://askubuntu.com/questions/981638/alfa-awus1900-driver-support/983834#983834) worked partially when using the Kali Linux snapshot image directly without upgrading packages (there are many updates avaliable). The device got detected and the network manager shows me avaliable APs as well as using nmcli dev wifi command. But the device is in managed mode: root@kali:~/rtl8814au# iw dev | grep type type managed I can't switch to monitor mode: root@kali:~/rtl8814au# airmon-ng check kill Killing these processes: PID Name 831 wpa_supplicant root@kali:~/rtl8814au# airmon-ng start wlan0 PHY Interface Driver Chipset phy0 wlan0 rtl8814au Realtek Semiconductor Corp. RTL8814AU 802.11a/b/g/n/ac ERROR adding monitor mode interface: command failed: Operation not supported (-95) Even not with ifconfig: root@kali:~/rtl8814au# ifconfig wlan0 down root@kali:~/rtl8814au# iwconfig wlan0 mode monitor Error for wireless request "Set Mode" (8B06) : SET failed on device wlan0 ; Operation not permitted. dmesg lot entry when putting in monitor mode: [ 940.905187] RTL871X: ERROR HalPwrSeqCmdParsing: Fail to polling Offset[0x6]=00 [ 940.905191] RTL871X: nolinked power save leave Some posts mentioned a bug in airmon-ng but say it should work with ifconfig. ### realtek-rtl88xxau-dkms According to [this thread in the kali forum](https://forums.kali.org/showthread.php?36296-EXTREME-WIFI-SUPPORT-Alfa-Networks-AWUS1900-WORKING) , there is a package called realtek-rtl88xxau-dkms in the repos that should contain all required drivers. So I installed his dependencies [like described here](https://forums.kali.org/showthread.php?36296-EXTREME-WIFI-SUPPORT-Alfa-Networks-AWUS1900-WORKING&p=79079#post79079) apt install dkms && apt-get install bc && apt-get install build-essential && apt-get install linux-headers-$(uname -r) then the driver package using apt-get install realtek-rtl88xxau-dkms and plugged in my usb wifi device. I'm wondering that I get some error about missing module or filename, but it's not clear for me what exactly is missing and if it's required (since it says installation completed): 88XXau.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.2.0-kali3-amd64/updates/ depmod.... DKMS: install completed. dmesg detects the new device, but after a few seconds it got disconnected: [ 1080.147957] usb 1-1: new high-speed USB device number 4 using ehci-pci [ 1080.595125] usb 1-1: New USB device found, idVendor=0bda, idProduct=8813, bcdDevice= 0.00 [ 1080.595131] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 1080.595135] usb 1-1: Product: 802.11ac NIC [ 1080.595136] usb 1-1: Manufacturer: Realtek [ 1080.595137] usb 1-1: SerialNumber: 123456 [ 1087.695407] usb 1-1: USB disconnect, device number 4 On the first run, this was all I got. But the second approach shows also this VirtualBox error: ### aircrack-ng/rtl8812au I'm not sure if [aircrack-ng/rtl8812au](https://github.com/aircrack-ng/rtl8812au) is the same driver as the realtek-rtl88xxau-dkms apt-package, so I tried ./dkms-install.sh there but also no luck, just similar issues. Altough the snapshot of Kali Linux is outdated for several months (over 800 package updates for a vanilla installation), there seems no kernel update. The following kernel version is the same before and after updating all packages: Linux kali 5.2.0-kali2-amd64 #1 SMP Debian 5.2.9-2kali1 (2019-08-22) x86_64 GNU/Linux

So i installed https://github.com/aircrack-ng/rtl8812au on my new ubuntu system. Using a realtek RTL8812AU USB wireless . Installed without problems but running airodump-ng getting no beacons at all. Wireless is in monitor mode. Any advice would be helpfull.

I am connected to my VirtualBox through Wi-Fi and have selected the bridged adapter in Kali Linux. However, when I try to connect using NAT, it is not working. Additionally, I am having problems with Aircrack-ng and network commands in Kali Linux. I cannot scan or hack any Wi-Fi networks. Please help me solve this issue.

I'm trying to monitor my Access Point "My AP" with a "TP-Link Archer T3U Plus AC1300". I put it in monitor mode: ip link set wlan0 down iwconfig wlan0 mode monitor ip link set wlan0 up _ $iwconfig wlan0 IEEE 802.11b ESSID:"" Nickname:"" Mode:Monitor Frequency:2.412 GHz Access Point: Not-Associated Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=0/100 Signal level=-100 dBm Noise level=0 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 airodump-ng receives beacons from other Access Points from my neighbors but not from my "My AP": $airodump-ng --band abg wlan0 BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID XXXXX -1 0 24 0 1 -1 WPA My AP -46 0 218 0 6 405 WPA2 CCMP PSK YYY <=== HERE XXXXX -60 3713 1572 1 1 130 WPA2 CCMP PSK AAA XXXXX -63 5010 1910 9 1 195 WPA2 CCMP PSK AAA XXXXX -66 5531 0 0 1 130 WPA2 CCMP PSK AAA XXXXX -72 5362 0 0 1 130 WPA2 CCMP PSK AAA BSSID STATION PWR Rate Lost Frames Notes Probes XX AAA -85 0 - 1e 0 204 XX AAA -1 1e- 0 0 22 XX AAA -74 1e- 1 0 254 XX AAA -80 1e- 1e 0 813 XX AAA -66 1e- 1e 0 636 XX AAA -74 1e- 6 14 100 XX AAA -86 1e- 1 0 10 Info: - AP is FRITZ!Box 7490 - AP is a Mesh with a Fritz Repeater - AP has no hidden SSI. I can see it in my phone and connect to it. - AP is 2,4 GHz and 5 GHz Why I don't receive any beacons from my Access Point but from other in my area?

I'm trying to crack my own wi-fi through WPS using reaver using sudo reaver -i wlan0 -b 84:9F:B5:71:48:28 -vv and it keeps outputting these messages repeatedly. I'm using tp link wn722n wireless adapter v3. It supports monitor mode and packet injection (after a bit of exhaustion). There's one thing that doesn't work on this adapter which is changing its mac address (don't know if that would be useful or not). I left it for 10 hours and it's still like that. The problem is the with the error (WPS transaction failed (code: 0x02), re-trying last pin) and that it's stuck on the same pin (12345670) P.S: I'm a bit of a newbie to linux, so please make your answer detailed. [+] Waiting for beacon from 20:E8:82:AE:36:76 [+] Switching wlan0 to channel 1 [+] Received beacon from 20:E8:82:AE:36:76 [+] Vendor: RealtekS [+] Trying pin "12345670" [+] Sending authentication request [+] Sending association request [+] Associated with 20:E8:82:AE:36:76 (ESSID: WE_AE3676) [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [+] Sending EAPOL START request [!] WARNING: Receive timeout occurred [!] WARNING: 10 successive start failures [+] Sending EAPOL START request [+] Sending WSC NACK [!] WPS transaction failed (code: 0x02), re-trying last pin

I wanted to find passphrase from .cap file and .txt file (Password Dictionary). But I have too many .txt file's there. Can I use those file one by one for cracking? My command is given below: I tried this way, but it did not work

aircrack-ng -a2 -b [bssid] -w /home/kali/Downloads/Wordlist/*.txt  /home/kali/Desktop/*.cap

root@kali:~# aircrack-ng –a2 –b F8:1A:67:56:52:36 –w /root/pass.txt /root/Desktop/*.cap Opening –a2 open failed: No such file or directory Opening –b open failed: No such file or directory Opening F8:1A:67:56:52:36 open failed: No such file or directory Opening –w open failed: No such file or directory Opening /root/pass.txt Unsupported file format (not a pcap or IVs file). Opening /root/Desktop/-01.cap Read 219544 packets. # BSSID ESSID Encryption 1 F8:1A:67:56:52:36 khushi sahu WPA (1 handshake) Choosing first network as target. root@kali:~# Why is it showing -a2, -b, -w as "open failed: No such file or directory", although they are aircrack commands? What am I doing wrong?

I'm using aircrack-ng to capture a handshake on a WPA2 access point. I would like to write the outfile in pcap format, but I keep getting errors. I've tried reinstalling aircrack-ng using versions from github and arch repository. I ultimately want to save the outfile in hccapx format for cracking with hashcat.

## OS: Arch Linux x86_64 
## Kernel: 5.18.12-zen1-1-zen 

## Name: aircrack-ng-git
## Version: 20220715.76370d0e-1

sudo airmon-ng start wlan1
# (mac80211 monitor mode already enabled for [phy1]wlan1 on [phy1]10)

sudo airodump-ng  -i wlan1 -c 6 --essid $ESSID --write "$ESSID-log" --output-format pcap
# Invalid output format: IVS and PCAP format cannot be used together.

sudo airodump-ng  -i wlan1 -c 6 --essid $ESSID --write "$ESSID-log"
# outfile: $ESSID-log.ivs

sudo airodump-ng  -i wlan1 -c 6 --essid $ESSID --write "$ESSID-log" --output-format kismet
# outfile: $ESSID-log.kismet.csv
# outfile: $ESSID-log.csv

I have a major problem on my Nethunter. Whenever I try to run "airmon-ng start wlan0" or "airmon-ng check kill" this happens; ~~~lang-text Error: /proc must be mounted To mount /proc at boot you need an /etc/fstab line like: proc /proc proc defaults In the meantime, run "mount proc /proc -t proc" Requested device "wlan0" does not exist. Run /usr/sbin/airmon-ng without any arguments to see available interfaces ~~~ Edit: "airmon-ng" working properly. I can see the interfaces. I searched a lot and... Nothing. Im stuck with this problem. I already saw a lot questions as same as mine but answers was outdated. Edit: the output of sudo ls -la /proc

-xr-xr-x 624 root root    0 Jan  1  1970 .
drwx------  21 root root 3488 Feb  3 10:27 ..
dr-xr-xr-x   9 root root    0 Feb  4 22:02 6642
dr-xr-xr-x   9 root root    0 Feb  4 22:03 6777
dr-xr-xr-x   9 root root    0 Feb  4 22:03 6780
dr-xr-xr-x   9 root root    0 Feb  4 22:03 6798
dr-xr-xr-x   9 root root    0 Feb  4 22:03 6799
-r--r--r--   1 root root    0 Feb  4 22:03 NVTSPI
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 aed
-dr-xr-xr-x   4 root root    0 Feb  4 22:03 asound
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 atf_log
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 battery
--?????????   ? ?    ?       ?            ? battery_status
-?????????   ? ?    ?       ?            ? bcctlmt
--?????????   ? ?    ?       ?            ? boot_mode
dr-xr-xr-x   2 root root    0 Feb  4 22:03 bootdevice
-?????????   ? ?    ?       ?            ? bootprof
--?????????   ? ?    ?       ?            ? border_suppression
-?????????   ? ?    ?       ?            ? buddyinfo
-dr-xr-xr-x   3 root root    0 Feb  4 22:03 bus
--?????????   ? ?    ?       ?            ? ccci_dump
-?????????   ? ?    ?       ?            ? ccci_log
--?????????   ? ?    ?       ?            ? cgroups
dr-xr-xr-x   2 root root    0 Feb  4 22:03 charger
dr-xr-xr-x   2 root root    0 Feb  4 22:03 chip
-?????????   ? ?    ?       ?            ? clkdbg
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 clkmgr
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 cm_mgr
--?????????   ? ?    ?       ?            ? cmdline
-?????????   ? ?    ?       ?            ? config.gz
--?????????   ? ?    ?       ?            ? consoles
dr-xr-xr-x   2 root root    0 Feb  4 22:03 cpu_loading
dr-xr-xr-x   5 root root    0 Feb  4 22:03 cpufreq
dr-xr-xr-x   2 root root    0 Feb  4 22:03 cpuhvfs
-r--r--r--   1 root root    0 Feb  4 22:03 cpuinfo
--?????????   ? ?    ?       ?            ? crypto
-?????????   ? ?    ?       ?            ? ddr_info
--?????????   ? ?    ?       ?            ? devapc_dbg
lrwxrwxrwx   1 root root   29 Feb  4 22:03 device-tree -> /sys/firmware/devicetree/base
-?????????   ? ?    ?       ?            ? devices
--?????????   ? ?    ?       ?            ? diskstats
dr-xr-xr-x   2 root root    0 Feb  4 22:03 dpe
dr-xr-xr-x   2 root root    0 Feb  4 22:03 drcc
dr-xr-xr-x   3 root root    0 Feb  4 22:03 driver
dr-xr-xr-x   6 root root    0 Feb  4 22:03 eem
-?????????   ? ?    ?       ?            ? execdomains
--?????????   ? ?    ?       ?            ? f2fs_status
-?????????   ? ?    ?       ?            ? fb
--?????????   ? ?    ?       ?            ? filesystems
-?????????   ? ?    ?       ?            ? fm
--?????????   ? ?    ?       ?            ? fpsensor
dr-xr-xr-x   2 root root    0 Feb  4 22:03 freqhopping
dr-xr-xr-x   6 root root    0 Feb  4 22:03 fs
-rw-r--r--   1 root root    0 Jan 29 16:38 ged
--?????????   ? ?    ?       ?            ? gesture_function
-?????????   ? ?    ?       ?            ? gesture_state
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 golden
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 gpufreq
--?????????   ? ?    ?       ?            ? interrupts
-?????????   ? ?    ?       ?            ? iomem
--?????????   ? ?    ?       ?            ? ioports
dr-xr-xr-x 129 root root    0 Feb  4 22:03 irq
dr-xr-xr-x   2 root root    0 Feb  4 22:03 isp_p2
-?????????   ? ?    ?       ?            ? kallsyms
--?????????   ? ?    ?       ?            ? key-users
-?????????   ? ?    ?       ?            ? keys
--?????????   ? ?    ?       ?            ? kmsg
-?????????   ? ?    ?       ?            ? kpagecgroup
--?????????   ? ?    ?       ?            ? kpagecount
-?????????   ? ?    ?       ?            ? kpageflags
--?????????   ? ?    ?       ?            ? last_kmsg
-?????????   ? ?    ?       ?            ? loadavg
--?????????   ? ?    ?       ?            ? locks
-?????????   ? ?    ?       ?            ? m4u
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mali
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mcdi
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mdpm
--r--r--r--   1 root root    0 Jan 29 17:18 meminfo
-?????????   ? ?    ?       ?            ? misc
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mobile_tm
--?????????   ? ?    ?       ?            ? modules
lrwxrwxrwx   1 root root   11 Feb  4 22:03 mounts -> self/mounts
-?????????   ? ?    ?       ?            ? mrdump_rst
--?????????   ? ?    ?       ?            ? msdc_debug
-?????????   ? ?    ?       ?            ? msdc_help
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mt-auxadc
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mt_power_gs
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mtk-perf
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mtk_battery_cmd
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mtk_cmdq_debug
--?????????   ? ?    ?       ?            ? mtk_jpeg
dr-xr-xr-x   2 root root    0 Feb  4 22:03 mtkcooler
dr-xr-xr-x   2 root root    0 Feb  4 22:03 mtktz
-?????????   ? ?    ?       ?            ? mtprintk
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 mtprof
-lrwxrwxrwx   1 root root    8 Feb  4 22:03 net -> self/net
--?????????   ? ?    ?       ?            ? nvt_baseline
-?????????   ? ?    ?       ?            ? nvt_diff
--?????????   ? ?    ?       ?            ? nvt_fw_version
-?????????   ? ?    ?       ?            ? nvt_raw
--?????????   ? ?    ?       ?            ? nvt_selftest
-?????????   ? ?    ?       ?            ? pagetypeinfo
--?????????   ? ?    ?       ?            ? partitions
dr-xr-xr-x   2 root root    0 Feb  4 22:03 pbm
dr-xr-xr-x   4 root root    0 Jan 29 16:38 perfmgr
dr-xr-xr-x   4 root root    0 Feb  4 22:03 picachu
-?????????   ? ?    ?       ?            ? pidmap
--?????????   ? ?    ?       ?            ? pl_lk
dr-xr-xr-x   5 root root    0 Feb  4 22:03 ppm
dr-xr-xr-x   2 root root    0 Jan 29 16:38 pressure
dr-xr-xr-x   2 root root    0 Feb  4 22:03 resource_monitor
-?????????   ? ?    ?       ?            ? rid
--?????????   ? ?    ?       ?            ? rlkdevinfo
-?????????   ? ?    ?       ?            ? sched_debug
--?????????   ? ?    ?       ?            ? schedstat
dr-xr-xr-x   2 root root    0 Feb  4 22:03 scp_dvfs
dr-xr-xr-x   2 root root    0 Feb  4 22:03 scsi
-?????????   ? ?    ?       ?            ? sdcard_intr_gpio_value
-lrwxrwxrwx   1 root root    0 Jan  1  1970 self -> 6799
--?????????   ? ?    ?       ?            ? softirqs
-?????????   ? ?    ?       ?            ? stat
--?????????   ? ?    ?       ?            ? swaps
dr-xr-xr-x   2 root root    0 Feb  4 22:03 swpm
dr-xr-xr-x   1 root root    0 Feb  4 22:03 sys
-?????????   ? ?    ?       ?            ? sysrq-trigger
--?????????   ? ?    ?       ?            ? tasks_all
-?????????   ? ?    ?       ?            ? tasks_rq
--?????????   ? ?    ?       ?            ? thermlmt
lrwxrwxrwx   1 root root    0 Jan  1  1970 thread-self -> 6799/task/6799
-?????????   ? ?    ?       ?            ? timer_list
--?????????   ? ?    ?       ?            ? tkv
-?????????   ? ?    ?       ?            ? tkv_recovery
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 tran_chg_limit_current
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 tran_dvfsrc
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 tran_gc_debug
--?????????   ? ?    ?       ?            ? tran_mmc_cid
dr-xr-xr-x   2 root root    0 Feb  4 22:03 tran_release_wakelock
-?????????   ? ?    ?       ?            ? ttpct
-dr-xr-xr-x   4 root root    0 Feb  4 22:03 tty
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 udi
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 uid
--?????????   ? ?    ?       ?            ? uid_concurrent_active_time
-?????????   ? ?    ?       ?            ? uid_concurrent_policy_time
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 uid_cputime
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 uid_io
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 uid_procstat
--?????????   ? ?    ?       ?            ? uid_time_in_state
dr-xr-xr-x   2 root root    0 Feb  4 22:03 upower
-?????????   ? ?    ?       ?            ? uptime
--?????????   ? ?    ?       ?            ? version
-?????????   ? ?    ?       ?            ? vmallocinfo
--?????????   ? ?    ?       ?            ? vmstat
-?????????   ? ?    ?       ?            ? wdk
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 wlan
-dr-xr-xr-x   2 root root    0 Feb  4 22:03 wmt_tm
--?????????   ? ?    ?       ?            ? zoneinfo
-?????????   ? ?    ?       ?            ? zraminfo

I mean you could check if the wps button has been pressed or not using this command > wpa_cli wps_pbc But i am wondering if it's possible to do it using airodump-ng Without any one connecting to it. The wifiphisher Utility claims to be able to do it , even that i wasn't able to find any info about a ready tool that does that and the python code isn't clear enough so i can't tell how they do it Trying to figure out a method to do it passively to add it to a possibly new attack vector Thanks

I recently installed a Kali Linux distribution with default toolset. I try to use airmon-ng but have no success. I had aircrack-ng package installed (it was installed from the beggining but to be sure I did sudo apt update && sudo apt install aircrack-ng, it didn't help). The package is just not found. sudo apt install airmon-ng didn't help too. How do I install and start to use airmon-ng in my installation? Upd: here's the contents of apt list --installed | grep aircrack:

aircrack-ng/kali-rolling,now 1:1.6-4 amd64 [installed]

I have a question about the program aircrack. When I want start the monitor mode in my adapter i use the command: airmon-ng start wlan0 and when i wanna stop the monitor mode i use the command: airodump-ng wlan0mon When I use the last command, my internet does not come back. In other words, i cant see the networks to connect. Do I need to enter with another command?

When I type this command iwconfig in Kali Linux when I am root the output is

lo   no wireless extensions
eth0  no wireless extensions

When I try running airmon-ng I get no output and this error: ls: cannot access '/sys/class/ieee80211/': No such file or directory This is on a linux terminal on my Pixelbook, I installed aircrack-ng using **Katoolin**. I had a look at [this question](https://unix.stackexchange.com/questions/306836/airmon-ng-ls-cannot-access-sys-class-ieee80211-no-such-file-or-directory?newreg=5c4e9d19841d45bab9e2eb2d75da65b8) but the answer doesn't apply to ChromeOS. running iwconfig gives me:

lo         no wireless extensions.

eth0       no wireless extensions.

I have installed aircrack using command sudo yum install aircrack-ng. But when I run command airmong-ng It gives an error: Bash airmong-ng command not found. Do I have to install airmong-ng individually? I've tried sudo yum install airmong-ng, but package not found.

If I use aircrack-ng in a console, the console shows messages sometimes, ex.: new USB device plugged in when I plug in a new USB device. This messes up the screen and I cannot see that what was the key that has been found after running aircrack-ng for weeks. **Question:** If we run aircrack-ng in the console (ALT+CTRL+F3 for example) how can we store the found key? Or redirect the system messages sent to the console to devnull?

When I try to install /aicrack-ng/mdk4 I get:

: ld returned 1 exit status make: *** [Makefile:38: mdk4] Error 1 make: Leaving directory '/home/u4/mdk4/src' make: *** [Makefile:10: all] Error 2

This is the end of the output (since when I submit the whole output it is considered as a spam) when I run 'make' in the mdk4 folder.

-g -O3 -Wall -Wextra   -c -o wids.o wids.c
make: Leaving directory '/home/u4/mdk4/src/attacks'
make -C attacks
make: Entering directory '/home/u4/mdk4/src/attacks'
make: Nothing to be done for 'all'.
make: Leaving directory '/home/u4/mdk4/src/attacks'
gcc -g -W -Wall -O3 -D_FILE_OFFSET_BITS=64 -D_REVISION=mdk4-v1 -DCONFIG_LIBNL30 -DCONFIG_LIBNL -I/usr/include/libnl3  -g -O3 -Wall -Wextra -fcommon  mdk4.c osdep/libosdep.a debug.o helpers.o mac_addr.o linkedlist.o greylist.o dumpfile.o packet.o brute.o osdep.o channelhopper.o ghosting.o fragmenting.o attacks/attacks.o attacks/auth_dos.o attacks/beacon_flood.o attacks/countermeasures.o attacks/deauth.o attacks/dummy.o attacks/eapol.o attacks/fuzzer.o attacks/ieee80211s.o attacks/probing.o attacks/wids.o -o mdk4 -lnl-genl-3 -lnl-3  -lm -Losdep -losdep -lpthread -lpcap
/usr/bin/ld: attacks/auth_dos.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/beacon_flood.o:/home/u4/mdk4/src/attacks/beacon_flood.c:34: multiple definition of `bssid'; attacks/auth_dos.o:/home/u4/mdk4/src/attacks/auth_dos.c:50: first defined here
/usr/bin/ld: attacks/beacon_flood.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/countermeasures.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/deauth.o:/home/u4/mdk4/src/attacks/deauth.c:19: multiple definition of `bssid'; attacks/auth_dos.o:/home/u4/mdk4/src/attacks/auth_dos.c:50: first defined here
/usr/bin/ld: attacks/deauth.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/dummy.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/eapol.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/fuzzer.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/ieee80211s.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/probing.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
/usr/bin/ld: attacks/wids.o:/home/u4/mdk4/src/attacks/attacks.h:39: multiple definition of `attack_count'; attacks/attacks.o:/home/u4/mdk4/src/attacks/attacks.h:39: first defined here
collect2: error: ld returned 1 exit status
make: *** [Makefile:38: mdk4] Error 1
make: Leaving directory '/home/u4/mdk4/src'
make: *** [Makefile:10: all] Error 2

- And then I found this solution on github: Installation git clone https://github.com/aircrack-ng/mdk4 cd mdk4 make sudo make install # Using Arch Linux (and derived) append CC=clang after any make in commands. But the thing is I have no idea how to do this > append CC=clang after any make in commands. I use manjaro with bspwm environment What should I do? edit: So I did the CC=clang thing and this time the error is slightly different: ` error: linker command failed with exit code 1 (use -v to see invocation) make: *** [Makefile:38: mdk4] Error 1 make: Leaving directory '/home/u4/mdk4/src' make: *** [Makefile:10: all] Error 2` edit: The first screenshot is the beginning of the output and the seconde one is the end of the output.

I apologise if this is basic troubleshooting. I bought a AWUS036NEH, which is recognised and properly appearing in Device Manager in Windows 10. I am using Debian 10x 64 bit, on Windows 10 via VMWare Workstation. I installed the Windows 10 driver for the ALFA device. My PC has an ethernet connection from a BT wifi disc. I am using VmWare Workstation, Kali 2020 64 bit. When I go to VM, Removable Devices, I am given the choice to connect my ALFA device to Kali, but disconnecting it from the host. Unfortunately, doing so disconnects me from the internet on my PC. Connecting the device to Kali (which disables my internet on PC)

root@kali:~# airmon-ng start wlan0
PHY Interface Driver Chipset
phy0 wlan0 rt2800usb Ralink Technology, Corp. RT2870/RT3070
(mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon)
(mac80211 station mode vif disabled for [phy0]wlan0)

Can anyone shed any light on this? I went to Device Manager, and right clicked on my 802.11n USB wireless card, have altered the Country region (2.4GHz); to see if that would help it would seem not....? using anything other than 0,1 or 5, (2,3,4,6,7), my internet cuts out. I am not sure how changing the channl of my wireless card would affect my internet, when it is a plug-in/USB device? I thought perhaps there was a conflict between for Kali, but I am totally basically lost. Also, when I connect the USB wireless card to VMWare, then ran /usr/sbin/airmon-ng and I got:

phy3    wlan0           rt2800usb       Ralink Technology, Corp. RT2870/RT3070

Then I ran sudo airmon-ng start wlan0 which gave me:

PHY     Interface       Driver          Chipset

phy3    wlan0           rt2800usb       Ralink Technology, Corp. RT2870/RT3070
                (mac80211 monitor mode vif enabled for [phy3]wlan0 on [phy3]wlan0mon)
                (mac80211 station mode vif disabled for [phy3]wlan0)

I then ran sudo airodump-ng wlan0mon, left it running it for 15 minutes...totally blank.

Interface wlan0mon:                                                                                                                                                                                               
ioctl(SIOCGIFINDEX) failed: No such device

Where am I going wrong? Why is my internet crashing on my PC? Can I have my internet, and use aircrack at the same time?

When I run airmon-ng on Ubuntu 20.04 terminal it gives me the details for PHY, Interface, Driver and Chipset of my laptop but when using Kali Linux on Virtual box it doesn't give me the details. What could be the problem? Both are updated and upgraded to their respective latest versions.

When I run airodump-ng to scan Wi-Fis around me, I get no output, like there's nothing around me. I have a Qualcomm Atheros QCA9377 adapter that's integrated in my laptop (Dell Inspiron 15) and i'm running Kali Linux 64 2019.1 here's the airmon-ng output:

airmon-ng start wlan0

Found 3 processes that could cause trouble.
Kill them using 'airmon-ng check kill' before putting
the card in monitor mode, they will interfere by changing channels
and sometimes putting the interface back in managed mode

  PID Name
  550 NetworkManager
  602 wpa_supplicant
 2069 dhclient

PHY	Interface	Driver		Chipset

phy0	wlan0		ath10k_pci	Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31)

		(mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon)
		(mac80211 station mode vif disabled for [phy0]wlan0)

i have tried airmon-ng check kill but it didn't work, when i run airodump-ng, here's what i get:

CH 12 ][ Elapsed: 12 s ][ 2019-05-09 19:23                                    
                                                                               
 BSSID              PWR  Beacons    #Data, #/s  CH  MB   ENC  CIPHER AUTH ESSID
                                                                               
                                                                               
 BSSID              STATION            PWR   Rate    Lost    Frames  Probe

with channels switching, i have tried using 1 specific channel yet i found not ports with this solution either. I have also noticed some error messages when i boot linux related to the network driver:

ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/pre-cal-pci-0000:02:00.0.bin (-2)
firmware_class: See http://wiki.debian.org/Firmware  for information about missing firmware
ath10k_pci 0000:02:00.0: firmware: failed to load ath10k/cal-pci-0000:02:00.0.bin(-2)
ath10k_pci 0000:02:00.0: firmware: failed to load ath10/QCA9377/hw1.0/firmware-6.bin (-2)

I also confirmed that my network adapter supports monitor mode using iw list and monitor mode appears in the list:

Supported interface modes:
		 * IBSS
		 * managed
		 * AP
		 * monitor
		 * mesh point
		 * P2P-client
		 * P2P-GO
		 * P2P-device