[ale] freeswan

[James P. Kinney III]

Yep. That issue is open on the desk! Part of the reason for working on
this is the issue in Linux Journal and I have some wireless stuff and a
laptop and my basement office is rather cold.

On Fri, 2002-12-13 at 21:18, Geoffrey wrote:
> I've not read it yet, but there is an article on installation and such 
> of freeswan in the most recent Linux Journal.  I don't know if it's 
> available on line.
> 
> James P. Kinney III wrote:
> > I'm trying to set up a FreeS/Wan VPN. I've got the latest tools and
> > toys. Cookbooked a basic configuration copied from Nate
> > http://www.natecarlson.com/linux/
> > 
> > When the ipsec starts, the actual communication part, pluto, immediately
> > dies with a "signal 8". 
> > 
> > ?????
> > 
> > Has anyone used Frees/Wan lately? Has anyone a clue as to what this
> > means?  From the "turned on all debugging" error log:
> > 
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_msg_hdr_build:
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_msg_hdr_build: on_entry
> > &pfkey_ext=c6769d70 pfkey_ext=c6769d9c *pfkey_ext=00000000.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_msg_hdr_build: on_exit
> > &pfkey_ext=c6769d70 pfkey_ext=c6769d9c *pfkey_ext=c75566a0.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_safe_build: error=0
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_safe_build:success.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_safe_build: error=0
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_safe_build:success.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_msg_build:
> > pfkey_msg=cb4c44b0 allocated 56 bytes, &(extensions[0])=c6769d9c
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_msg_build: copying 40
> > bytes from extensions[15]=cb4c45f0 to=cb4c44c0
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_msg_build: extensions
> > permitted=0000c001, seen=00008001, required=00000001.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_upmsg: allocating 56
> > bytes...
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_upmsg: ...allocated at
> > cafe64f0.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_register_reply: sending
> > up register message for satype=9(IPIP) to socket=cb7a2ac4 succeeded.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_release: sock=cb7a2ac4
> > sk=c45b1140
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_destroy_socket: .
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_remove_socket: .
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_remove_socket:
> > succeeded.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_destroy_socket:
> > pfkey_remove_socket called.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_destroy_socket:
> > sk(c45b1140)->(&c45b1188)receive_queue.{next=c45b1188,prev=c45b1188}.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_destroy_socket:
> > destroyed.
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_list_remove_socket:
> > removing sock=cb7a2ac4
> > Dec 13 09:28:39 castle last message repeated 7 times
> > Dec 13 09:28:39 castle ipsec__plutorun: !pluto failure!:  exited with
> > error status 136 (signal 8)
> > Dec 13 09:28:39 castle kernel: klips_debug:pfkey_list_remove_socket:
> > removing sock=cb7a2ac4
> > Dec 13 09:28:39 castle ipsec__plutorun: restarting IPsec after pause...
> > 
> > 
> > It's the !pluto failure!: line where it all dies. And that is at the
> > beginning of the plutorun script that generates the error.
-- 
James P. Kinney III   \Changing the mobile computing world/
President and CEO      \          one Linux user         /
Local Net Solutions,LLC \           at a time.          /
770-493-8244             \.___________________________./

GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics) <jkinney at localnetsolutions.com>
Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7 



 This is a digitally signed message part