[Openswan Users] openswan to sonicwall

[Peter McGill]

If ipsec cannot find the connection that is in the conf, then
Either you changed the conf without reloading it, or there is an
Error in the conn which causes it to be discarded.

After updating you conf file, either:
ipsec restart
Or
ipsec auto --replace (conn)
ipsec auto --rereadsecrets
Ie) ipsec auto --replace sonicwall

Check your pluto logs for error's reading the conn.
It may indicate which line in the conn caused the error.
grep -e 'pluto' /var/log/*

Supply us your whole conf, the two lines below are not a whole conf.

Note: 71.36.0.0 is not a valid ip address, you must use a valid public (internet) ip address in left and right.
(left can also be %defaultroute to automatically get your public ip address from the default route.)
(right can also be %any to allow connections from any address.)

Peter McGill
 

> -----Original Message-----
> From: users-bounces at openswan.org 
> [mailto:users-bounces at openswan.org] On Behalf Of Nathan
> Sent: September 1, 2007 10:29 AM
> To: users at openswan.org
> Subject: [Openswan Users] openswan to sonicwall
> 
> I've installed open swan on 3 pcs in my house, 2 sled 10.1 
> and 1 centos
> 5. I follows the instructions on wiki for sonicwall connection. I
> receive the same error on all machine's 021 no connection named
> sonicwall when I type ipsec whack --initiate --name sonicwall
> 
> ipsec.conf
> 
> conn sonicwall
> 	left=71.36.0.0
> 
> What am I doing wrong to keep receiving this error.
> Openswan 2.4.4.1
> 
> Nate
> 
> _______________________________________________
> Users at openswan.org
> http://lists.openswan.org/mailman/listinfo/users
> Building and Integrating Virtual Private Networks with Openswan: 
> http://www.amazon.com/gp/product/1904811256/104-3099591-294632
> 7?n=283155