[Bug 918354] Re: ifupdown doesn't detect Network Manager in "managed" mode since Oneiric
Launchpad Bug Tracker
918354 at bugs.launchpad.net
Wed Jan 18 20:35:11 UTC 2012
This bug was fixed in the package ifupdown - 0.7~beta2ubuntu3
---------------
ifupdown (0.7~beta2ubuntu3) precise; urgency=low
* More label fixes from upstream, don't bring down the parent
when bringing down a label.
http://anonscm.debian.org/hg/collab-maint/ifupdown/rev/f9cef973859e
http://anonscm.debian.org/hg/collab-maint/ifupdown/rev/80a68bbbd45d
* /etc/init/network-interface-security.conf was made a conffile in
maverick. Update the check in postinst to fix upgrade from Oneiric.
(LP: #918323)
* Fix NetworkManager managed mode detection to look at
/etc/NetworkManager/NetworkManager.conf instead of
/etc/NetworkManager/nm-system-settings.conf (LP: #918354)
-- Stephane Graber <stgraber at ubuntu.com> Wed, 18 Jan 2012 14:19:03 -0500
** Changed in: ifupdown (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/918354
Title:
ifupdown doesn't detect Network Manager in "managed" mode since
Oneiric
Status in “ifupdown” package in Ubuntu:
Fix Released
Bug description:
Network Manager in Oneiric switched from
/etc/NetworkManager/NetworkManager.conf to /etc/NetworkManager/nm-
system-settings.conf for its daemon settings.
ifupdown contains code to check in the ifupdown section of that config
for a managed flag (default value false) and if set to true, disable
ifup/ifdown to prevent from messing with Network Manager.
ifupdown's code wasn't updated to look at the new location and so that
part of the code didn't work since the switch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/918354/+subscriptions
More information about the foundations-bugs
mailing list