Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tool does not handle changed network interface names #6

Open
MartinRothschink opened this issue Aug 5, 2024 · 2 comments
Open

Tool does not handle changed network interface names #6

MartinRothschink opened this issue Aug 5, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@MartinRothschink
Copy link

Hi, my upgrade from Debian 11 -> 12 failed today.
My server was set-up with Debian 9 and then upgraded to Debian 10 and 11.

The primary reason is a change of the network interface name.

Instead of eth0, enX0 is used in my case. This change is not handled by the tool currently.

See https://wiki.debian.org/NetworkConfiguration

See [NetworkInterfaceNames](https://wiki.debian.org/NetworkInterfaceNames). Since Stretch, new systems by default no longer use old-style interface names such as eth0, eth1, wlan0, wlan1. The new system uses names based on hardware location, like eno0, enp0s31f6, wlp1s7 (or in the case of USB dongles, MAC address: enx2c56ac39ec0d).

You can list interfaces with: ls /sys/class/net

Various examples below continue to use "eth0" as a default interface name, even though it is unlikely to exist on a modern system.

Upgrading and Network Interface Names
Stretch and Buster still retain support for the old naming system as long as the file /etc/udev/rules.d/70-local-persistent-net.rules is still in place, but users are advised to switch ahead of the upgrade to Bullseye.

@MartinRothschink MartinRothschink added the bug Something isn't working label Aug 5, 2024
@kpushkaryov
Copy link
Contributor

Please give more information about the issue. At what stage did debian11to12 fail, what were the symptoms?

Ideally, provide the feedback archive generated by ./debian11to12 --prepare-feedback.

@MartinRothschink
Copy link
Author

Hi,
It happens after the reboot after the dist upgrade. The machine comes up as Debian 12 without any active network connection and all following steps fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants