3 ms·

Okay, but... what difference does it make? Apart from not having to install it manually? Am I missing something?

• ngetchell 4y ago
  I believe moving wireguard support into the kernel reduces context switching for the app and greatly improves performance.
• RealStickman_ 4y ago
  Wireguard in the kernel is faster than the userspace implementation. You still have to install the tooling.
• rascul 4y ago
  If I recall correctly, we went through this on Linux in the past. I believe the first wireguard implementations were userspace while the work was being done to get it in the kernel.
• jessermeyer 4y ago
  As others have hinted to -- no userspace copies. No context switches. Vroom Vroom.
• kevans91 4y ago
  It depends on how you were running before -- if you had the wireguard-kmod package, then yes, the only difference is that you don't have to install it manually. If you only had the wireguard-go pkg before, then see the other responses where you'll now be using the kernel implementation instead of userspace. edit to note: we can't really provide wg-quick in base at the moment (uses bash-isms), so that still ends up needing installed manually if wg(8) isn't sufficient for your needs.