Wifite stuck at enabling monitor mode on wlan0

[darkmatter1505]

Cloned the latest from github, started it with ./Wifite.py and I get the opening screen and then it looks for wireless interfaces, finds the only wireless interface, wlan0 and it sitting at [+] enabling monitor mode on Wlan0...

It's been sitting at this for over 15 minute and nothing has happened.

[kimocoder]

@darkmatter1505 which Wi-Fi chipset are you using?

[darkmatter1505]

Intel centrino built in to a Lenovo p450 laptop

Dark Matter

---

From: Christian B. notifications@github.com Sent: Tuesday, February 27, 2018 11:46:26 AM To: derv82/wifite2 Cc: DarkMatter1505; Mention Subject: Re: [derv82/wifite2] Wifite stuck at enabling monitor mode on wlan0 (#67)

@darkmatter1505https://github.com/darkmatter1505 which Wi-Fi chipset are you using?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/derv82/wifite2/issues/67#issuecomment-368964593, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AL5dl5fnzzOMXg-k14RCNuLkyh4fXBmAks5tZD9fgaJpZM4SVN5y.

[kimocoder]

chipset is found by running "airmon-ng" standalone. run it and check under "chipset"

[darkmatter1505]

Intel corporation centrino ultimate-N 6300 rev 3e

Dark Matter

---

From: Christian B. notifications@github.com Sent: Tuesday, February 27, 2018 11:57:47 AM To: derv82/wifite2 Cc: DarkMatter1505; Mention Subject: Re: [derv82/wifite2] Wifite stuck at enabling monitor mode on wlan0 (#67)

chipset is found by running "airmon-ng" standalone. run it and check under "chipset"

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/derv82/wifite2/issues/67#issuecomment-368968376, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AL5dl_Np4yyR01jGO3zl4Ssqt2So1bEGks5tZEIbgaJpZM4SVN5y.

[derv82]

What operating system are you using?

Have you successfully put the device into monitor mode before?

What is the output when you run airmon-ng?

What is the output when you run airmon-ng start Wlan0?

[kimocoder]

According to this it's the iwlwifi, and last time i checked (5 hours ago) iwlwifi chipset was working. Have this as my internal myself. Lets see the output

[darkmatter1505]

here is the output:

airmon-ng start wlan0

PHY Interface Driver Chipset

phy0 wlan0 iwlwifi Intel Corporation Centrino Ultimate-N 6300 (rev 3e)

    (mac80211 monitor mode vif enabled for [phy0]wlan0 on

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

ifconfig:

wlan0mon: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 unspec 24-77-03-DE-03-0C-30-3A-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC) RX packets 188 bytes 46326 (45.2 KiB) RX errors 0 dropped 188 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

On Tue, Feb 27, 2018 at 12:23 PM, Christian B. notifications@github.com wrote:

According to this https://wikidevi.com/wiki/Intel_Centrino_Ultimate-N_6300 it's the iwlwifi, and last time i checked (5 hours ago) iwlwifi chipset was working. Have this as my internal myself. Lets see the output

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/derv82/wifite2/issues/67#issuecomment-368976522, or mute the thread https://github.com/notifications/unsubscribe-auth/AL5dlwITGKW27iosNiIOdrvW10isBg_uks5tZEgbgaJpZM4SVN5y .

[derv82]

What operating system are you using?

Have you successfully put the device into monitor mode before?

[kimocoder]

As the "iwconfig" output says, "airmon-ng" sets monitor mode just fine. I'm using Kali (2018.2) using the same chipset + iwlwifi and it works just fine over here.

The driver itself, has to support "virtual interface" in order to have airmon-ng working and "iwlwifi" supports it, so this 'could' be either an OS issue or simply a user error.

[darkmatter1505]

I'm using the latest Kali 2018.

Dark Matter

---

From: derv notifications@github.com Sent: Wednesday, February 28, 2018 12:23:38 AM To: derv82/wifite2 Cc: DarkMatter1505; Mention Subject: Re: [derv82/wifite2] Wifite stuck at enabling monitor mode on wlan0 (#67)

What operating system are you using?

Have you successfully put the device into monitor mode before?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/derv82/wifite2/issues/67#issuecomment-369134922, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AL5dl2LaYGLcp2ME3Fevp-iUS9BKWmnjks5tZPDpgaJpZM4SVN5y.

[Ashish-dawani]

i was having same issue and i used this command and it fixed it 👍 sudo rfkill unblock all

[derv82]

I wonder if the problem is the additional new-line characters that are present in the output provided by @darkmatter1505

airmon-ng start wlan0

PHY    Interface    Driver        Chipset

phy0    wlan0        iwlwifi        Intel Corporation Centrino Ultimate-N
6300 (rev 3e)

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

---

It would help to know exactly what airmon-ng prints out when Wifite executes the command.

Can you re-run Wifite with the -vv switch? This enables verbose output, including the airmon-ng start ... command and the output of that command.

You should see something like this in the (verbose) Wifite output:

[Shahzod111]

hello everyone help me show prism0

root@kali:~# airmon-ng start wlan0

Found 4 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 487 NetworkManager 543 wpa_supplicant 3948 dhclient 3992 dhclient

PHY Interface Driver Chipset

phy0 wlan0 wl Broadcom Limited BCM43142 802.11b/g/n (rev 01)

    (experimental wl monitor mode vif already enabled for [phy0]wlan0 on [phy0]prism0)

[Blompus]

I had this same problem using the alfa awus036ACH. This device doesn't allow airmon to put it in monitoring mode using the start command, but using the following it is possible:

> ifconfig wlan0 down
> iwconfig wlan0 mode monitor
> ifconfig wlan0 up

It then works with airodump, but wifite refuses to recognize that the interface is in monitor mode. Using the wifite -vv, I noticed wifite checks the 'iw dev' command to check for a monitoring interface. This continues to give a 'type: managed' output, even though the iwconfig shows it as in monitoring mode and other applications are able to use the monitoring capabilities (airodump).

By using the following commands to set the iw type to monitoring I managed to pass the checks wifite does to start monitoring:

> sudo ip link set wlan0 down
> sudo iw wlan0 set monitor control
> sudo ip link set wlan0 up

[37y]

I had this same problem using the alfa awus036ACH. This device doesn't allow airmon to put it in monitoring mode using the start command, but using the following it is possible:

> ifconfig wlan0 down
> iwconfig wlan0 mode monitor
> ifconfig wlan0 up

It then works with airodump, but wifite refuses to recognize that the interface is in monitor mode. Using the wifite -vv, I noticed wifite checks the 'iw dev' command to check for a monitoring interface. This continues to give a 'type: managed' output, even though the iwconfig shows it as in monitoring mode and other applications are able to use the monitoring capabilities (airodump).

By using the following commands to set the iw type to monitoring I managed to pass the checks wifite does to start monitoring:

> sudo ip link set wlan0 down
> sudo iw wlan0 set monitor control
> sudo ip link set wlan0 up

Had to comment to thank you for this information, worked perfectly for me and i was having the same issues. Thank you.

[kyl3p3tri3]

i was having same issue and i used this command and it fixed it 👍 sudo rfkill unblock all

this worked for me. Thanks @Ashish-dawani

[soyeb-sec]

It's worked for me. Thanks...... @Blompus