Results 1 to 7 of 7

Thread: Solve arimon-ng issues by a simple modfication of NetworkManager.conf

  1. #1
    Join Date
    2013-Sep
    Posts
    264

    Solve arimon-ng issues by a simple modfication of NetworkManager.conf

    About the conflict between airmon-ng and NetwrokManager

    You may have seen a lot of posts and topics these days about "problems with airmon-ng in Kali sana."
    The mode monitor interface created by airmon-ng doesn't work and we need to use "airmon-ng check kill", which is very annoying as it simply totally stop network manager and doesn't allow us to be connected with another interface.


    First it is good to know that it is not an issue specific to Kali linux or that it is related to the "new airmon-ng" interfaces.
    The problem is a general issue for any GNU-Linux distribution and occurs with all aircrack-ng version since it is caused by NetworkManager
    Thanks to USUARIONUEVO (cf Kali 2.0 evitar que networkmanager nos *robe las interfaces en monitor) we know that the conflict is generated by version superior to 0.9.8.10
    Downgrading Network Manger would solve the issue but it is not an option.

    Editing /etc/NetworkManager/NetworkManager.conf

    This solution is "ugly" but logical and seems to be very safe with no mistake possible. Effects are inmediate.
    With airmon-ng we create an interface called wlanXmon. It is only dedicated to monitor mode and it is not suposed to be handled by network manager. The problem is that Network Manager always take back the control over our wlanXmon interfaces due to some recents changes.
    Let's help airmon-ng a little to keep the control on the interface by adding exceptions in our Network Manager' file.

    1 : Open your /etc/NetworkManager/NetworkManager.conf file as root
    Code:
    sudo leafpad /etc/NetworkManager/NetworkManager.conf
    2 : Add the following lines to your file
    Code:
    [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 -  https://forums.kali.org/showthread.php?27091-Solve-arimon-ng-issues-by-a-simple-modfication-of-NetworkManager-conf
    3 : Save the modification. You are now able to use airmon-ng as it should be; without any need to force it by "check killing" everything


    It is not an elegant solution, but very straightforward.
    You can put how many wlanXmon interfaces you want. I put 12 : it should be enough if you don't use many different dongles.
    Notice that the symbol used as a separator between the interfaces is ;

    Tip previously published (in Spanish) in Modificación del fichero NetworkManager.conf para arreglar airmon-ng
    Last edited by kcdtv; 2015-09-28 at 16:19.

  2. #2
    Join Date
    2015-Aug
    Location
    The Pits
    Posts
    86
    Hello kcdtv, this is the bee's knees! THANK YOU!

  3. #3
    Join Date
    2013-Jul
    Location
    United States
    Posts
    520
    AH! Thanks buddy!

  4. #4
    Join Date
    2015-Sep
    Posts
    3
    Finally! Glad we sorted that out! Thanks mate!
    __________________
    if a thing is worth doing, its worth doing right...

  5. #5
    Join Date
    2015-Sep
    Posts
    2
    I find it quite elegant indeed. Thanks mate for sharing.

  6. #6
    Join Date
    2016-Jul
    Posts
    3
    Great solution! Thank you very much. One addition I would make-- if you have two dedicated devices and use wlan0 for internet and wlan1 solely for monitoring, you can just add "interface-name:wlan1;" to the .conf file as an unmanaged interface. Saves the effort of creating a wlan1mon interface.

  7. #7
    Join Date
    2016-Oct
    Posts
    2
    I have tried this solution, yet whenever I try to run programs which require monitoring and Internet my wlan0 disappears. I only use two interfaces so I took raellic advice and it was a no-go. Suggestions?

Similar Threads

  1. Reaver modfication for Pixie Dust Attack
    By t6_x in forum Project Archive
    Replies: 106
    Last Post: 2017-02-10, 18:51
  2. Replies: 2
    Last Post: 2015-08-19, 02:02
  3. Reaver modfication for Pixie Dust Attack
    By t6_x in forum General Archive
    Replies: 81
    Last Post: 2015-05-05, 00:55

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •