Bug 1062409 - default gateway broken if NetworkManager is disabled/uninstalled
Summary: default gateway broken if NetworkManager is disabled/uninstalled
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-02-06 20:26 UTC by René Genz
Modified: 2014-10-07 14:46 UTC (History)
5 users (show)

Fixed In Version: NetworkManager-
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-10-06 12:06:45 UTC

Attachments (Terms of Use)

Description René Genz 2014-02-06 20:26:11 UTC
Description of problem:
network connection to computers outside the subnet is not possible, if NetworkManager is disabled/uninstalled.

Version-Release number of selected component (if applicable):
NetworkManager.x86_64   1:

How reproducible:

Steps to Reproduce:
1. kickstart text-only installation with static IPv4 adress assignment (IPv6 disabled); uninstall NetworkManager in %post section
2. after installation:
$ cd /etc/sysconfig/network-scripts/
$ cat ifcfg-em1
IPADDR0=<IPv4 adress>
GATEWAY0=<IPv4 gateway adress>

$ sed -i 's/0=/=/' ifcfg-em1

$ cat ifcfg-em1
IPADDR=<IPv4 adress>
GATEWAY=<IPv4 gateway adress>

$ systemctl restart network.service
#and everything works fine again

Actual results:
not possible to open external website with firefox

Expected results:
being able to open external website with firefox

Additional info:
This is a repost of bug 911949 because I could not change the Fedora version.

Comment 1 Jirka Klimes 2014-08-29 07:01:44 UTC
It is fixed in Fedora 21 - bug 771673.

Comment 2 C.M. Connelly 2014-09-05 01:26:09 UTC
This problem is also seen in RHEL 7.

Comment 3 Dan Williams 2014-09-05 01:53:30 UTC
(In reply to C.M. Connelly from comment #2)
> This problem is also seen in RHEL 7.

RHEL7 is already handled by bug 1105770.

Comment 4 Fedora Update System 2014-09-05 03:07:22 UTC
NetworkManager- has been submitted as an update for Fedora 20.

Comment 5 Fedora Update System 2014-09-09 22:22:28 UTC
Package NetworkManager-
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2014-09-12 14:29:45 UTC
NetworkManager- has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 7 René Genz 2014-10-02 13:10:17 UTC
I am using NetworkManager-
If NetworkManager is uninstalled and you restart your F20 machine, connections to computers outside of local network is not possible. A simple ping will fail.

I suspect the reason is '/etc/sysconfig/network-scripts/ifcfg-em1' still uses GATEWAY0

sed -i 's/0=/=/' ifcfg-em1
systemctl restart network.service
is a workaround.

Shall I open a bug for a different package? Which package to blame?

Comment 8 Jirka Klimes 2014-10-06 12:06:45 UTC
The problem of writing GATEWAY has been fixed in NetworkManager-

However, if there are old files with GATEWAY0, they need to be fixed as you did when you use legacy network.service.

Comment 9 René Genz 2014-10-07 14:46:52 UTC
sorry, I left out important information in my previous post:
I reinstalled my computer. There were no leftover files from previous installation.

The reinstallation was performed with a kickstart text-only installation.
It was initiated with a F20 USB thumb drive that was loaded with Fedora-20-x86_64-netinst.iso.
An update repo is specified. It is accessible and works.
The kickstart file contains static IPv4 adress assignment; IPv6 is disabled; NetworkManager package is uninstalled in %post section of kickstart file.

After installation '/etc/sysconfig/network-scripts/ifcfg-em1' contains GATEWAY0.
NetworkManager- is the version that was available in the update repo.

Note You need to log in before you can comment on or make changes to this bug.