Description of problem:
Extracted from bug 815243. Currently with F18 Beta to disable networking completely the superuser needs to disable and stop the NetworkManager and network services and then loop over the network interfaces to make sure networking is really disabled. Compared to earlier Fedoras where "service NetworkManager stop ; service network stop" did the trick this is clumsy given that today it is not atypical to have 4 or 8 or even more NICs on a system.
Please provide a simple method for the superuser to disable networking at will.
Version-Release number of selected component (if applicable):
Fedora 18 Beta
AFAIK the future lies in using only NetworkManager for network configuration. Stopping NetworkManager doesn't clear the interfaces by design. But you can
disable networking with NetworkManager using nmcli.
(In reply to comment #0)
> Compared to earlier Fedoras where "service
> NetworkManager stop ; service network stop" did the trick this is clumsy
> given that today it is not atypical to have 4 or 8 or even more NICs on a
You are right that this was a trick, or hack, not a supported method IMO.
I don't why this is filed against systemd. systemd sets up the loopback interface, but it's not involved in other interfaces.
At the moment functionality to stop NetworkManager does not exist, perhaps we could add a D-Bus command to NM to tell it to quit and actually clear all interface configuration. Like pavel says, NetworkManager is meant to be either disabled or running all the time, and if you're somebody who needs to disable NetworkManager, then you're obviously somebody who knows enough to manually configure interfaces too. Plus, given that this operation would only ever occur once (because after that, NetworkManager would be disabled) it's not a particularly high priority.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.
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 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.