| |||||||||||||
|
| |||||||||||||
NetworkManager and ConnMan (Dan Williams' Blog)NetworkManager and ConnMan (Dan Williams' Blog)Posted Jun 29, 2009 11:48 UTC (Mon) by jlokier (subscriber, #52227)In reply to: NetworkManager and ConnMan (Dan Williams' Blog) by dcbw Parent article: NetworkManager and ConnMan (Dan Williams' Blog)
Since you ask, these things don't work with NM in my experience so far:
If there's a simple plugin interface where all these things can be scripted to work properly, or a simple configuration file like most daemons, well "man" didn't show anything useful. Make it more accessible in a unixy way - with a proper man page, proper options and a proper config file, and I think that will clear up most user's concerns.
(Log in to post comments)
NetworkManager and ConnMan (Dan Williams' Blog) Posted Jun 29, 2009 22:02 UTC (Mon) by Frej (subscriber, #4165) [Link]
> 1. Simple configurations which are already in /etc/network/interfaces. Don't ask me why, I've been told they should work with the appropriate NM setting. Why do I have *two* identical "wired eth0" entries in nm-applet, but only one works. I don't know.
I don't think NM understands /etc/network/interfaces other than if it should ignore the interface or not. The double wired interfaces is probably a bug maybe in nm-applet or network driver (wired usually works though).
> 2. Interfaces with bridges, so that local KVMs can be used. These need the DHCP client and/or static IP settings to be done on the bridge interface, but the rest of management - wireless keys or wired signal detection - to use the real interface. It's a real pain to have to kill NM and manually set up a wireless network when I want to use KVM, particularly as it means wireless config is duplicated inside and outside NM, and the nice NM roaming isn't available.
I can highly recommend virt-manager - i've never needed to care about kvm and network setup. And never needed to disable nm.
> 3. OpenVPN with additional options not listed in the GUI.
That should probably be patchable ;)
> 4. 3g bluetooth connections - I have a script which kills NM to use 3g, and restart NM when I've finished using 3g.
> 5. Command line use, for when you log in but not with a GUI, or X is broken. Sure, that's unusual, but when it happens it's really unhelpful that your wireless network configuration is stored only in a place where you can't use or even read it.
Everybody agrees that cli interface would be nice. But your info is in /etc/NetworkManager (if it set as a system setting, otherwise the somewhat painfull gconftool-2 can help)
> 6. Automatic NM-managed wireless connection when not logged in. Others have mentioned uses.
I've Never tried that? Should work with when it's a system setting - or is the password not saved in system settings? :(
NetworkManager and ConnMan (Dan Williams' Blog) Posted Jun 29, 2009 22:34 UTC (Mon) by dlang (✭ supporter ✭, #313) [Link]
one of the claims for NM is that it works with the distro config files instead of needing to do it's own thing.
this doesn't match my experiance either.
NM works for most people most of the time, and that's about all that I would expect from any tool like this (there are just _too_ many ways for networking to be configured). my problem with NM is that it has no allowance for the cases where it doesn't work, you have to uninstall it to be able to do anything else.
NetworkManager and ConnMan (Dan Williams' Blog) Posted Aug 2, 2009 1:11 UTC (Sun) by bfields (subscriber, #19510) [Link] "I can highly recommend virt-manager - i've never needed to care about kvm and network setup. And never needed to disable nm."Is your host doing NAT for the kvm guests? I find that works fine by default. But last time I needed to put the kvm guests on the real network (using bridging, as in the parent comment), I found libvirt and nm weren't enough--I needed to turn off nm and do all the setup manually. (But it may be that I missed some libvirt configuration that could have helped.)
|
|
||||||||||||