Hello,
I was facing a problem where network interfaces name changes whenever the NVMe SSD is added or removed from the motherboard
Without SSD:
- Built-in NIC = enp1s0
- PCIe NIC = enp2s0
- USB NIC = enx00909e9d7a7a
With SSD installed:
- Built-in NIC = enp2s0
- PCIe NIC = enp3s0
- USB NIC = enx00909e9d7a7a
It looks like the NVMe SSD takes a higher priority in the motherboard and shifts the address for all other PCIe devices by 1
USB NIC was not affected
This change in interface name breaks macvtap networks for KVM and docker
The solution I found is to force a static name for the interfaces using .link files in /etc/systemd/network/
so I just renamed the PCIe NIC to lan1.
I didn't rename the Built-in NIC as it might break something because it is the interface OMV uses while the others are for VMs, and docker.
It worked just fine from the Debian side
root@Z0-NAS-01:~# ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master br0 state UP group default qlen 1000
link/ether 2c:f0:5d:96:bd:08 brd ff:ff:ff:ff:ff:ff
3: lan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:31:92:17:cb:fa brd ff:ff:ff:ff:ff:ff
inet6 fe80::231:92ff:fe17:cbfa/64 scope link
valid_lft forever preferred_lft forever
4: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 2c:f0:5d:96:bd:08 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.32/24 brd 10.0.0.255 scope global br0
valid_lft forever preferred_lft forever
5: enx00909e9d7a7a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:90:9e:9d:7a:7a brd ff:ff:ff:ff:ff:ff
inet6 fe80::290:9eff:fe9d:7a7a/64 scope link
valid_lft forever preferred_lft forever
7: macvtap0@enx00909e9d7a7a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 500 link/ether 52:54:00:01:26:60 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fe01:2660/64 scope link
valid_lft forever preferred_lft forever
---
82: macvtap1@enx00909e9d7a7a: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 500
link/ether 52:54:00:59:ea:58 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fe59:ea58/64 scope link
valid_lft forever preferred_lft forever
83: macvtap2@lan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 500
link/ether 52:54:00:f7:06:a6 brd ff:ff:ff:ff:ff:ff
inet6 fe80::5054:ff:fef7:6a6/64 scope link
valid_lft forever preferred_lft foreverBut the new interface was missing from OMV GUI
and KVM plugin too (probably because it reads the interface names from the same database as OMV)
For KVM it was an easy fix with command virsh net-define
I know OMV doesn't like changes from CLI
Problem #2: I mounted the drive using the command line or GUI tool and I can't pick that drive in the shared folder device dropdown.
Solution #2: Never mount a drive with anything other than the OMV web interface. This creates the necessary database entries to populate the device dropdown.
So is there a way for me to manually add this interface to OMV database, a command to scan the interfaces again or maybe (just maybe) impelling a way to rename interface from GUI.
