Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: Why having Network manager and tons of conflict instead of wicd (and no conflicts)?

  1. #1
    Senior Member
    Join Date
    Sep 2013
    Posts
    262

    Why having Network manager and tons of conflict instead of wicd (and no conflicts)?

    In our GNU-Linux world Network Manager became the default solution in the vast majority of distribution
    I guess this choice is mainly due to the lack of alternatives.
    Network manger may have a nice design but it deamons is absolutely terrible and since system.d imposed itself it is more buggy than ever
    As we all know we have to turn it off to be able to pass properly monitor mode with airmon-ng (with check kill )
    That's very annoying
    If we dig a little we will see that netwrok manger
    - doesn't allow to change mac to connect to an access point
    - doesn't let ifconfig switch on or off an interface
    - in kali 2016.1 (specific and very annoying bug) it simply doesn't allow you to use a single wifi interface if you use two. Or boithes are switched off or bothes are switched on
    To say it simply, network manger doesn't let the user to have a control on its interfaces.

    If these features may not interest a regular user of ubuntu or linux mint, it is not the case for a pentester...
    ...Not so far ago wicd was the default network aplication in backtrack

    The wicd project is maybe less famous and may look a bit "abandoned" as iut has a new version every two year
    But it is stable, reliable and absolutly conflictless with other command line tool

    Some may argue that it is less fancy and trendy then gome netwrok manager...
    But should that be a priority in pentest distribution? (that a rhetoric question in case you didn't get it )
    wicd is a python open source code and its design can be simply adapted (gtk) to kali linux look

    I really wonder how network manger could have been choosen by kali team and how can't this big lack of functionalism hasn't been detected (and that's nothing new)
    I wonder why "at least", if kali staff want to stick to network manger, why they did not automatize playing with netwrok manger conf file to exclude the interface that we want to use in monitor mode or whatever.
    They are several themes in this forum and others about this isues and tips to solve it... the simplest one is without any doubt switching to wicd

    My aim is not to criticize but to help kali linux to improve. My feeling is that there is a gap between the comunity and the staff, this forum should help to create bridges and should be a place of exchange but we barely - never - see any kali developer answering or explaining stuff...
    Is that's really how a GNU-Linux distribution should work? (that's also a rhetoric question)

    Yes, there is the " bugtrack "... but that not the place or the form to generate dialogue and exchange points of view.
    I think this forum lack of partition from developer, that the community is not listened too and that leads to very bad choice like having network manager as a default network manager

  2. #2
    Senior Member
    Join Date
    Mar 2015
    Posts
    138
    Very strongly agree with you here kcdtv, One of the first things i do in ANY linux install is dump network manager. Absolutely nothing but a headache.
    Also agree with your other point, and that's one of the reasons i really don't use kali. Almost feels as there is no way to get involved.

  3. #3
    Senior Member
    Join Date
    Sep 2013
    Posts
    262
    Hi aanarchy
    It would have been nice to get the point of view of some developer, but i guess this is not the way kali linux works ...
    I wanted to give it a go to kali linux 2016,1 and stick to the original concept... but GNOME 3 and other details like network manager make me wonder why
    For sure we can easly build our custom kali live system with "live build" or do it form scartch with mini Kali... As we can usae driectly debian SID with XFCE and add tools from kali repo by hand...
    I just think it is a shame that there is so few connection between the forum/user community and the offensive security' developers
    It seems very important if you are "going roling release"
    And a bugtrack is not a place for exchanging point of view and having a real dialogue
    Things could be different, things could be better...
    I am not "complaining" or demanding; as you i don't need kali linux to have my hacking tool in my GNU-Linux
    But i am pretty sure that distribution are better if there is a good communication between staff and users...
    take care and cya ariund
    Last edited by kcdtv; 2016-03-14 at 02:00 AM.

  4. #4
    Junior Member
    Join Date
    Mar 2016
    Posts
    4
    I tottaly agree with you,wicd works properly for me on Kali Sana,but in this Rolling edition just issues,can't connect wicd(bad password),when i try MITMF,broke after 10 sec :-(

  5. #5
    Senior Member
    Join Date
    Sep 2013
    Posts
    262
    i haven't got any problem with wicd and kali2016.1.
    Removing netwrk manager and installing wicd was one the first things I did.

    Did you remove properly network-manager and network-manager-gnome?
    Code:
    sudo apt-get remove network-manager-gnome network-manager
    can't connect wicd(bad password)
    You have to be aware and select the proper way... by default with a WPA netwrok it is WPA (hex), you have to switch to WPA (passphrase)

    when i try MITMF
    I am not an expert or english speaker so i am bit lost here
    MITM is "Man in the Middle", I don't know MITMF and what the "F" stands for.
    I guess you are speaking about creating a rogue access point (F for Fake? )
    You have more sucess with network manager on this operation?

  6. #6
    Junior Member
    Join Date
    Mar 2016
    Posts
    4
    YES thank you i fix it now works properly,and mitmf ist the best mitm tool look here https://github.com/byt3bl33d3r/MITMf and F means Framework,thank you
    Last edited by Maxnonym; 2016-03-19 at 07:52 PM.

  7. #7
    Senior Member
    Join Date
    Sep 2013
    Posts
    262
    You very welcome
    And thanks to you for pointing out MITMF... It looks very interesting.. I will have to give it a go

  8. #8
    Junior Member
    Join Date
    Mar 2016
    Posts
    4
    Thanks, you are also welcome!!!!

  9. #9
    Senior Member
    Join Date
    Mar 2015
    Posts
    138
    Briefly spoke with a "developer" tonight, and apparently they actively avoid the forums: <unnamed developer> i ignore the forums like the plague that they are because users can't be arsed to search"

    Nice... :-/

    And his words of advice to get involved are: <unnamed developer> file bugs in the bug tracker

    Perhaps gives merit to the antipathy i feel towards the team behind this project...
    Skype: aanarchyy01

  10. #10
    Senior Member
    Join Date
    Jan 2016
    Posts
    100
    "wlan0" does not sound like an interface name which has been put in monitor
    mode. Please make sure to post pertinent debugging information when you post
    here, this is not a support forum."
    this was the answer from bug tracker of a issue of kali rolling on january . oh well.. "getting involved" doesn't mean they'll listen

Posting Permissions

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