1

Whenever I try to use airmon-ng start wlan0, only the same thing as executing airmon-ng check happens, so mon0 isn't created. Here are dumps of what happened, when I entered ifconfig and iwconfig:

ifconfig

lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 0 (Local Loopback) RX packets 22 bytes 1316 (1.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 22 bytes 1316 (1.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099 mtu 1500 ether 00:e0:4c:72:00:1e 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

iwconfig

wlan0 unassociated Nickname:"rtl_wifi" Mode:Managed Access Point: Not-Associated Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0 Signal level:0 Noise level:0 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.

eth0 no wireless extensions.

If you need any more info to solve the problem, just ask

1

Do your wireless chipset and drivers support monitor mode? You can check with this command:

iw [your-wifi-adaptor-eg-phy0] info

or this

iw list

if you're unsure.

Posting that info will help. Here's an example of a snippet from my output: Supported interface modes: * IBSS * managed * AP * AP/VLAN * WDS * monitor * mesh point As you can see, the chipset on my machine would support it.

0

After checking using iw list and confirming it has monitor mode listed in there.

If monitor mode is listed then try iw config wlan0 mode monitor and this should put your wlan0 into monitor mode.

Your Answer

By clicking "Post Your Answer", you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.