I have OMV hosted as a VM on a proxmox setup (Intel NUC). I assigned an USB network adapter exclusively to this VM. This worked and I was able to set up this (native) network through the OMV GUI. Then I added a VLAN (tagged) to this adapter. The GUI reported success, but in fact it was not successful. After some research on the internet I found out, that the problem is the adapter name, wich is too long. It is assigned by the system automatically. What OMV does for naming the VLAN adapter is extending the interface name with the number of the VLAN. This is exactly when the name gets too long. I found out by using the command "netplan generate". This gives the according error message. Solutions I found in the net suggest a renaming of the interface by Netplan before adding the VLAN. But this doesn't work properly with OMV. It seems not to be recognized by the system, i.e. it does not show up in the GUI. Any ideas?
Network adapter name to long for creating a VLAN
-
votdev
Approved the thread. -
I found out by using the command "netplan generate". This gives the according error message.
I am very surprised that it was then possible to press the apply button in the OMV UI because when the configuration is applied then a netplan apply is called which in turn calls netplan generate. Therefore the error message should also be displayed in the UI.
It would be useful to have some additional information to help you. For example, the systemd journal message from netplan or the name of the interface.Solutions I found in the net suggest a renaming of the interface by Netplan before adding the VLAN.
You can customize the config scripts of OMV by injecting your custom SLS files. See https://docs.openmediavault.or…html#the-saltstack-states and https://github.com/openmediava…/systemd-networkd/netplan for more information.
-
Participate now!
Don’t have an account yet? Register yourself now and be a part of our community!