Network card getting: rename4 ? Predictable Network Interface Names

Jan 24, 2017
4
0
6
The Netherlands
So i know that most people still have "ethX".
But i like the "Predictable Interface Names" and therefore use them.
Only my "new" chelsio cc2-n320e-rs dual 10g sfp+ card doens't play nice for some reason?

It gives me a "renameX" interface. with is not editable in the GUI and is "random" therefor not predictable.

Motherboard is a X10SLM-F


Code:
4: enp5s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether <snip>:7a brd ff:ff:ff:ff:ff:ff
5: rename5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether <snip>:7b brd ff:ff:ff:ff:ff:ff
dmesg shows:
Code:
<snip>
[    1.070785] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[    1.076643] igb 0000:04:00.0: added PHC on eth0
[    1.076644] igb 0000:04:00.0: Intel(R) Gigabit Ethernet Linux Driver
[    1.076645] igb 0000:04:00.0: eth0: (PCIe:2.5GT/s:Width x1)
[    1.076646] igb 0000:04:00.0 eth0: MAC: 0c:c4:7a:91:bc:0e
[    1.076713] igb 0000:04:00.0: eth0: PBA No: 011000-000
[    1.088061] igb 0000:04:00.0: LRO is disabled
[    1.088062] igb 0000:04:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
[    1.088862] igb 0000:04:00.0 eno1: renamed from eth0
<snip>
[    1.148977] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 0c:c4:7a:91:bc:0f
[    1.148979] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[    1.149026] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: 0100FF-0FF
<snip>
[    1.149533] e1000e 0000:00:19.0 eno2: renamed from eth0
<snip>
[    1.312868] cxgb3 0000:05:00.0: Port 0 using 4 queue sets.
[    1.312869] cxgb3 0000:05:00.0: Port 1 using 4 queue sets.
[    1.312873] cxgb3 0000:05:00.0 eth0: Chelsio T320 10GBASE-R NIC (rev 4) PCI Express x4 MSI-X
[    1.312874] cxgb3: eth0: 64MB CM, 0MB PMTX, 0MB PMRX, S/N: PT49140566
[    1.312875] cxgb3 0000:05:00.0 eth1: Chelsio T320 10GBASE-R NIC (rev 4) PCI Express x4 MSI-X
[    1.313494] cxgb3 0000:05:00.0 enp5s0: renamed from eth0
[    1.332239] cxgb3 0000:05:00.0 rename5: renamed from eth1
<snip>
Google doesn't give me any clue in whats happening other then "use the eth0" and "use the /etc/udev/rules.d/70-persistent-net.rules"


Code:
root@server:~# pveversion --verbose
proxmox-ve: 5.4-1 (running kernel: 4.15.18-13-pve)
pve-manager: 5.4-5 (running version: 5.4-5/c6fdb264)
pve-kernel-4.15: 5.4-1
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-51
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
openvswitch-switch: 2.7.0-3
proxmox-widget-toolkit: 1.0-26
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-20
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
Code:
root@server:~# cat /etc/*release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"
ID=debian
 
Last edited:

wolfgang

Proxmox Staff Member
Staff member
Oct 1, 2014
5,375
362
103
Hi,

do you have the problem if you use Kernel "pve-kernel-4.15.18-9" ?
 
Jan 24, 2017
4
0
6
The Netherlands
Hi,

do you have the problem if you use Kernel "pve-kernel-4.15.18-9" ?
Yes it still exists
Code:
4: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc mq state UP group default qlen 1000
    link/ether <snip>:7a brd ff:ff:ff:ff:ff:ff
