Hello,

I'm currently in the process of cleaning up and i noticed this bug i
reported is still open.

Based on what we know now i think the bug can be closed.

To summarize:
* the ordering of network interfaces (and therefore the ethn names) was
never meant to be stable and changed with Xen 4.17
* domUs starting with bookworm use enXn by default and their order
matches the config
* bullseye domUs on a bookworm dom0 with more than 10 network interfaces
need a workaround:
* use udev from bullseye-backports and enXn naming scheme
* use custom udev rules to get fixed interface names

Thanks for your help with this issue,
Valentin

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)