Red Hat Bugzilla – Bug 973558
system-config-network: interface names do not agree with "ip link"
Last modified: 2015-02-17 10:32:57 EST
On a freshly installed Fedora 19 system, "ip link" reports two interaces, em1 and p2p1. p2p1 is the primary network interface (the default route goes out over this link). However, system-config-network-tui only offers to configure the interfaces "enp2s0 (enp2s0)" and "enp3s0 (enp3s0)" in the device selection dialog. This is quite confusing.
It would also help if the device selection dialog indicated which of the interfaces are actually up
"ip link" shows:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: p2p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 68:05:ca:ab:cd:ef brd ff:ff:ff:ff:ff:ff
3: em1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT qlen 1000
link/ether 00:9c:02:ab:cd:ef brd ff:ff:ff:ff:ff:ff
Relevant dmesg output:
[ 17.332098] e1000e 0000:02:00.0 eth0: registered PHC clock
[ 17.332107] e1000e 0000:02:00.0 eth0: (PCI Express:2.5GT/s:Width x1) 68:05:ca:ab:cd:ef
[ 17.332110] e1000e 0000:02:00.0 eth0: Intel(R) PRO/1000 Network Connection
[ 17.332123] e1000e 0000:02:00.0 eth0: MAC: 3, PHY: 8, PBA No: E46981-008
[ 17.332746] tg3 0000:03:00.0 eth1: Tigon3 [partno(BCM95723) rev 5784100] (PCI Express) MAC address 00:9c:02:ab:cd:ef
[ 17.332754] tg3 0000:03:00.0 eth1: attached PHY is 5784 (10/100/1000Base-T Ethernet) (WireSpeed, EEE)
[ 17.332758] tg3 0000:03:00.0 eth1: RXcsums LinkChgREG MIirq ASF TSOcap
[ 17.332762] tg3 0000:03:00.0 eth1: dma_rwctrl dma_mask[64-bit]
[ 17.806068] systemd-udevd: renamed network interface eth0 to p2p1
[ 17.819712] systemd-udevd: renamed network interface eth1 to em1
Same here; this actually causes an additional problem for me: on my IPA server I disabled NetworkManager, and it seemed the network script is affected by this inconsistency in network device names, because the gateway specified in the network script (ifcfg-enp2s0) did not show up in the routing table and had to be added by hand
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.