TerraMaster Forum

Thank you @outkastm!

Hey @Outkastm On 6.0.577 I'm getting a system event error when my F4-424 Pro reboots. Is the kernel module no longer accessible on the latest builds?

You can enable the wireguard module permanently , by editing /etc/modules.load.d/modules.conf
Just add wireguard to the end and reboot the nas.

This way it will be loaded @ boot.

Thanks for this! Have you tested it? I have Tailscale working fine for me at present, but cutting out the middle man and just running wireguard would be a better solution

No, i haven`t tried it , but if you run modinfo wireguard you`ll see it is loaded.

CraftyClown wrote: ↑07 Jan 2025, 07:03

I just updated the command in the task scheduler file.

Wireguard works fine on the latest firmware

outkastm wrote: ↑25 Jan 2025, 03:49

CraftyClown wrote: ↑07 Jan 2025, 07:03

I just updated the command in the task scheduler file.

Wireguard works fine on the latest firmware

Thanks. Can I ask if there's any advantage to activating the module via a task scheduler as opposed to just editing the modules.conf as suggested by fordrwd4ever?

CraftyClown wrote: ↑25 Jan 2025, 04:36

My guess would be that the conf file gets overwritten on updates. (Sometimes even on Boot?) The scheduler should remain as written.

outkastm wrote: ↑25 Jan 2025, 03:49

CraftyClown wrote: ↑07 Jan 2025, 07:03

I just updated the command in the task scheduler file.

Wireguard works fine on the latest firmware

Working great now thank you, although just as a heads up there is a small mistake in your guide! In the port forwarding section you say the protocol should be TCP instead of UDP. Your screengrabs are correct, it's just the text that needs fixing

Thanks, corrected.
Regarding using task scheduler instead of manual editing the file.
More friendly for beginners
As Gremlin said, In case of a firmware update and the file is overwritten, using the task scheduler at shutdown, we can assure that the module is activated at boot