Wireguard not starting upon firewall start.

[5SpeedFun]

I am not sure if this is a new problem or not, as in the past, after the firewall rebooted I manually restarted all services.

Now I've created an Lo1 interface to bind services to so that has solved most of my startup problems, however wireguard doesn't auto-start.  I poked through the logs in the gui but I didn't see anything interested.

There isn't an section of wireguard config to bind it to certain interfaces -- afaik it binds to all.  Is anyone else having this issue as well?

[loko3]

The UI wireguard configuration lacks a lot. You should be able to create clients and servers and have it auto start on reboot imho. Feels kind of basic.

[Greelan]

Don’t understand your comment. You can create both local and remote peers, and WG starts on boot automatically. What’s missing?

[loko3]

Running latest version of OpnSense and I need to use wg-quick to be able to connect to my vpn provider (https://www.ovpn.com/en). The GUI doesn't work and seems to lack options like DNS config for example.

[Greelan]

Click on “advanced mode” (top left of local config) and you can see additional options like DNS. Tho be aware that setting DNS in WG on OPNsense overwrites resolv.conf, and so changes it for all of OPNsense, not just WG, so it may break resolution depending on what DNS servers are used. That’s why DNS has been moved to Advanced, as usually it shouldn’t be set unless the user knows what they are doing

Not sure why you have an issue with your provider on boot. Mine connects to Mullvad without fail

[loko3]

Thanks got it to work now

[Greelan]

You probably need to do some reading on WG configuration. This is quite good: https://github.com/pirate/wireguard-docs

On OPNsense, local is the [Interface] config, and Endpoint is the [Peer] config

You don’t just put the same stuff on each peer. They are at opposite ends of the tunnel