No WireGuard kernel module

[duronald]

Hi,

NanoKVM had the Wireguard kernel module loaded so we were able to configure it as a wireguard server. However, NanoKVM Pro does not have the wireguard kernel module and we are unable to use WireGuard. Please add the WireGuard kernel module.

root@kvm-dbe5:# wg setconf wg0 /etc/wireguard/wg0.conf
Unable to modify interface: Protocol not supported
root@kvm-dbe5:# sudo modprobe wireguard
modprobe: FATAL: Module wireguard not found in directory /lib/modules/4.19.125
root@kvm-dbe5:~# lsmod | grep wireguard

[TeutonJon78]

Already a feature request: #39

[916BGAI]

Hi @duronald ,

Thanks for the feedback. We plan to add WireGuard kernel module support in a future NanoKVM-Pro release.

[Th3LaughingMan]

Any chance to have a UI to set it up easily?

[916BGAI]

@duronald @TeutonJon78

The WireGuard kernel module has already been added in the Preview channel.

[Th3LaughingMan]

But can we get a UI to help set it up easier?

[duronald]

Do we know when the preview channel will be merged into main with the WireGuard kernel module?

[duronald]

Closed, wireguard kernel module has been merged into a release and it works. Thank you all!

[duronald]

Nevermind, there's an issue. The WireGuard kernel module loads very late in the boot process, after network-online.target in systemD. This causes wireguard scripts to fail when run through a systemd service at boot. Is this expected behavior?

[916BGAI]

Nevermind, there's an issue. The WireGuard kernel module loads very late in the boot process, after network-online.target in systemD. This causes wireguard scripts to fail when run through a systemd service at boot. Is this expected behavior?

wireguard.ko is located at:

/kvmcomm/ko/wireguard.ko

You can load it earlier in your own startup script .

[duronald]

I modified my service to wait until the WireGuard module was ready and fixed it. Not sure where the existing startup scripts were and didn’t really have time to find out. Thank you for the help!

[Shinmera]

I modified my service to wait until the WireGuard module was ready and fixed it. Not sure where the existing startup scripts were and didn’t really have time to find out. Thank you for the help!

How did you actually do this? I'm not aware of a simple way to have a service wait until a kernel module is ready, and googling fails me, too.