5: rename5: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether <snip>:7b brd ff:ff:ff:ff:ff:ff
Code:
[    0.992316] e1000e: loading out-of-tree module taints kernel.
[    0.992668] dca service started, version 1.12.1
[    0.993351] e1000e: Intel(R) PRO/1000 Network Driver - 3.4.1.1-NAPI
[    0.993352] e1000e: Copyright(c) 1999 - 2018 Intel Corporation.
[    0.993370] Intel(R) Gigabit Ethernet Linux Driver - version 5.3.5.18
[    0.993371] Copyright(c) 2007 - 2018 Intel Corporation.
[    0.993604] cxgb3: Chelsio T3 Network Driver - version 1.1.5-ko
[    0.993625] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
<snip>
[    1.080595] igb 0000:04:00.0: added PHC on eth0
[    1.080596] igb 0000:04:00.0: Intel(R) Gigabit Ethernet Linux Driver
[    1.080597] igb 0000:04:00.0: eth0: (PCIe:2.5GT/s:Width x1)
[    1.080598] igb 0000:04:00.0 eth0: MAC: 0c:c4:7a:91:bc:0e
[    1.080672] igb 0000:04:00.0: eth0: PBA No: 011000-000
[    1.086615] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[    1.092037] igb 0000:04:00.0: LRO is disabled
[    1.092038] igb 0000:04:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
<snip>
[    1.173845] e1000e 0000:00:19.0 eth1: (PCI Express:2.5GT/s:Width x1) 0c:c4:7a:91:bc:0f
[    1.173846] e1000e 0000:00:19.0 eth1: Intel(R) PRO/1000 Network Connection
[    1.173892] e1000e 0000:00:19.0 eth1: MAC: 11, PHY: 12, PBA No: 0100FF-0FF
<snip>
[    1.324999] cxgb3 0000:05:00.0: Port 0 using 4 queue sets.
[    1.325000] cxgb3 0000:05:00.0: Port 1 using 4 queue sets.
[    1.325004] cxgb3 0000:05:00.0 eth2: Chelsio T320 10GBASE-R NIC (rev 4) PCI Express x4 MSI-X
[    1.325005] cxgb3: eth2: 64MB CM, 0MB PMTX, 0MB PMRX, S/N: PT49140566
[    1.325006] cxgb3 0000:05:00.0 eth3: Chelsio T320 10GBASE-R NIC (rev 4) PCI Express x4 MSI-X
[    1.325672] cxgb3 0000:05:00.0 enp5s0: renamed from eth2
[    1.340236] cxgb3 0000:05:00.0 rename5: renamed from eth3
Code:
root@server:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.4-5 (running version: 5.4-5/c6fdb264)
pve-kernel-4.15: 5.4-1
pve-kernel-4.15.18-13-pve: 4.15.18-37
pve-kernel-4.15.18-12-pve: 4.15.18-36
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-10-pve: 4.15.18-32
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.18-8-pve: 4.15.18-28
pve-kernel-4.15.18-7-pve: 4.15.18-27
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.15.18-4-pve: 4.15.18-23
pve-kernel-4.15.18-2-pve: 4.15.18-21
pve-kernel-4.15.18-1-pve: 4.15.18-19
pve-kernel-4.15.17-3-pve: 4.15.17-14
pve-kernel-4.15.17-2-pve: 4.15.17-10
pve-kernel-4.15.17-1-pve: 4.15.17-9
corosync: 2.4.4-pve1
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.1-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-51
libpve-guest-common-perl: 2.0-20
libpve-http-server-perl: 2.0-13
libpve-storage-perl: 5.0-41
libqb0: 1.0.3-1~bpo9
lvm2: 2.02.168-pve6
lxc-pve: 3.1.0-3
lxcfs: 3.0.3-pve1
novnc-pve: 1.0.0-3
openvswitch-switch: 2.7.0-3
proxmox-widget-toolkit: 1.0-26
pve-cluster: 5.0-36
pve-container: 2.0-37
pve-docs: 5.4-2
pve-edk2-firmware: 1.20190312-1
pve-firewall: 3.0-20
pve-firmware: 2.0-6
pve-ha-manager: 2.0-9
pve-i18n: 1.1-4
pve-libspice-server1: 0.14.1-2
pve-qemu-kvm: 2.12.1-3
pve-xtermjs: 3.12.0-1
qemu-server: 5.0-50
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.13-pve1~bpo2
 
Last edited:

wolfgang

Proxmox Staff Member
Staff member
Oct 1, 2014
5,375
362
103
I really don't want to tag you but i think this really needs some love as you guys are generating the kernel.
The name is generated also by the nic driver and the bios.
The problem is we have no chelsio nic so we can't reproduce it here.
I can only recommend you to use the udev rules to set the nic name manual.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE and Proxmox Mail Gateway. We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get your own in 60 seconds.

Buy now!