Advertisement
Guest User

Drin - IPSEC

a guest
Apr 20th, 2016
293
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.27 KB | None | 0 0
  1. Gentlemen,
  2.  
  3. First I'd like to thank you for discussing this question on the show, and those who wrote in in response. It turned out that in order to get the ike IPSEC client working I had to enable both IPSEC and IPSEC_NAT_T in my custom kernel. Alan mentioned that IPSEC will be a default in 11, will that also be true for IPSEC_NAT_T? I ask, and this is what prompted another email, because I'm finding managing updates to be a bit of a pain. Whenever I use freebsd-update the OS reverts to the GENERIC kernel after a reboot and I have to rebuild and reinstall my custom kernel. Doing so is straight forward enough but seems to break iked and I have to rebuild it again from from ports - I can't reinstall using pkg as it doesn't seem to have been compiled with IPSEC NAT traversal which I require. Is there an easier way of managing updates when using a custom kernel? Or should I consider switching to CURRENT on my laptop? I think you're mentioned on the show that running CURRENT is reasonably safe but I'm still deterred somewhat by the warnings on the freebsd.org site (specifically "The snapshots are primarily for testing purposes and not fully tested compared to the releases. They may include experimental or degraded features that can corrupt your existing system.").
  4.  
  5. Thanks again,
  6. Drin
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement