Change in name of Ethernet device
I just did a 'zypper dup' on an aarch64 Tumbleweed system and lost the Ethernet device. Instead of having the name eth0 it is now named end0. After copying /etc/sysconfig/network/ifcfg-eth0 to /etc/sysconfig/network/ifcfg-end0 and restarting the network I now see with ip a an UP end0 device. However I cannot access the system using ssh because the firewall does not know end0. How can I rename end0 into eth0 again? -- fr.gr. member openSUSE Freek de Kruijf
Hi,
-----Original Message----- From: Freek de Kruijf <freek@opensuse.org> Sent: 22 November 2022 12:55 To: Mailinglist openSUSE ARM <arm@lists.opensuse.org> Subject: Change in name of Ethernet device
I just did a 'zypper dup' on an aarch64 Tumbleweed system and lost the Ethernet device.
Instead of having the name eth0 it is now named end0. After copying /etc/sysconfig/network/ifcfg-eth0 to /etc/sysconfig/network/ifcfg-end0 and restarting the network I now see with ip a an UP end0 device. However I cannot access the system using ssh because the firewall does not know end0.
How can I rename end0 into eth0 again?
Here, on my aarch64 server running Tumbleweed, Ethernet is not named eth0 but enp2s0 and the update did not affect it. What hardware are you running on? I suspect the Systemd version update (251.8 -> 252.1) to be responsible of this eth0 => end0 naming change. But no idea if it is expected or not. Could you create a bug report for this problem, please? Thanks, Guillaume
-- fr.gr.
member openSUSE Freek de Kruijf
On Tue, Nov 22, 2022 at 12:55:01PM +0100, Freek de Kruijf wrote:
I just did a 'zypper dup' on an aarch64 Tumbleweed system and lost the Ethernet device.
Instead of having the name eth0 it is now named end0. After copying /etc/sysconfig/network/ifcfg-eth0 to /etc/sysconfig/network/ifcfg-end0 and restarting the network I now see with ip a an UP end0 device. However I cannot access the system using ssh because the firewall does not know end0.
How can I rename end0 into eth0 again?
Just have a quick look into your udev rules: /etc/udev/rules.d/70-persistent-net.rules SUBSYSTEM=="net", ACTION=="add", DRIVERS=="e1000", ATTR{dev_id}=="0x0", ATTR{type}=="1", ATTR{address}=="52:54:00:12:5e:01", NAME="ext0" You can also use YaST to set a specific NIC name. Ciao, Alex~
-- fr.gr.
member openSUSE Freek de Kruijf
-- Alexander Bergmann <abergmann@suse.com> Security Engineer, GPG: E30A 65A4 0F50 0066 B2B5 F614 DE54 E875 9FFA 4886 SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nuremberg, Germany (HRB 36809, AG Nürnberg) Managing Director/Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
Op dinsdag 22 november 2022 14:52:32 CET schreef Alexander Bergmann:
On Tue, Nov 22, 2022 at 12:55:01PM +0100, Freek de Kruijf wrote:
I just did a 'zypper dup' on an aarch64 Tumbleweed system and lost the Ethernet device.
Instead of having the name eth0 it is now named end0. After copying /etc/sysconfig/network/ifcfg-eth0 to /etc/sysconfig/network/ifcfg-end0 and restarting the network I now see with ip a an UP end0 device. However I cannot access the system using ssh because the firewall does not know end0.
How can I rename end0 into eth0 again?
Just have a quick look into your udev rules:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="e1000", ATTR{dev_id}=="0x0", ATTR{type}=="1", ATTR{address}=="52:54:00:12:5e:01", NAME="ext0"
You can also use YaST to set a specific NIC name.
Ciao, Alex~
Many thanks. However I do have a different Ethernet device on my Banana Pi M64. # hwinfo --network 18: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 5WpM.ndpeucax6V1 Parent ID: Euci.TfPFe67fIBB SysFS ID: /class/net/end0 SysFS Device Link: /devices/platform/soc/1c30000.ethernet Hardware Class: network interface Model: "Ethernet network interface" Driver: "dwmac-sun8i" Driver Modules: "dwmac_sun8i" Device File: end0 HW Address: 02:ba:f7:39:24:a4 Permanent HW Address: 02:ba:f7:39:24:a4 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #3 (Ethernet controller) So my /etc/udev/rules.d/70-persistent-net.rules, which is currently empty should look like?: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="dwmac_sun8i", ATTR{dev_id}=="0x0", ATTR{type}=="1", ATTR{address}=="02:ba:f7:39:24:a4",NAME="eth0" -- fr.gr. member openSUSE Freek de Kruijf
On Tue 22 Nov 2022 03:40:20 PM CST, Freek de Kruijf wrote:
Op dinsdag 22 november 2022 14:52:32 CET schreef Alexander Bergmann:
On Tue, Nov 22, 2022 at 12:55:01PM +0100, Freek de Kruijf wrote:
I just did a 'zypper dup' on an aarch64 Tumbleweed system and lost the Ethernet device.
Instead of having the name eth0 it is now named end0. After copying /etc/sysconfig/network/ifcfg-eth0 to /etc/sysconfig/network/ifcfg-end0 and restarting the network I now see with ip a an UP end0 device. However I cannot access the system using ssh because the firewall does not know end0.
How can I rename end0 into eth0 again?
Just have a quick look into your udev rules:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="e1000", ATTR{dev_id}=="0x0", ATTR{type}=="1", ATTR{address}=="52:54:00:12:5e:01", NAME="ext0"
You can also use YaST to set a specific NIC name.
Ciao, Alex~
Many thanks. However I do have a different Ethernet device on my Banana Pi M64.
# hwinfo --network 18: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: 5WpM.ndpeucax6V1 Parent ID: Euci.TfPFe67fIBB SysFS ID: /class/net/end0 SysFS Device Link: /devices/platform/soc/1c30000.ethernet Hardware Class: network interface Model: "Ethernet network interface" Driver: "dwmac-sun8i" Driver Modules: "dwmac_sun8i" Device File: end0 HW Address: 02:ba:f7:39:24:a4 Permanent HW Address: 02:ba:f7:39:24:a4 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #3 (Ethernet controller)
So my /etc/udev/rules.d/70-persistent-net.rules, which is currently empty should look like?:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="dwmac_sun8i", ATTR{dev_id}=="0x0", ATTR{type}=="1", ATTR{address}=="02:ba:f7:39:24:a4",NAME="eth0"
Hi Does the kernel boot option net.ifname=0 not work these days? Or just run ip link property add dev end0 altname eth0 as a systemd service then can let the system do it's thing..... -- Cheers Malcolm °¿° (Linux Counter #276890) Tumbleweed 20221120 | GNOME Shell 43.1 | 6.0.8-1-default HP Z440 | Xeon E5-2690 V3 X24 @ 2.60GHz | Nvidia Quadro T400/Nvidia Tesla P4 up 11:53, 2 users, load average: 0.15, 0.37, 0.37
Op dinsdag 22 november 2022 16:05:24 CET schreef Malcolm:
On Tue 22 Nov 2022 03:40:20 PM CST, Freek de Kruijf wrote:
Op dinsdag 22 november 2022 14:52:32 CET schreef Alexander Bergmann:
On Tue, Nov 22, 2022 at 12:55:01PM +0100, Freek de Kruijf wrote:
I just did a 'zypper dup' on an aarch64 Tumbleweed system and lost the Ethernet device.
Instead of having the name eth0 it is now named end0. After copying /etc/sysconfig/network/ifcfg-eth0 to /etc/sysconfig/network/ifcfg-end0 and restarting the network I now see with ip a an UP end0 device. However I
cannot
access the system using ssh because the firewall does not know end0.
How can I rename end0 into eth0 again?
Just have a quick look into your udev rules:
/etc/udev/rules.d/70-persistent-net.rules
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="e1000", ATTR{dev_id}=="0x0",
ATTR{type}=="1", ATTR{address}=="52:54:00:12:5e:01",
NAME="ext0"
You can also use YaST to set a specific NIC name.
Ciao, Alex~
Many thanks. However I do have a different Ethernet device on my Banana Pi M64.
# hwinfo --network 18: None 00.0: 10701 Ethernet
[Created at net.126] Unique ID: 5WpM.ndpeucax6V1 Parent ID: Euci.TfPFe67fIBB SysFS ID: /class/net/end0 SysFS Device Link: /devices/platform/soc/1c30000.ethernet Hardware Class: network interface Model: "Ethernet network interface" Driver: "dwmac-sun8i" Driver Modules: "dwmac_sun8i" Device File: end0 HW Address: 02:ba:f7:39:24:a4 Permanent HW Address: 02:ba:f7:39:24:a4 Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #3 (Ethernet controller)
So my /etc/udev/rules.d/70-persistent-net.rules, which is currently empty should look like?:
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="dwmac_sun8i", ATTR{dev_id}=="0x0", ATTR{type}=="1", ATTR{address}=="02:ba:f7:39:24:a4",NAME="eth0"
Hi Does the kernel boot option net.ifname=0 not work these days?
Or just run ip link property add dev end0 altname eth0 as a systemd service then can let the system do it's thing.....
I tried the shown information in /etc/udev/rules.d/70-persistent-net.rules, except DRIVERS=="dwmac_sun8i" should be DRIVERS=="dwmac-sun8i" and the device name is now back to eth0. Thanks a lot everyone. -- fr.gr. member openSUSE Freek de Kruijf
participants (4)
-
Alexander Bergmann -
Freek de Kruijf -
Guillaume Gardet -
Malcolm