Wireguard - What the necessary packages now? (22.1)

[vamp]

Hello there,

Now this packages installed my firewall (22.1)



I would like to use built-in kernel version.

"kmod" and "go" packages still need? what the correct way to uninstall it? (i not found it in plugins, only the "os-wireguard ")

[emmitt]

Same question here... 

[franco]

Why does this keep coming up when nothing changed for years?

We use the go implementation since 2019.

Kmod was added in 2021 and is installed MANUALLY.

Please don't forget what you did instantly: install kmod package MANUALLY.

And yes this is the kernel module version you are using.

And no you cannot deinstall go but IT DOES NOT MATTER.

Clear?


Cheers,
Franco

[emmitt]

Thanks for the quick reply even if it is comparatively harsh. But maybe I just feel that way because English is not my native language. 

In 21.x kmod was almost essential for wireguard to work stable and without excessive cpu load.

My question was only if the module is still needed under 22.1 or if you can uninstall it.

[Greelan]

If you want the UI interface you need the plugin, even if WG is using the kmod under the hood

If your question is whether you should continue to use the kmod or revert to the go implementation, my recommendation would be to continue with the kmod if it has been working well for you. The kmod will be faster than the go implementation, and will eventually be the default installation

[franco]

> My question was only if the module is still needed under 22.1 or if you can uninstall it.

Which one? wireguard-go? It cannot be removed because that's what the plugin prefers to use unless you manually install wireguard-kmod additionally. I think I said this.


Cheers,
Franco

[spider]

I can't get the WireGuard interface to work with 22.1. The interface starts, change from tun0 to wg0 and goes down.

Saving the configuration and installing 21.7 plus updates and plugin, and the interface stays up.

- spider.

[franco]

Sorry, wrong thread maybe?


Cheers,
Franco

[spider]

I was uncertain if this needed a new thread. The discussion is about using wireguard-go or the kernel mod and wireguard-go is not working for me. Anyway I'll start a new thread.

- spider

[emmitt]

If you want the UI interface you need the plugin, even if WG is using the kmod under the hood

If your question is whether you should continue to use the kmod or revert to the go implementation, my recommendation would be to continue with the kmod if it has been working well for you. The kmod will be faster than the go implementation, and will eventually be the default installation

Thanks - then I will stay with kmod.

[mic]

Sorry

but I don't understand, which package should I install from the following?

• os-wireguard
• wireguard-go
• wireguard-knod
• wireguard-tools

Thank you

[Patrick M. Hausen]

os-wireguard will give you all you need. It's the official supported OPNsense package.

You can manually pkg install wireguard-kmod on the command line if you feel like you absolutely must use the kernel module. This will work and give better performance (for some value of "better") but there will also be minor issues like e.g. the service state in the dashboard will always be "red" even if WireGuard is running.

Your choice.

[Vesalius]

This frequent question is hopefully put to bed with 22.7 if/when @franco is able to follow through with splitting the plugin into 2 variants, one for the older slower go, and another that automatically installs the kmod package, see links below.

For what little it is worth, I would to make the os-WireGuard the kmod variant and have a separate os-WireGuard-go.

https://forum.opnsense.org/index.php?topic=26971.msg130685#msg130685
https://forum.opnsense.org/index.php?topic=26971.msg130746#msg130746

[kjkent]

...splitting the plugin into 2 variants, one for the older slower go, and another that automatically installs the kmod package...

For what little it is worth, I would to make the os-WireGuard the kmod variant and have a separate os-WireGuard-go.

Just a heads up to anyone stumbling across this thread now while trying to decide on which of the two packages should be installed (this page ranks top of search suggestions for 'opnsense wireguard-go'), Vesalius' comment is now how the packages appear in the UI.

(Apologies for reviving a dead thread -- I hope the potential time it might save others proves worth it.)