On Mon, Jun 07, 2021 at 12:16:46AM +0700, Robert Elz wrote:
> It turns out there is another fix needed, in vfs_vnops.c
> [...]
Ugh :-| there's no such thing as a simple namei change, everything
one touches causes more of the chewing gum to fall off.
I've adjusted my copy of the changes and I
Date:Sun, 06 Jun 2021 00:28:50 +0700
From:Robert Elz
Message-ID: <28802.1622914...@jinx.noi.kre.to>
Once more, into the self-reply...
| (all the rest of the files
| your patch modified are as you modified them).
It turns out there is another fix needed, in
On Sun, Jun 06, 2021 at 05:53:37AM -0700, Andy Ruhl wrote:
> Hopefully this helps someone searching:
>
> The options(4) man page shows this line:
>
> strings netbsd | sed -n 's/^_CFG_//p' | unvis (note that "netbsd" is
> the kernel file, usually at /netbsd)
>
> This will work if the kernel has
On Sun, Jun 6, 2021 at 2:49 AM Matthias Petermann wrote:
>
> ...looks like the IPSEC_NAT_T option no longer exists, but is included
> in IPSEC instead.
>
>
> OPTIONS(4):
>
> "
> options IPSEC
> Includes support for the IPsec protocol, using the implementation
> derived
> from
...looks like the IPSEC_NAT_T option no longer exists, but is included
in IPSEC instead.
OPTIONS(4):
"
options IPSEC
Includes support for the IPsec protocol, using the implementation
derived
from OpenBSD, relying on opencrypto(9) to carry out cryptographic
operations.
Hello,
the subject probably already summarises the question - here is just a
brief background: I would like to establish an IPSEC connection from a
NetBSD box behind a NAT router to a IPSEC-VPN. My understanding is that
the kernel must have the appropriate IPSEC_NET_T-option for this. Can I
