Bug 964139

The Fedora 20 component was created in error. We only create new Fedora versions when we branch a new release. These bugs are all being moved to rawhide. 

Please retarget them to 19 if they also apply to the Fedora 19 branched release. 

Thanks.

Can you post the contents of your /etc/sysconfig/network-scripts/ifcfg-ens33 file?

I reported related/similar network problems on the test list (for F19, still present now):

https://lists.fedoraproject.org/pipermail/test/2013-May/115582.html

And here is a sample of /etc/sysconfig/network-scripts/ifcfg-... working files (that stop working correctly without NM).

[root@physics network-scripts]# cat ifcfg-enp4s0
TYPE=Ethernet
#BOOTPROTO=dhcp
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=enp4s0
UUID=4fd3476d-2423-4c26-99f9-28b5f6d18b05
ONBOOT=yes
HWADDR=00:08:54:41:46:01
PEERDNS=yes
PEERROUTES=yes
IPADDR=172.16.0.1
PREFIX=16

[root@physics network-scripts]# cat ifcfg-enp5s0
DOMAIN="central.ucv.ro"
IPV6_PEERDNS="yes"
IPV6INIT="yes"
UUID="df0a5629-9f3f-4c85-a5c0-ad72e8bbbbf6"
IPADDR0="193.x.y.130"
DNS1="193.x.y.254"
PREFIX0="26"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="yes"
HWADDR="00:25:22:F9:71:3D"
BOOTPROTO="none"
IPV6_DEFROUTE="yes"
GATEWAY0="193.x.y.129"
IPV6_AUTOCONF="yes"
IPV6_FAILURE_FATAL="no"
IPV6_PEERROUTES="yes"
TYPE="Ethernet"
ONBOOT="yes"
NAME="enp5s0"

So I had to add alias interfaces via /etc/rc.d/rc.local

[root@physics network-scripts]# cat /etc/rc.d/rc.local
#!/usr/bin/sh
ifconfig p4p1:0 192.168.1.1 netmask 255.255.255.0 up
ifconfig p5p1:0 193.x.y.142 netmask 255.255.255.192 up
ifconfig p5p1:1 193.x.y.143 netmask 255.255.255.192 up

[root@physics ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         g129.a.b.c      0.0.0.0         UG    0      0        0 p5p1
172.16.0.0      *               255.255.0.0     U     1      0        0 p4p1
192.168.1.0     *               255.255.255.0   U     0      0        0 p4p1
193.x.y.128     *               255.255.255.192 U     1      0        0 p5p1

Same problem appeared yesterday on a F19 LXDE install on VirtualBox but not on F19 Gnome on kvm.
I did not find somewhere explained what is enp4s0 (ifcfg-enp4s0) ..., why enp4s0 and not p4p1 as in F17, F18.

These bugs must be fixed before F19 is out.

This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Still an issue?
If so please include ifcfg file and NM logs (/var/log/messages or journalctl -u NetworkManager)

Network device names are not changed by NetworkManager but rather biosdevname/systemd.
https://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming

The problem seems to be that names shown by "ip addr" or "ifconfig -a" are shortened:

real name: enc1377737
name shown by "ip addr" or "ifconfig -a": enc13777

if you now try to use "ifconfig enc13777 10.10.10.10/24 up" this leads to an error message, because the device enc13777 really does not exist. Since none of the commands displays the full name you're a bit lost about what name the device really has.

At least in one case I could even give the full name to "ifconfig enc1377737 10.10.10.10/24 up" and got an error message, since the command shortened the device name to enc13777 and tried to use this one, while the system used enc1377737. This leads to situations where the device is listed giving

ip addr or
ifconfig -a

but you can't configure it, even looking up the full name, because the tools only accept device names max. eight characters in length!

There is no limitation to eight characters and I don't see any interface name truncation in ip or ifconfig commands. What versions do you use?

Interface names in linux can be up to 16 characters long and the tools show them all. (See e.g. http://books.google.cz/books?id=96V4AgAAQBAJ&pg=PA493)

So, if you have a problem with an ifcfg file, please post its content here and also logs from NetworkManager (from startup, including the activation of the file).

You can get list of all connection profiles know to NetworkManager with:
$ nmcli con
You can activate a profile with
$ nmcli con up <profile-name>

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 this bug is closed as described in the policy above.

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.

Works since some time for Fedora 20,21,rawhide