3 ms·
From the release notes[0]: > Support for NAT-T is now enabled by default. The IPSEC_NAT_T kernel configuration option has been removed. [r315514] (Sponsored by
by Mister_Snuggles 9y ago
From the release notes[0]:
> Support for NAT-T is now enabled by default. The IPSEC_NAT_T kernel configuration option has been removed. [r315514] (Sponsored by Yandex LLC)
All I can say is thank you! I use FreeBSD as, among other things, a VPN server/client and having to recompile my kernel to support IPSec (in 10.3) or to support NAT Traversal (in 11.0) has honestly been my biggest annoyance with FreeBSD. This will make upgrades a LOT easier for me.
Once 11.1 is released, I'm upgrading all of my machines.
[0] https://www.freebsd.org/relnotes/11-STABLE/relnotes/article.html#kernel-config https://www.freebsd.org/relnotes/11-STABLE/relnotes/article....
- kchoudhu 9y agoThank god. I remember being so excited when 11.0 was released, until I found out that that NAT-ing on the VPN interface wasn't possible without recompiling the kernel.
- i_feel_great 9y agoWhat is wrong with recompiling the kernel? Last time I used FreeBSD (also NetBSD), all that it took was to edit some config file and call a shell script. Has it changed from that?
- kchoudhu 9y agoYou can't use freebsd-update if you have to recompile your kernel, which in turn makes it difficult to manage large fleets of servers without running your own freebsd-update server.
- i_feel_great 9y agoAh, OK.
- Mister_Snuggles 9y agoThis is my biggest issue. Updating is basically a case of install updates, recompile kernel, reboot with fingers crossed. I'm scared to upgrade to a new release because of this.