I have the TP-Link TL-WN822N v. C (Realtek chipset) wireless adapter, and I am running Kali Linux from a live CD. After many hours of trying to get around these problematic drivers, I managed to get them to work. ### Issues - So now I can connect to the internet, but when I run the airmon-ng command the interface of the adapter does not show up. - When I run the airmon-zc command I get the interface as wlan1 but the PHY field is null so I can't get a monitor interface with airmon-ng start wlan1 command. Any suggestions on how I can assign it manually maybe?

I'm facing an issue with my MT7601U network adapter on Linux. Although I've successfully entered monitor mode, I'm encountering difficulties capturing handshakes and discovering devices in the network/s. Strangely, only WPS attacks seem to work reliably. Here are the key details: - **Adapter:** Ralink MT7601U - **Distribution:** parrotOS 6.0 (lorikeet) 64-bit Kernel 6.8.0-xxxxx - **Problem Summary:** - Monitor mode is enabled. - Unable to capture handshakes or detect devices in the network, except for WPS attacks which is very different kind of wifi attack. - **Attempts to Resolve:** - Successfully entered monitor mode using the iw command (sudo iw dev set monitor control). - Tried various tools like Aircrack-ng, Wireshark, and tcpdump for packet capture, but no success in capturing handshakes. - Even after ensuring monitor mode is active, no devices are being discovered in the network, except during WPS attacks. - **Observations:** - Checked system logs (dmesg, /var/log/syslog) but found no relevant error messages. - Updated drivers through the package manager and also tried downloading from the manufacturer's website, but the issue persists. I'm reaching out to the community for guidance on troubleshooting steps or potential solutions to this problem. Any advice or insights from users familiar with the MT7601U adapter or similar issues with other adapters would be greatly appreciated. Thank you for your assistance!

Hello I am on Ubuntu and I have a problem with the aireplay-ng command: When i do the command

-ng -0 0 -a $bssid -c $targetid wlp3s0

in the terminal I have the error message 'resource or device busy' and my computer crash so I have to force it to shutdown. Even if I try with a bssid or a target id which doesn't exist I have this result. I have the same when I try

-ng start wlp3s0

so I think it's because of my interface but I searched and I can't find anything that can help me

