Grr... ok, that might be solved when putting IPSEC in the kernel config,
but the second part still stands, I guess. (Why include libipsec code
when it is in the base tree... they should be compatible)
Just use the port. I presume the included copy of ipsec is there for other
platforms.
On Sat, 15 Jul 2000, Mark Huizer wrote:
Grr... ok, that might be solved when putting IPSEC in the kernel config,
but the second part still stands, I guess. (Why include libipsec code
when it is in the base tree... they should be compatible)
Just use the port. I presume the included
Grr... ok, that might be solved when putting IPSEC in the kernel config,
but the second part still stands, I guess. (Why include libipsec code
when it is in the base tree... they should be compatible)
they are NOT compatible. security/racoon really needs to compile
libipsec by
I'm trying to get racoon to work on my -current machine, but so far
compiling is a horror.
It tries to compile using it's own libipsec, which gives troubles when
starting racoon (pfkey: no such protocol).
Grr... ok, that might be solved when putting IPSEC in the kernel config,
but the
On Fri, 14 Jul 2000, Mark Huizer wrote:
Grr... ok, that might be solved when putting IPSEC in the kernel config,
but the second part still stands, I guess. (Why include libipsec code
when it is in the base tree... they should be compatible)
Just use the port. I presume the included copy of
