Messing wth Kali 6 months plus, never seen this error ?

[lanane]

O.K. I'm not a Linux pro but this is a fairly simple command.

One thing I will note : This is a clean install, I screwed my other install up trying to get ... Not Cuda but the OS version of it going. Anyways. Here it is :

root@Kali:~# airmon-ng stop wlan0

PHY	Interface	Driver		Chipset

phy0	wlan0		rtl8188ee	Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)

You are trying to stop a device that isn't in monitor mode.
Doing so is a terrible idea, if you really want to do it then you
need to type 'iw wlan0 del' yourself since it is a terrible idea.
Most likely you want to remove an interface called wlan[0-9]mon
If you feel you have reached this warning in error,
please report it.

root@Kali:~#

Same thing happens on my Wlan1 which has injection capabilities. Althought I never had problems putting wlan0 in monitor mode.

I can override it but then in iwconfig it shows a weird monitor .. Something like mon0monmon ... And it doesn't work when I try to capture handshakes

P.S. I did do ....

apt-get clean

apt-get update

apt-get upgrade

apt-get dist-upgrade

Also prior to running Airmon, below was status :

root@Kali:~# iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"ATT"  
          Mode:Managed  Frequency:2.427 GHz  Access Point: 22: 56: 22: 9E: A0: 22   
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-38 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:158   Missed beacon:0

lo        no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off

P.S. Code command would be nice on main page. I looked for it, but didn't know I had to go advanced

[kcdtv]

good evening
if you write

airmon-ng stop wlan0

you are not enabling the monitor mode but stoping it.
As your interface is not in monitor mode (you can see "managed") you logically get this error message
cheers

[lanane]

For some reason I remember the instructions on a "how to" saying to disable your wireless card you want to put into monitor mode before enabling it. I also thought it worked before, ie

airmon-ng stop wlan0
airmon-ng start wlan0

Then it went into monitor mode. I also seem to remember it working in a VM - I might be wrong though.

Anyways, I just went ahead and entered

airmon-ng start wlan0
airmon-ng start wlan1

Without disabling them first

Even though wlan0 doesn't support injection.

This is what I get instead of just mon0 and mon1 like I used to get :

Code :

root@Kali:~# iwconfig
wlan1mon  IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
eth0      no wireless extensions.

wlan0mon  IEEE 802.11bgn  ESSID:"ATT"  
          Mode:Managed  Frequency:2.427 GHz  Access Point: 58:56:E8:9E:A0:30   
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-28 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

lo        no wireless extensions.

So they aren't in monitor mode, and my internet connection wasn't even temporarily disconected. I swear the command to put it into monitor mode was airmon-ng start wlan(x) after I disabled them with airmon-ng stop wlan(x). In fact, I even have it saved in a "Quick How to Capture 4 way handshake" gedit file I saved and emaailed to myself with some captures it did work on. Of course, after other commands.

Sorry if there is some obvious answer here, but I actually remember this working for sure before.

[lanane]

root@Kali:~# iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"ATT"  
          Mode:Managed  Frequency:2.427 GHz  Access Point: 58:56:E8:9E:A0:30   
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-24 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:46   Missed beacon:0

lo        no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
root@Kali:~# airmon-ng
PHY	Interface	Driver		Chipset

phy0	wlan0		rtl8188ee	Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
phy1	wlan1		rt2800usb	Ralink Technology, Corp. RT5372

root@Kali:~# iwconfig
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"ATT"  
          Mode:Managed  Frequency:2.427 GHz  Access Point: 58:56:E8:9E:A0:30   
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-24 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:47   Missed beacon:0

lo        no wireless extensions.

wlan1     IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
root@Kali:~# 
root@Kali:~# airmon-ng
PHY	Interface	Driver		Chipset

phy0	wlan0		rtl8188ee	Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
phy1	wlan1		rt2800usb	Ralink Technology, Corp. RT5372

root@Kali:~# airmon-ng start wlan1
Found 5 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 kill (some of) them!

  PID Name
  761 NetworkManager
  852 wpa_supplicant
  879 dhclient
 1059 avahi-daemon
 1060 avahi-daemon

PHY	Interface	Driver		Chipset

phy0	wlan0		rtl8188ee	Realtek Semiconductor Co., Ltd. RTL8188EE Wireless Network Adapter (rev 01)
phy1	wlan1		rt2800usb	Ralink Technology, Corp. RT5372
		(mac80211 monitor mode vif enabled for [phy1]wlan1 on [phy1]wlan1mon)
		(mac80211 station mode vif disabled for [phy1]wlan1)


root@Kali:~# iwconfig
wlan1mon  IEEE 802.11bgn  ESSID:off/any  
          Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          
eth0      no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"ATT"  
          Mode:Managed  Frequency:2.427 GHz  Access Point: 58:56:E8:9E:A0:30   
          Bit Rate=72.2 Mb/s   Tx-Power=20 dBm   
          Retry short limit:7   RTS thr=2347 B   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=70/70  Signal level=-24 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:50   Missed beacon:0

lo        no wireless extensions.

Even though it wasn't in monitor mode I gave it a shot,

root@Kali:~# 
root@Kali:~# airodum-ng wlan1mon
bash: airodum-ng: command not found
root@Kali:~# airodump-ng wlan1mon
ioctl(SIOCSIWMODE) failed: Device or resource busy

ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead.  Make
sure RFMON is enabled: run 'airmon-ng start wlan1mon <#>'
Sysfs injection support was not found either.

root@Kali:~#