I earlier asked a question [Wifi isnt working after using wifite [duplicate]](https://unix.stackexchange.com/questions/640890/wifi-isnt-working-after-using-wifite) . [This](https://unix.stackexchange.com/a/435060/449077) and [this answer](https://unix.stackexchange.com/a/307784/449077) helped me. But, the problem is it works but, after few hours later when I start my laptop I get the same issue. I faces the [issue](https://unix.stackexchange.com/questions/640890/wifi-isnt-working-after-using-wifite) whenever I run codes on the . Then, reboot my laptop everything works fine. I am unable to fix the issue permanently. I didn't use wifite after facing the [issue that moment](https://unix.stackexchange.com/questions/640890/wifi-isnt-working-after-using-wifite) sudo airmon-ng check kill Output : Killing these processes PID Name 1394 wpa_supplicant sudo service NetworkManager restart sudo ifconfig wlan0 up Output : wlan0 : Error while getting interface flags : No such device sudo iwconfig wlan0 down Output : wlan0: ERROR while getting interface flags:No such device sudo ifconfig wlan0 up Output : wlan0 : ERROR while getting interface flags:No such device sudo aireplay-ng wlan0 Output : Please specify an attack mode. "aireplay-ng --help" for help I was trying to set wlan0 up. But, there was no wlan0 when I run ifconfig. When I restarted after running those commands. wlan0 was working correctly but, I have faced the multiple times. After running wifite few days ago. Even I have faced the issue again now... I think wifite status is keep running or something else is happening to it. iwconfig > lo no wireless extensions. > >eth0 no wireless extensions. > >wlan0 IEEE 802.11 ESSID:off/any > Mode:Managed Access Point: Not-Associated Tx-Power=15 dBm > Retry short limit:7 RTS thr:off Fragment thr:off > Power Management:off > >wwan0 no wireless extensions. > >docker0 no wireless extensions. ifconfig >docker0: flags=4099 mtu 1500 > inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 > ether 02:42:7d:19:b4:b6 txqueuelen 0 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > >eth0: flags=4099 mtu 1500 > ether f0:de:f1:da:7d:80 txqueuelen 1000 (Ethernet) > RX packets 0 bytes 0 (0.0 B) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 0 bytes 0 (0.0 B) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > device interrupt 20 memory 0xf2500000-f2520000 > >lo: flags=73 mtu 65536 > inet 127.0.0.1 netmask 255.0.0.0 > inet6 ::1 prefixlen 128 scopeid 0x10 > loop txqueuelen 1000 (Local Loopback) > RX packets 28 bytes 1728 (1.6 KiB) > RX errors 0 dropped 0 overruns 0 frame 0 > TX packets 28 bytes 1728 (1.6 KiB) > TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

I am using modified wifite for linux:https://github.com/derv82/wifite2 But i can't get it to work. I have instaled all necessary apps for wifite to work. Every time when i run it it give out: "Error: airmon-ng did not find any wireless interfaces" I am using lastest version of windows 10 Pro.

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'm running Fedora 31 Security Lab updated to the latest on Acer, with wireless driver ath10k_pci. The case is is that when i run airmon-ng there are no captured packets. Does the hardware is problematic or the driver? I've stopped the Network Manager , then ran airmon-ng check kill and then airmon-ng it shows that wlp3s0mon is started but nothing captured. Also tried without airmon. Checked iwlist and it does not show monitor but when i run iwconfig wlp3s0 mode monitor and check again with iwconfig it shows Mode:Monitor but still no captured packets. No errors in dmesg, rfkill is 'unblocked' and the adapter is detected and properly running when not in Monitor. I`ve read in the Qualcom's forum that QCA9377 can't operate in monitor but I was not sure because of the driver or the hardware.

I am using Termux in a Samsung Galaxy S6 Edge Plus (SM-G928C) running Lineage OS 1.14.1 and android version 7 with root (SuperSU). When I run

airmon -ng

, it throws the following error.

/data/data/com.termux/files/usr/bin/airmon-ng: 59: id: Permission denied
Unable to determine user id, permission errors may occur.
/data/data/com.termux/files/usr/bin/airmon-ng: 75: uname: Permission denied
/data/data/com.termux/files/usr/bin/airmon-ng: 110: wc: Permission denied
Your kernel has module support but you don't have modprobe installed.
It is highly recommended to install modprobe (typically from kmod).
/data/data/com.termux/files/usr/bin/airmon-ng: 183: ls: Permission denied

/data/data/com.termux/files/usr/bin/airmon-ng: 1202: ls: Permission denied
PHY     Interface       Driver          Chipset

Any idea on how to get it fixed?

> aireplay-ng -0 3 -a xx:xx:xx:xx mon0 15:31:35 Waiting for beacon frame (BSSID:xx:xx:xx:xx) on channel -1 15:31:35 Couldn't determine current channel for mon0, you should either force the operation with --ignore-negative-one or apply a kernel patch Please specify an ESSID (-e). I got this error in kali linux(Latest Version with update) while using the command ~#aireplay-ng -0 2 -a xx:xx:xx:xx:xx mon0 (De-authentication attack). So, what is this error and how to resolve. Thanks!

I'm new to Kali but I realy want to get into this so I tried some online tutorials refering to aircrack-ng. I am using 2 interfaces which are my wifi and a networkadapter (it's connected to the same WiFi than the first interface). However, everytime im using airmon-ng start [networkname] it keeps disconnecting my WiFi. could that be because of an invalid networkcard? or maybe because of the managed mode? wlx00223f942bc4 IEEE 802.11bgn ESSID:"JIxx0Ovqee1j" Mode:Managed Frequency:2.462 GHz Access Point: 08:76:FF:CB:C4:21 Bit Rate=18 Mb/s Tx-Power=30 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=70/70 Signal level=-40 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:1 Invalid misc:23 Missed beacon:0 wlp3s0 IEEE 802.11bgn ESSID:"JIxx0Ovqee1j" -->home wifi Mode:Managed Frequency:2.462 GHz Access Point: 08:76:FF:CB:C4:21 Bit Rate=18 Mb/s Tx-Power=15 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=56/70 Signal level=-54 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:145 Missed beacon:0 Problem (after using monitor mode): root@sney:/home/sney# airmon-ng start wlx00223f942bc4 Found 6 processes that could cause trouble. If airodump-ng, aireplay-ng or airtun-ng stops working after a short period of time, you may want to run 'airmon-ng check kill' PID Name 768 NetworkManager 795 avahi-daemon 829 avahi-daemon 1000 wpa_supplicant 1236 dhclient 2225 dhclient PHY Interface Driver Chipset phy0 wlp3s0 iwlwifi Intel Corporation Centrino Wireless-N 2200 (rev c4) phy1 wlx00223f942bc4 carl9170 NetGear, Inc. WN111(v2) RangeMax Next Wireless [Atheros AR9170+AR9101] Interface 15mon is too long for linux so it will be renamed to the old style (wlan#) name. (mac80211 monitor mode vif enabled on [phy1]wlan0mon (mac80211 station mode vif disabled for [phy1]wlx00223f942bc4)

I have awus1900 adapter and use kali linux on vmware Driver for awus1900 I installed from this site: **https://github.com/aircrack-ng/rtl8814au** Before switching the adapter to monitor mode, I entered the command

-ng check kill

My system is completely updated. I tried to switch to monitor mode using the

-ng start wlan0

command and manually. Both methods didn't work. My monitor interface: wlan0 When I tried to catch a handshake using the

-ng -c  --bssid  -w handshake wlan0

command, the program showed the message: *fixed channel wlan0: -1* I can enter the --ig flag in

-ng

, but, in this case, the

-ng

comand won't work for me. The comand:

-ng --deauth 3 -a  -c  -x 64 wlan0 --ig

will return this: 14:35:48 Waiting for beacon frame (BSSID: AC:9E:17:B1:5D:04) on channel -1 14:35:48 Sending 64 directed DeAuth (code 7). STMAC: [AE:A9:82:D6:C4:C3] [ 0| 0 ACKs] 14:35:49 Sending 64 directed DeAuth (code 7). STMAC: [AE:A9:82:D6:C4:C3] [ 0| 0 ACKs] 14:35:49 Sending 64 directed DeAuth (code 7). STMAC: [AE:A9:82:D6:C4:C3] [ 0| 0 ACKs] The program runs, but no effect Without --ig

-ng

doesn't work It returnes: 14:59:46 Waiting for beacon frame (BSSID: AC:9E:17:B1:5D:04) on channel -1 14:59:46 Couldn't determine current channel for wlan0, you should either force the operation with --ignore-negative-one or apply a kernel patch I don't know how to apply a kernel patch My Kali Linux version **5.10.0-kali7-amd64**

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?

I try to start wifite on VMware (Kali) but doesnt work, is there a possibility to use the local network card (Intel(R) Dual Band Wireless-AC 3168) to let search the VM for available networks? This is the error message i received: root@kali:~# wifite . . .´ · . . · `. wifite 2.2.5 : : : (¯) : : : automated wireless auditor . · /¯\ ´ · .´ https://github.com/derv82/wifite2 ` /¯¯¯\ ´ [!] Warning: Recommended app pyrit was not found. install @ https://github.com/JPaulMora/Pyrit/wiki [!] Warning: Recommended app hcxdumptool was not found. install @ https://github.com/ZerBea/hcxdumptool [!] Warning: Recommended app hcxpcaptool was not found. install @ https://github.com/ZerBea/hcxtools [!] Conflicting processes: NetworkManager (PID 555), wpa_supplicant (PID 739), dhclient (PID 1454) [!] If you have problems: kill -9 PID or re-run wifite with --kill) [+] Checking airmon-ng... [!] airmon-ng did not find any wireless interfaces [!] Make sure your wireless device is connected [!] See http://www.aircrack-ng.org/doku.php?id=airmon-ng for more info [!] Error: airmon-ng did not find any wireless interfaces [!] Full stack trace below [!] Traceback (most recent call last): [!] File "/usr/lib/python2.7/dist-packages/wifite/__main__.py", line 93, in entry_point [!] wifite.start() [!] File "/usr/lib/python2.7/dist-packages/wifite/__main__.py", line 53, in start [!] Configuration.get_monitor_mode_interface() [!] File "/usr/lib/python2.7/dist-packages/wifite/config.py", line 129, in get_monitor_mode_interface [!] cls.interface = Airmon.ask() [!] File "/usr/lib/python2.7/dist-packages/wifite/tools/airmon.py", line 299, in ask [!] raise Exception('airmon-ng did not find any wireless interfaces') [!] Exception: airmon-ng did not find any wireless interfaces [!] Exiting*

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.

on my host pc there is showing some wlan networks with my wlan adapter tp-link AC1300. But in kali (my virtual machine) there are no networks at all. And yes it is in monitor mode and also detected. I would like to monitor my own network. But it does not show it. My AP is in my room. How can I fix this? Thank you

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.

Method 1: Airmon-ng - (don't work)

airmon-ng check kill
airmon-ng start wlan0

- Make wlan0mon, everything looks fine, but after some time (around 50 seconds) using some tools like airgeddon or airlay-ng, my Raspberry start lagging. For example if I type iwconfig I must wait 6 seconds to show respond from Raspberry and tools stopped working when I try to stop wlan0mon or start Network Manager it also doesn't work. When I type top, there isn't any high recourse process what can cause lagging.

Method 2: Iwconfig - (don't work)

ifconfig wlan0 down
iwconfig wlan0 mode monitor
ifconfig wlan0 up
- Normally change to monitor mode, but when I try some tools like airgeddon or airplay-ng it says some errors and I can't use them.

Info

- I tried reinstall whole Kali Linux
- Reinstall firmware: apt install --reinstall kalipi-re4son-firmware
- apt-get update
- apt-get full-upgrade
- apt install -y kali-linux-large

Is it some software issue or hardware issue or do I need to buy some Wi-Fi adapter?
Thanks for answering, any help is really appreciated, I'm just beginner with Kali Linux and Raspberry.

I'm using Intel (R) Dual Band Wireless-AC 8260 on my laptop and installed Kali Linux 2020.2 on virtual box. My problem is when I run sudo airmon-ng it doesn't get detected, I get no output under PHY, Interface, Driver or Chipset. But on Ubuntu 20.04 installed on my HDD when I run the same command I get PHY(phy0), Interface(wlp2s0), Driver(iwlwifi), Chipset(Intel Corporation Wireless 8260 (rev 3a)). How can I get Kali Linux on virtual box to detect my Wi-Fi card? I already installed the firmware through sudo apt-get install firmware-iwlwifi and it's in the newest version.

I've seen a lot of tutorials on how to crack a WPA/WPA2 Network using Reaver or Aircrack-Ng on Kali Linux. However, neither of these tools work for me. With Reaver, after it switches to the correct channel (after a decent amount of time switching between channels), it just freezes and doesn't output anything, even with -vv as an option. With the Aircrack-Ng method, I never see a WPA handshake after sending a deauth package. If this isn't the right place to ask about this, where should I ask for help on this? If this is the right place, what can I do about this? Here is a picture from my iPhone that shows what pops up in my virtual console 1 after booting up. Everything above the part for entering the login shows up during boot, everything after that shows up after boot. I don't know if this has anything to do with it, but it may. Regardless, does this pose any problem for my Kali Linux? I am running Kali Linux ***2.0*** on an ext4 partition. If the installation process of Kali Linux makes a difference, it is contained in my post here: [Warning while Booting into Ubuntu](https://unix.stackexchange.com/questions/237072/warning-while-booting-into-ubuntu) . This post of mine contains the warnings I get while booting into Ubuntu, which are similar to that of booting into Kali Linux. So I guess I have two questions: 1. Where can I get help using tools like Reaver or Aircrack-ng? 2. Are the warnings in the image anything I need to worry about? EDIT: Here is information requested about the errors: For the ext4 one, my installation completed successfully. It ended saying that I could reboot into Kali now. However, if you look in the link I provided, it shows about my installation procedure, and there were some parts that I believe were not that significant that I could not see any options for, as part of the installer was cut off on my display, but I'm not sure if that was the problem. My Wifi connection works fine, as I am posting from Kali Linux. However, I can just try sudo apt-get if I must. I don't know what the name is for the iwlwifi firmware. I just tried running the command regarding the openvas-scanner, and then with the -l option, which it said to show extra information, and this is the output: sudo systemctl status openvas-scanner.service -l ● openvas-scanner.service - Open Vulnerability Assessment System Scanner Daemon Loaded: loaded (/lib/systemd/system/openvas-scanner.service; enabled) Active: failed (Result: exit-code) since Sun 2015-10-18 20:08:25 PDT; 21h ago Docs: man:openvassd(8) http://www.openvas.org/ Process: 742 ExecStart=/usr/sbin/openvassd --listen=127.0.0.1 --port=9391 (code=exited, status=1/FAILURE) Oct 18 20:08:25 kali systemd: openvas-scanner.service: control process exited, code=exited status=1 Oct 18 20:08:25 kali systemd: Failed to start Open Vulnerability Assessment System Scanner Daemon. Oct 18 20:08:25 kali systemd: Unit openvas-scanner.service entered failed state. EDIT If it makes a difference, my Kali Linux is on a ***logical*** ext4 partition. I also installed Kali grub the second time going through, which is what is run now instead of my Ubuntu grub. This is the output from lsusb: Bus 001 Device 004: ID 0a5c:5801 Broadcom Corp. BCM5880 Secure Applications Processor with fingerprint swipe sensor Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 8087:8000 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 1bcf:2985 Sunplus Innovation Technology Inc. Laptop Integrated Webcam HD Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub And the output from lspci: 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b) 00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04) 00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04) 00:16.3 Serial controller: Intel Corporation 8 Series HECI KT (rev 04) 00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I218-LM (rev 04) 00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4) 00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4) 00:1c.4 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 5 (rev e4) 00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04) 00:1f.2 RAID bus controller: Intel Corporation 82801 Mobile SATA Controller [RAID mode] (rev 04) 00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04) 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev 73) 03:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) I apologize if this is in a difficult-to-understand format.

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