4 ms·
Anyone know if this release also includes the recently[1] added in-kernel wireguard? [1]: https://svnweb.freebsd.org/base?view=revision&revision=368163 https:/
by stock_toaster 6y ago
Anyone know if this release also includes the recently[1] added in-kernel wireguard?
[1]: https://svnweb.freebsd.org/base?view=revision&revision=368163 https://svnweb.freebsd.org/base?view=revision&revision=36816...
- codetrotter 6y agoLooks like it does # uname -a FreeBSD freebsd 13.0-BETA1 FreeBSD 13.0-BETA1 #0 releng/13.0-n244471-638e531019f: Fri Feb 5 17:12:07 UTC 2021 root@releng1.nyi.freebsd.org:/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 # kldload if_wg # kldstat Id Refs Address Size Name 1 30 0xffff000000000000 11fd228 kernel 2 1 0xffff0000e1800000 24000 uhid.ko 3 1 0xffff0000e1824000 24000 usbhid.ko 4 1 0xffff0000e1848000 25000 hidbus.ko 5 1 0xffff0000e186d000 25000 wmt.ko 6 1 0xffff0000e1c00000 452000 zfs.ko 7 1 0xffff0000e2052000 52000 if_wg.ko
- stock_toaster 6y agoawesome! thanks for looking! <3
- waynesonfire 6y agoSWEET.
- shassard 6y agoI tried adding the wireguard module to my loader.conf this morning and my VM bombed horribly on reboot. I'm not sure if it's some ordering issue or something else, but use some caution when doing this.
- loeg 6y agoThere's not a ton of reason to load it in loader.conf (which is the bootloader configuration), by the way. The recommended location would be rc.conf kld_list, which is after userspace starts. loader.conf is only really needed for hardware drivers needed to load the operating system from storage devices (and most such drivers are already built in to the kernel).