Bug in wireguard ? Cant start more than 3 wireguard-servers.

[zitlo]

/usr/local/etc/rc.d/wireguard restart

Thank you!

Wireguard restarts just fine, /usr/local/etc/rc.d/wireguard status is showing also an correct output... My wireguard service status inside the gui is red...

Edit:
- I deleted all configurations inside /usr/local/etc/rc.d/wireguard and inside the gui
- I uninstalled the wireguard plugin
- Then I restarted opnsense.
- I innstalled the plugin again
- I created a new configuration

Same problem, gui status showing red and service is starting on cli

[Patrick M. Hausen]

Are you using the kmod? If yes, the dashboard will always show a wrong state of the service. You can remove the WireGuard service from the services widget and add the WireGuard widget instead, which gives you an overview of all your peers.

[zitlo]

Hello pmhausen,

I dont know what kmod is, but now I discovered (after I uninstalled the wireguard plugin) that I have an unassigned interface (wg0). How can I delete it? from the gui it is not possible

[Patrick M. Hausen]

You have (and need) a wgN interface for each WireGuard server that is up and running. If you just uninstalled WG, the interfaces might be left - a reboot will fix that.

You do not need to assign the interfaces.

A kmod is a kernel module. If you did a `pkg install wireguard-kmod` on the command line, you will be running that instead of wireguard-go. Everything will supposedly work just the same but the service status on the dashboard will be broken.

[zitlo]

Thank you for your help!

[dmmincrjr]

I'm having an issue where I can't get one interface to start after the upgrade and I can't figure it out as the config file works in 21.7.8 but not after the upgrade. I have 3 sites that I'm using Wireguard to connect and two of those sites I have upgraded to 22.1 and Wireguard worked without issue.

Edit:

I did finally figure out the issue. I had a misconfiguration of the Allowed IP's in the tunnel. The strange thing was the tunnel worked with the misconfiguration in versions up to 21.7.8 for a couple years which is why I had assumed my configuration was correct and something else was the problem.