I hear lots of anger from people that hate NetworkManager, but:can it coexist with network?what damage does NetworkManager cause?once i've used NetworkManager must I us... [by cocobolo]
I've got a laptop which I use two wireless adapters with. With one of them, I'd like NetworkManager to manage and automatically connect me to wireless networks when they're available. The other, I want NetworkManager to leave alone, letting me hack on it with iwconfig and whatnot.
Whenever I boot into Fedora 16 (KDE Spin), the network manager system tray icon is set to "M" and it says that NetworkManager startup required. I restart NetworkManager and everything seems to start working normally.
Recently, NetworkManager has stopped listing access points completely. In fact, VPNC config is not listed in my NetworkManager list of items.
Not sure if I'm on the right track here, but you can start/stop/enable/disable etc NetworkManager with: systemctl start NetworkManagerwifi-menu will not work if NetworkManager is running and vice-versa.I use NetworkManager, but if I don't boot into a gui cause somethings broken, then I have to stop NetworkManager in order for wifi-menu to work.
Most people suffer from problems with Networkmanager after a crash or after not being able to return from sleep/hybernate mode.
Neither reinstalling Networkmanager nor changing to ifup and then switching back to networkmanager solves this problem, because it is located in a config file which is not being overwriten during reinstall or configuration by yast.
I have a problem getting my VPN to work.
In /var/log/syslog I get the following when trying to connect through network-manager.
Aug 17 11:23:42 rofe-laptop NetworkManager: <info> Starting VPN service 'org.freedesktop.NetworkManager.openvpn'...
Aug 17 11:23:42 rofe-laptop NetworkManager: <info> VPN service 'org.freedesktop.NetworkManager.openvpn' started (org.freedesk