[SOLVED] How to re-enable networking when moving boot disk to new hardware?

[gctwnl]

I have moved my boot and data disks from an Intel NUC 10th generation to an ASUS NUC 13th generation. This works for now, except for one essential thing: networking.

I suspect that as PVE was installed on different ethernet hardware, it might be loading the wrong drivers. Or there is another reason.

What can I do to fix this?

1. Remove /etc/udev/rules.d/60-bridge-network-interface.rules
2. Find new name of ethernet device via ip link
3. Edit /etc/network/interfaces, make sure it uses new name
4. Reboot

Then the local stack works and if you properly plug in the ethernet cable, so does the rest...

 

[cheiss]

I suspect that as PVE was installed on different ethernet hardware, it might be loading the wrong drivers. Or there is another reason.

Drivers are normally loaded automatically by the kernel based on detected PCI IDs.

Most likely the interface name is different - each hardware/firmware combination tends to enumerate PCI devices in a different order and manufacturers place devices at different places on the bus, at least on consumer hardware this commenly is a problem.

1. Remove /etc/udev/rules.d/60-bridge-network-interface.rules

Why, where did you get this from? This a) is normally symlinked to /dev/null and b) has nothing to do with interface naming?

2. Find new name of ethernet device via ip link
3. Edit /etc/network/interfaces, make sure it uses new name

Yes, these are the correct steps. You might also need to check the following other files for the old interface name:

- /etc/pve/nodes/<nodename>/host.fw
- /etc/pve/sdn/controllers.cfg
- /etc/pve/sdn/fabrics.cfg

You can also pin interface names based on MAC addresses beforehand: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_manually_creating_link_files

 

[gctwnl]

Thank you.

I searched for a lot of things. I found things that said these rules were regenerated if necessary and I (mis)understood they were implicated in naming of devices. Probably something like this https://support.tilaa.com/hc/en-us/...work-Issues-after-Cloning-Removing-UDEV-Rules but these are for older distributions. I really do not recall, been at it for a while (but then I found out I had not plugged in the ethernet cable fully, which probably made me go too far along the device naming route in trying to get it to work.

I noticed they weren't recreated, but the networking works. Did I damage something? Should I repair something?

 

[cheiss]

Did I damage something? Should I repair something?

No, in this case this file doesn't do anything anyway (it's by default a symlink to /dev/null); I primarily wanted to highlight to never delete system files if you don't know exactly what they are doing.