From: Marco Gaiarin <gaio@lilliput.linux.it>
To: pve-user@lists.proxmox.com
Subject: [PVE-User] Interface not renamed...
Date: Wed, 21 May 2025 14:28:31 +0200 [thread overview]
Message-ID: <dgt0gl-nko1.ln1@leia.lilliput.linux.it> (raw)
I've upgraded a server from PVE7 to PV8, and (as expected) some interfaces
get renamed.
Really, i've upgraded TWO identical server (Dell T440), and one went
flawlessy, the other... and interface get NOT renamed, remain 'eth1':
root@svpve2:~# ip link show eth1
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000
link/ether 5c:6f:69:0f:99:79 brd ff:ff:ff:ff:ff:ff
altname enp1s0f1
I've tried:
root@svpve2:~# ip -force link set dev eth1 name ens1f1
RTNETLINK answers: File exists
and:
root@svpve2:~# ip link property add dev eth1 altname ens1f1
RTNETLINK answers: File exists
but nothing work; there's something i can do whithout rebooting the server?
Thanks.
PS: port is on a dual-port pcie card, the other port on the same card works as expected:
root@svpve2:~# ip link show ens1f0
2: ens1f0: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT 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
--
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next reply other threads:[~2025-05-22 6:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 12:28 Marco Gaiarin [this message]
2025-05-23 10:16 ` Falko Trojahn
2025-05-23 10:23 ` Roland via pve-user
2025-05-23 14:41 ` Marco Gaiarin
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=dgt0gl-nko1.ln1@leia.lilliput.linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox