windmaple: There are some major problems in your configuration:
1. do not use aircrack-ng tools or scripts in combination with hcxtools.
airmon-ng creates a virtual interface (monx) and leaves wlan0 managed!
2. do not use wlandump-ng/wlanresponse on virtual devices like monx
"I placed the wifi card into monitor mode but somehow wlandump doesn't like wlan0"
wlandump-ng/wlanresponse likes wlan0, but they don't like virtual devices!
3. as freeroute wrote, you must identify all services that takes access to your capture device and stop them (at least this 2):
sudo systemctl stop NetworkManager.service
sudo systemctl stop wpa_supplicant.service
4. as freeroute wrote, you must put the interface into monitor mode (where $WLANDEV is your device name)
sudo ip link set $WLANDEV down
sudo iw dev $WLANDEV set type monitor
sudo ip link set $WLANDEV up
sudo iw dev $WLANDEV info
5. if you got pcap read errors like this:
internal pcap errors.....................................: 12
there are more services that prevent wlandump-ng/wlanresponse to access the device - you must identify and stop them.
6. if you finished capturing do not forget to put the device back into managed mode
sudo ip link set $WLANDEV down
sudo iw dev $WLANDEV set type managed
sudo ip link set $WLANDEV up
sudo iw dev $WLANDEV info
7. and start the services - otherwise you will have no connectivity!
sudo systemctl start NetworkManager.service
sudo systemctl start wpa_supplicant.service
I prefer ip in combination with iw which is much more powerful than ifconfig (archlinux dropped support for deprecated ifconfig “net-tools” sometime back).
Read about the difference between both tools here:
https://www.tecmint.com/ifconfig-vs-ip-c...iguration/
https://p5r.uk/blog/2010/ifconfig-ip-comparison.html
1. do not use aircrack-ng tools or scripts in combination with hcxtools.
airmon-ng creates a virtual interface (monx) and leaves wlan0 managed!
2. do not use wlandump-ng/wlanresponse on virtual devices like monx
"I placed the wifi card into monitor mode but somehow wlandump doesn't like wlan0"
wlandump-ng/wlanresponse likes wlan0, but they don't like virtual devices!
3. as freeroute wrote, you must identify all services that takes access to your capture device and stop them (at least this 2):
sudo systemctl stop NetworkManager.service
sudo systemctl stop wpa_supplicant.service
4. as freeroute wrote, you must put the interface into monitor mode (where $WLANDEV is your device name)
sudo ip link set $WLANDEV down
sudo iw dev $WLANDEV set type monitor
sudo ip link set $WLANDEV up
sudo iw dev $WLANDEV info
5. if you got pcap read errors like this:
internal pcap errors.....................................: 12
there are more services that prevent wlandump-ng/wlanresponse to access the device - you must identify and stop them.
6. if you finished capturing do not forget to put the device back into managed mode
sudo ip link set $WLANDEV down
sudo iw dev $WLANDEV set type managed
sudo ip link set $WLANDEV up
sudo iw dev $WLANDEV info
7. and start the services - otherwise you will have no connectivity!
sudo systemctl start NetworkManager.service
sudo systemctl start wpa_supplicant.service
I prefer ip in combination with iw which is much more powerful than ifconfig (archlinux dropped support for deprecated ifconfig “net-tools” sometime back).
Read about the difference between both tools here:
https://www.tecmint.com/ifconfig-vs-ip-c...iguration/
https://p5r.uk/blog/2010/ifconfig-ip-comparison.html