Please try omv-firstaid and reconfigure the network interface.
Gesendet von meinem ARIA mit Tapatalk
Please try omv-firstaid and reconfigure the network interface.
No, always "ping: unknown host google.com", both with DHCP or Static IP address.
Instead "ping 8.8.8.8" is OK.
I've also tried to connect OMV directly to the router with DHCP, bypassing the firewall. Same result.
This is most likely for resolv.conf loosing its symlink. The symlink allows dynamic changes of resolv.conf
Run this command
dpkg-reconfigure resolvconf
And when ask for dynamic updates say yes.
Configure the interface to use dhcp this time and save and apply. Check dns resolving and inspect /etc/resolv.conf file has the dns server obtained from the dhcp server (router )
I found that no network interface was defined in openmediavault. I don't really understand why this is something you have to setup manually, because it was configured in Debian 12 prior to installing OMV7. But, adding a network interface in Network > Interfaces with the + button seems to have fixed the issue, both for OMV and it also took effect immediately in the shell. Without having looked into the cause other than this, I assume OMV7 is trashing any resolv.conf changes, and when you add the NIC into OMV it adds all the necessaries. I just added the only NIC it showed in the list with settings to DHCP. No customisation.
I found that no network interface was defined in openmediavault. I don't really understand why this is something you have to setup manually, because it was configured in Debian 12 prior to installing OMV7.
OMV tries to import the existing network configuration, but this might not work for every system and several Debian derivates.
OMV tries to import the existing network configuration, but this might not work for every system and several Debian derivates.
Must be a bug because it's a vanilla amd64 install of Debian 12. Haven't done anything to it. It nuked the working config.
Must be a bug because it's a vanilla amd64 install of Debian 12. Haven't done anything to it. It nuked the working config.
This is not a bug, the import just does not support all options.
Contributions from the community are welcome to improve that. But I can tell you right away that this will not be an easy undertaking since all the Debian derivatives on which OMV runs use different systems, for example systems-networkd, ifupdown or network-manager.
At the end omv-firstaid can be used to reconfigure the network setting from CLI.
Must be a bug because it's a vanilla amd64 install of Debian 12. Haven't done anything to it. It nuked the working config.
BTW, the documentation explicitly is mentioning how and when the network settings are imported, see https://docs.openmediavault.or…ml#installation-on-debian.
Don’t have an account yet? Register yourself now and be a part of our community!
