From: Marco Gaiarin <gaio@lilliput.linux.it>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] Interface not renamed...
Date: Fri, 23 May 2025 16:41:25 +0200 [thread overview]
Message-ID: <aDCJFTKo_i7FXI4_@sv.lnf.it> (raw)
In-Reply-To: <d1f0f4d4-1589-4d35-bc6b-32194cf97721@web.de> <af9f074b-0784-44ba-8eca-a7b51315d31a@gmail.com>
Mandi! Falko Trojahn
In chel di` si favelave...
> you surely don't have any udev rules for this interface
> e.g. left over from former system?
No, i've not altered in any way udev rules...
Mandi! Roland
In chel di` si favelave...
> iirc, that can be a matter of the bios version installed.
> https://linux.dell.com/files/whitepapers/consistent_network_device_naming_in_linux.pdf
We have upgarded 8 identical servers, upgrading to identical bios version;
this is the only one that have this trouble.
Anyway, i've found some more info:
root@svpve2:~# ip link show | egrep '[0-9]+: '
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
3: eth1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000
4: ens5f0np0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000
5: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000
6: eno2: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond1 state UP mode DEFAULT group default qlen 1000
7: ens5f1np1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 9000 qdisc mq master bond2 state UP mode DEFAULT group default qlen 1000
8: idrac: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT group default qlen 1000
9: bond2: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000
10: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr0 state UP mode DEFAULT group default qlen 1000
11: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
12: bond1: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master vmbr1 state UP mode DEFAULT group default qlen 1000
13: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
[...]
interface 'ens1f1' does not desappear, simply get not 'renamed' on boot, and
remain 'eth1'.
I've tried a manual:
ip link set eth1 master bond1
and interface start working as expected.
If logs can be useful, if it is better to fire up a bug, say me.
Just i'm here, i've found also:
root@svpve2:~# ip addr show ens1f0
2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP group default qlen 1000
link/ether f4:ee:08:24:3a:ff brd ff:ff:ff:ff:ff:ff permaddr 5c:6f:69:0f:99:78
altname enp1s0f0
and 'enp1s0f0' in 'altname' was the old interface name, that was in
/etc/network/interfaces; but at boot bond does not bind it, i was forced to
use the 'new' name.
'altname' work only insome aspect? Or simply, does not work for bonds?
Thanks.
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2025-05-23 14:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 12:28 Marco Gaiarin
2025-05-23 10:16 ` Falko Trojahn
2025-05-23 10:23 ` Roland via pve-user
2025-05-23 14:41 ` Marco Gaiarin [this message]
2025-05-27 8:12 ` Fiona Ebner
2025-05-27 20:46 ` Marco Gaiarin
2025-07-30 15:20 ` Marco Gaiarin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aDCJFTKo_i7FXI4_@sv.lnf.it \
--to=gaio@lilliput.linux.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.