Re: -current, racoon, ipsec
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. Which coredumps when there is no matching SPD in the list, but well,that's minor. The other thing is that I haven;t gotten a single encrypted session to work, but that will wait until after the holiday :) Mark -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, racoon, ipsec
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 copy of ipsec is there for other platforms. Which coredumps when there is no matching SPD in the list, but well,that's minor. The other thing is that I haven;t gotten a single encrypted session to work, but that will wait until after the holiday :) You should *definitely* talk to the KAME guys with any bugs you find in racoon. I have a couple of problems I discovered in my testing tonight prior to the 4.0 merge, and there are still 5 days until the ports freeze in which to correct them. *Any* help you can give to sumikawa-san will mean a better IPSEC-enabled 4.1-RELEASE. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, racoon, ipsec
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 itself. itojun To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
-current, racoon, ipsec
Hi, 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). So... I tried using the system libipsec, which has pfkey and pfkey_dump commented in the source file. Tried to put these in, and ipsec_hexdump is missing. Does anyone have this working and how? Mark -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, racoon, ipsec
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 second part still stands, I guess. (Why include libipsec code when it is in the base tree... they should be compatible) So... I tried using the system libipsec, which has pfkey and pfkey_dump commented in the source file. Tried to put these in, and ipsec_hexdump is missing. Does anyone have this working and how? Mark -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Nice testing in little China... To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: -current, racoon, ipsec
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 ipsec is there for other platforms. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
