View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002579Kali LinuxKali Package Bugpublic2015-08-21 04:212015-08-21 13:58
Reporterbkarnes Assigned Tomuts  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Versionkali-dev 
Summary0002579: Wifite kills wlan0 after use
Description

After using wifite on the commandline, the network tools function (system settings) doesn't work. The wireless card still shows up when doing ifconfig, but can not connect to any access points or even view the network settings dialogue (system settings).

Steps To Reproduce

Start up Kali VM (Using VirtualBox, but does same in VMware and regular install)

Show Wireless networking settings
See Screenshot (WirelessSettings-BeforeWifite-ifconfig.png)

Show Ifconfig (WirelessSettings-BeforeWifite-ifconfig.png)
root@kali:~# ifconfig

wlan0     Link encap:Ethernet  HWaddr 00:c0:ca:69:05:b1  
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Run wifite -mac -i wlan0 (WifiteAndIfconfig.png)
root@kali:~# wifite -mac -i wlan0

  .;'                     `;,    
 .;'  ,;'             `;,  `;,   WiFite v2 (r87)
.;'  ,;'  ,;'     `;,  `;,  `;,  
::   ::   :   ( )   :   ::   ::  automated wireless auditor
':.  ':.  ':. /_\ ,:'  ,:'  ,:'  
 ':.  ':.    /___\    ,:'  ,:'   designed for Linux
  ':.       /_____\      ,:'     
          /       \             

 [+] mac address anonymizing enabled
     not: only works if device is not already in monitor mode!
 [+] set interface: wlan0

 [+] scanning for wireless devices...
 [!] could not find wireless interface "wlan0" in monitor mode
 [+] changing wlan0's MAC from 00:c0:ca:69:05:b1 to 00:c0:ca:76:b8:b6... done
 [+] enabling monitor mode on wlan0... done
 [+] initializing scan (wlan0mon), updates at 5 sec intervals, CTRL+C when ready.
 [0:00:25] scanning wireless networks. 0 targets and 0 clients found

Checked Ifconfig while wifite is running (WifiteAndIfconfig.png)
root@kali:~# ifconfig

wlan0mon  Link encap:UNSPEC  HWaddr 00-C0-CA-69-05-B1-3A-30-00-00-00-00-00-00-00-00  
         UP BROADCAST NOTRAILERS RUNNING PROMISC ALLMULTI  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Didn't find any hosts after a few seconds, killed (Ctrl-C) wifite (WifiteAndIfconfig.png)

 [!] no targets found!
 [!] you may need to wait for targets to show up.

 [+] disabling monitor mode on wlan0mon... done
 [+] changing wlan0's mac back to 00:c0:ca:69:05:b1... done
 [+] quitting

root@kali:~# ifconfig

Looked at Wireless Network Settings again, nothing
See screenshot (WirelessSettings-AfterWifite-NoWorkie.png)

Ran Ifconfig again to see if wireless is still there:
root@kali:~# ifconfig

wlan0     Link encap:Ethernet  HWaddr 00:c0:ca:69:05:b1  
         UP BROADCAST MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000 
         RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

Brought down and up the wlan0 (command line) - no joy

Rebooted VM and once back up, can get to wireless network settings again

I then tried the same process again (as above) after killing the conflicting processes (wpa_supplicant - using airmon-ng check & airmon-ng check kill). Performed the same steps as above with the same results, except it allowed me to view the surrounding wireless targets when kicking off wifite.

Activities

muts

muts

2015-08-21 12:33

reporter   ~0003819

Last edited: 2015-08-21 12:33

We don't develop wifite. You're better off submitting a bug with the developers, or supplying a patch yourself.
bkarnes

bkarnes

2015-08-21 13:23

reporter   ~0003820

This happens with the version that is in the Kali Repos as well as the up to date version from GitHub. Wifite works in the Kali 1.x series without any issues (both from the repo as well as GitHub). I would think that if it was a wifite issue, it would not work in the Kali 1.x series and would show the same results.
muts

muts

2015-08-21 13:26

reporter   ~0003821

Last edited: 2015-08-21 13:29

And still, we do not develop wifite and will not chase down this issue. Unless you have descriptive and informative bug to report, this issue will remain closed.

Also note, changes in how aircrack-ng places cards in monitor mode has had some effects on how wifite should be used. For example, putting the card in monitor mode manually before running wifite seems to solve many issues. Also, gnome networking features should not be expected to integrate with manual entry / exit of a card into monitor mode.

Issue History

Date Modified Username Field Change
2015-08-21 04:21 bkarnes New Issue
2015-08-21 12:33 muts Note Added: 0003819
2015-08-21 12:33 muts Status new => closed
2015-08-21 12:33 muts Assigned To => muts
2015-08-21 12:33 muts Resolution open => no change required
2015-08-21 12:33 muts Note Edited: 0003819
2015-08-21 13:23 bkarnes Note Added: 0003820
2015-08-21 13:23 bkarnes Status closed => feedback
2015-08-21 13:23 bkarnes Resolution no change required => reopened
2015-08-21 13:26 muts Note Added: 0003821
2015-08-21 13:26 muts Status feedback => closed
2015-08-21 13:26 muts Resolution reopened => no change required
2015-08-21 13:28 muts Note Edited: 0003821
2015-08-21 13:29 muts Note Edited: 0003821