Aircrack-ng forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Aircrack-ng 1.7 release

Sorry Guest, you are banned from posting and sending personal messages on this forum.
This ban is not set to expire.
Pages: [1]   Go Down

Author Topic: Edit NewtorkManager.conf to prevent conflicts with airmon-ng (no check kill)  (Read 16266 times)

kcdtv

  • Experienced
  • Full Member
  • ********
  • Offline Offline
  • Posts: 212

  This solution may be ugly but it is very straightforward and efficient with immediate effects.
As we have all noticed; since the version 0.9.8.10 of Network manager we cannot activate properly monitor mode.
It has nothing to do with airmon-ng or the distribution that you use : Network Manager "takes" the control back on any interface and disable monitor mode
(snapshot made under Xubuntu 15.04 and aircrack-ng "svn" revision nº 2677)

 As the interfaces called "wlan-number-mon" are designed to be used only in monitor mode we can "help" airmon-ng to maintain the monitor mode by creating some exceptions in our NewtorkManager.conf file

STEP 1

  Open your NewtorkManager.conf file as root
Code: [Select]
(sudo) gedit /etc/NetworkManager/NetworkManager.confif you are root you don't need "sudo".  if you have "leafpad" but not "gedit"; just write "leafpad" instead of "gedit", If you don't have any text editor use "nano". If you are insane use "vim".  :P 


STEP 2

Add the following lines at the end of your file
Code: [Select]
[keyfile]
unmanaged-devices=interface-name:wlan0mon;interface-name:wlan1mon;interface-name:wlan2mon;interface-name:wlan3mon;interface-name:wlan4mon;interface-name:wlan5mon;interface-name:wlan6mon;interface-name:wlan7mon;interface-name:wlan8mon;interface-name:wlan9mon;interface-name:wlan10mon;interface-name:wlan11mon;interface-name:wlan12mon                               # 30/08/2015: avoid conflicts with airmon-ng
You can put as many interface as you wish as long as you use the separator ; between every interface.


STEP 3

Save the changes and enjoy. You can immediately use airmon-ng without problems


PS :
  - Thanks to USUARIONUEVO for opening this thread ( Kali 2.0 evitar que networkmanager nos *robe las interfaces en monitor )and bringing on all his expertise :
  - Tip previously published in Modificación del fichero NetworkManager.conf para arreglar airmon-ng and in Solve arimon-ng issues by a simple modfication of NetworkManager.conf
« Last Edit: August 30, 2015, 06:46:03 pm by kcdtv »
Logged

polomarko

  • Guest

This only work if you have TWO WiFi  adapters.  Your screenshots shows Atheros and Ralink.
 What about if we have only one?
Logged

kcdtv

  • Experienced
  • Full Member
  • ********
  • Offline Offline
  • Posts: 212

You missed the point   :)
This works with one, two, three, four, five... all the interfaces you want...  ;)
Network manager ignore all the wlanXmon (from wlan0mon to wlan12mon, you can put more if you want) interfaces.
It will manages only the wlanX (managed mode interface)
If you have a single interface it is likely to be wlan0 and will become wlan0mon in monitor mode.
It will be ignored by Network manager and you will not have conflict
Chipset is irrelevant here: It is a matter of identifier (wlan) and by ignoring from wlan0mon to wlan12mon you cover any kind of realistic case (do you have 14 USB plug on the same computer? If yes had wlan13mon and it wil be ok)
Notice that this post is more than one year old and if you use an updated system it is not necesary anymore (no more conflict with airmon-ng and network manager)
Logged

cavaNN

  • Newbie
  • *
  • Offline Offline
  • Posts: 1

I Have the latest kali and i frequently upgrade all the tools yet this conflict between Network Manager and airmon-ng is still present, any suggestions ??
I
Logged
Pages: [1]   Go Up