Red Hat Bugzilla – Bug 438902
conflicts with NetworkManager
Last modified: 2014-03-16 23:13:11 EDT
Description of problem:
On a default install, there is the Administration->Network, and
Administration->Network Device Control. Enabling/disabling devices here is going
to screw up NetworkManager (now running by default) pretty badly.
Version-Release number of selected component (if applicable):
So does ifup/ifdown in a terminal??
What should s-c-control/network do? Kill NM?
Well, ifup/ifdown isn't presented to the user in the normal menus. I'm not sure
killing NM is the right answer.
nevertheless, someone could ifup/ifdown from a terminal and NM should not screw
Ideally no, NM wouldn't screw up, but then people could also add/delete/change
routes in the routing table, add/remove/change IP addresses, etc. Should NM
handle all those cases too? That's a boatload of code for not a lot of benefit.
Either you use NM and don't mess with devices, or you don't use NM and you mess
With NM_CONTROLLED=no though, I'll make NM ignore the ifcfg and the device that
is specified by the MAC address in the ifconfig file, so that's the "out". If
you have a device that's not controlled by NM, then you should probably be able
to ifup/ifdown as much as you want. There are at least a few ways to make
ifup/ifdown and NM cooperate:
1) If NM isn't running, do what's done now
2) If NM is running, and the ifcfg isn't NM_CONTROLLED=no, poke NM to activate
3) If NM is running, and the ifcfg is NM_CONTROLLED=no, activate the connection
but don't change the default route
Well, need a C-based NM-poker, unless we want to do fire&forget dbus-send. Aside
from that, seems reasonable.
I'll sign up to write a C-based poker, just need to know what ifup/ifdown expect
from it (ie, what commands it should expect, what return values, etc).
Hm, interfaces that I think would be required:
2) bring up interface XXX (either by device name or mac address)
3) bring down interface XXX (either by device name or mac address)
#2 and #3 should probably have options to block.
For compatibility, auto-ip probably shouldn't be tried if DHCP fails.
Specific failure codes we may want to enumerate:
- device has no link
- configuration failed (DHCP or otherwise)
Ok, this version should not let the user activate/deactivate, if NM_CONTROLLED
what do you think?
What actually sets NM_CONTROLLED? Or is it all done by hand?
s-c-n can set/unset it. Dunno what else does.
Can set/unset,or sets/unsets by default?
btw, s-c-n > 1.5.3 honors NM_CONTROLLED=yes (default, if not specified is "no")
anaconda really should write this and ask/inform the user about this.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
*** Bug 459017 has been marked as a duplicate of this bug. ***
NM should be fixed also, because it's deafault is 'yes' even thou it's not specified.
> NM should be fixed also ...
In the current installations, even after upgrades, service 'network'
by default is not running. Which would mean "no network connections"
if NM requires an explicit "yes" unless this would be added to
a configuration. OTOH NM is still unable to set hostname from IP.
If there is some documentation which describes what is really expected
all around in this setup then I am not aware of its existence.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.