After a zypper dup and reboot of my Raspberry Pi 4 it was rendered unreachable, except for via serial console (it is a headless device, wlan is not enabled). Some digging in journalctl -b showed that eth0 was renamed to end0, and end0 was not up and running (seen via command ip ad).
The last version that I have seen to not have this issue is Tumbleweed 20221112.
The solution that I came up with (after a fruitless attempt to solve it via yast2), is copying /etc/sysconfig/network/ifcfg-eth0 to /etc/sysconfig/network/ifcfg-end0. Restarting the network (systemctl restart network.service) made the RPI4 accessible via ethernet again. Later I removed /etc/sysconfig/network/eth0.
Replying to this old post of mine: if turned out that wicked was used on the RPI4, and NetworkManager on the RPI3. Switching the RPI4 to NetworkManager solves the issue as well: end0 is now used as the ethernet device without any additional settings.
The RPI3 still uses eth0 (same Tumbleweed version).
Wicked is being retired from TW, at least via YaST/installation, so newer installations (using NetworkManager) are expected to exhibit different behavior from those configured with Wicked. Systemd-network is a third option, but is not supported in YaST, yet.
I gathered as much. The RPI4 installation started as openSUSE-Tumbleweed-ARM-JeOS-raspberrypi3.aarch64-2020.01.08-Snapshot20200115.raw.xz, so at that time wicked was used. So six days ago I should have had some birthday cake (2020.01.08). Or is it tomorrow (20200115)?
