I put together some documentation, commands, and script for getting wireguard running at boot. It can be started/stopped/etc. from the terminal as well.
It handles support for multiple wgX.conf interfaces automatically.
Thanks for your share
I would like to see this functionality incorporated into the official firmware
With a persistent folder for Wireguard *.conf files that survives updates/upgrades would be a huge win. It would allow us to safely update the firmware remotely without losing access.
This feature has been involved in our future firmware released plan, please kindly wait!
Or it would be great if you added a wireguard client to the webui like tailscale
I just allowed an upgrade from 1.4.1 to 1.4.2, and my wireguard configuration was preserved. Did this previously not work, or does it depend on major/minor firmware upgrades?
Since I have updated my KVM to V1.5.0 release1 wireguard does not connect on boot .Could you update the script please ?
I wonder if the remote access work?