On Wed, 2011-06-29 at 22:09 +0200, Laurent CARON wrote: > On Wed, Jun 29, 2011 at 01:06:25PM -0700, Tom Eastep wrote: > > Well, Shorewall, by itself, is not causing the IPSEC configuration to > > change totally. Please try switching Shorewall configurations *without* > > restarting OpenSwan. > > I have openswan started and working (shorewall stopped). > I start shorewall with only 1 isp in config => openswan ok > I stop shorewall => openswan still ok > I start shorewall with 2 isp in config => openswan not ok
Then I need another pair of dumps. Because the IPSEC configuration is definitely different in the two you sent my and I know of no way that 'shorewall restart' can cause that. -Tom -- Tom Eastep \ When I die, I want to go like my Grandfather who Shoreline, \ died peacefully in his sleep. Not screaming like Washington, USA \ all of the passengers in his car http://shorewall.net \________________________________________________
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
