Since it had been over a year since I had last used OpenSWAN I couldn't remember why this error occurred. Searching Google for 021 no connection named "blah" was not producing a fix. Finally, and I admit this a little embarrassed I read the manual and found that I had forgot to do after configured the /etc/ipsec.conf file.
user@machine ~> sudo ipsec auto --add myconnection
So if you see the following in the future don't forget to add the connection.
user@machine ~> sudo ipsec whack --name myconnection --initiate
021 no connection named "myconnection"
Tuesday, February 5, 2008
021 no connection named [OpenSWAN]
Posted by
Joseph
at
1:00 PM
5
comments
Labels: linux, linux command, vpn
Restarting Pluto [OpenSWAN]
If you've suffered the same fate as I have...the inability to locate solutions on restarting pluto aside from the infamous RTM this post if for you.
First we'll make sure pluto is running and get the PID
user@machine ~> sudo ipsec setup --status
IPsec running - pluto pid: 8794
pluto pid 8794
No tunnels up
Now we restart everything related to ipsec
user@machine ~> sudo /etc/init.d/ipsec restart
ipsec_setup: Stopping Openswan IPsec...
ipsec_setup: Starting Openswan IPsec 2.4.6...
ipsec_setup: insmod /lib/modules/2.6.22-14-generic/kernel/net/key/af_key.ko
ipsec_setup: insmod /lib/modules/2.6.22-14-generic/kernel/net/ipv4/xfrm4_tunnel.ko
ipsec_setup: insmod /lib/modules/2.6.22-14-generic/kernel/net/xfrm/xfrm_user.ko
Last but not lease lets make sure pluto restarted and has a new PID
user@machine ~> ipsec setup --status
IPsec running - pluto pid: 9193
pluto pid 9193
No tunnels up
There are probably other ways of accomplishing this as well however so if you know please add a comment letting everyone know.
Posted by
Joseph
at
12:57 PM
0
comments
Labels: linux, linux command, vpn