On Sun, 24 Aug 2014 19:05:52 -0400 (EDT), Michael Biebl wrote: > > If you set managed=true, you actually tell NetworkManager to manage the > interface. So I'm not sure why you are surprised that it does.
In a previous release of network-manager, if I didn't set "managed=true" in the [ifupdown] section of /etc/NetworkManager/NetworkManager.conf, after giving control of the wired ethernet interface back to ifupdown, then the desktop had no network connectivity at all. I thought that this was "broken as designed" behavior. But apparently, that was a bug that has since been fixed. I set "managed=false", shutdown, and rebooted. "NetworkManager Applet" on the desktop now shows no connections at all. Nevertheless, desktop applications, such as the browser, still have network connectivity via the ifupdown-managed eth0 interface. This was easier than I thought. I didn't try that because I tried it before (about eight months ago, I think) and it didn't work. But now it does. Another annoying thing about my former configuration was that "netstat -rn" showed two identical default route entries. Apparently, ifupdown supplied one and network-manager supplied the other. I don't need two identical default routes. But with managed=false, only one default route shows up in the output of "netstat -rn". And, most importantly, network-manager does not delete my static route commands issued in /etc/rc.local. -- .''`. Stephen Powell : :' : `. `'` `- -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1889049189.408227.1408931154373.javamail.r...@md01.wow.synacor.com
