OMV will not be aware of this change.
Other than downloading updates, OMV itself has very little need for DNS. It could break docker or something I suppose but there are probably lots of custom wireguard configs that can do that.
Failed to start wg-quick@wgnet_wgvpn0.service - WireGuard via wg-quick(8)
-
- OMV 7.x
- gelöst
- 1Googol
-
-
Other than downloading updates, OMV itself has very little need for DNS. It could break docker or something I suppose but there are probably lots of custom wireguard configs that can do that.
Then what do we do? Do you want me to explain that solution in the documentation?
-
Then what do we do? Do you want me to explain that solution in the documentation?
leave it out of the documentation if hardly anyone will use it and it could break more than it fixes.
-
ok
-
Something new.
Alles anzeigenNew Process.
It turns out to be the problem of my config file,
after switch from resolvconf to systemd-resolved,
DNS = <ip> in the config file also need to change to PostUp = resolvectl dns %i <ip>.
Then no more error.
wg-quick fails with: Failed to resolve interface "tun": No such device
Instead of modify config file for example wg0.conf.
We could just use
Code# enable wg0 systemctl restart wg-quick@wg0 # disable wg0 systemctl stop wg-quick@wg0instead of
Code# enable wg0 wg-quick up wg0 # disable wg0 wg-quick down wg0and everthing works fine.
I also test in openmediavault-wireguard 7.0.1, unlike last time it works well now.
The differences:
- Linux and OMV has been reinstalled.
- I didn't install resolvconf and wireguard(already has wireguard.ko) this time.
- Update from OMV 7.0-16(Sandworm) to OMV 7.0.18(Sandworm).
More info:
This link below is basiclly my usage of wireguard but without docker.
-
We could just use
That systemd unit file is created by the wireguard package itself not the plugin.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!