Add network managers detection

[misterx]

Sometimes people complains because airodump-ng or aireplay-ng stop working after some time or it doesn't work. A network manager may be running and changing card mode back to managed. airodump-ng and aireplay-ng should indicate the user which network managers are running and why not having an option to kill them automatically.

Should be done on 1.0-dev also

List:

• wpa_action
• wpa_cli
• wpa_supplicant
• dhclient
• dhclient3
• knetworkmanager
• network-manager. Process Name: NetworkManager
• network-manager-gnome (is this the real process name?)
• NetworkManagerDispatcher
• RutilT (ralink NM)
• netcfg2
• netcfg
• net-profiles

Windows:

• Wireless Zero Configuration, but it should check if the service is running (WZCSVC) because the process is svchost and other services use this process.

[hirte]

we shouldn't kill these processes unless we are sure they mean trouble, we could put a list in --test to choose to kill known processes.

[misterx]

airodump-ng and aireplay-ng will warn if it finds any of them and offer to kill them. Also, they will refuse to run if any of them is running to avoid any bug report.

[misterx]

Added windows network manager.

[ebfe]

the offer of killing these processes should be a last resort for users which don't know any better. the wpa* tools are likely to have been called by some initd script and we shouldn't fumble with those

[hirte]

see r518 for a detection implementation into airmon-ng

[misterx]

added NetworkManagerDispatcher

[misterx]

added another NM

[anonymous]

In archlinux there is a network manager called netcfg2, the daemon name is net-profiles. I also think there is one older one, netcfg, with a daemon name of network. I am not 100% sure of this.