May be you must add :
leftfirewall=yes
rightfirewall=yes
in your :
> >conn vpn_jim
> > # How persistent to be in (re)keying negotiations
> (0 means very).
> > keyingtries=0
> > # RSA authentication with keys from DNS.
> > authby=secret
> > left=10.0.0.4
>
Objet : Re: [leaf-user] trying to get ipsec VPN working
>
...SNIP...
> >#
> ># Shorewall 1.4 - /etc/shorewall/tunnels
> >#
> ># TYPE ZONEGATEWAY GATEWAY
> ># ZONE
> >ipsec
Am Freitag, 4. Juni 2004 22:46 schrieb Jim Walters:
> At this point, I have eleminated all of the errors that displayed on the
> console during the startup phase. When I try to start the VPN connection
> from the command line with "ipsec auto --up vpn_jim" (vpn_jim is the name
> of my vpn tunnel,
Jim
I have a number of ipsec boxes running on Bering 1.0 and 1.2. I must admit
the complexity of your ascii art puzzled me at first.
Basically I understood the following.
You have 2 Bering boxes in Network 10.0.0.0/24 serving as IPSEC gateways
for the networks 192.168.0.0/24 and 192.168.1.0/24
Jim Walters wrote:
Hi,
Thanks for the quick response, Charles! Here are some answers to your good
questions.
1) Is the ipsec service running on startup? Yes. The ipsec service seems
to be running on startup, which is what I want it to do. If I try starting
the service without stopping it, ipsec
nformation
when I have some.
Thanks,
Jim Walters
-Original Message-
From: Charles Steinkuehler [mailto:[EMAIL PROTECTED]
Sent: Friday, June 04, 2004 4:06 PM
To: Jim Walters
Cc: [EMAIL PROTECTED]
Subject: Re: [leaf-user] trying to get ipsec VPN working
Jim Walters wrote:
> Hi All,
>
Jim Walters wrote:
Hi All,
I have been a happy LRP and LEAF user for a number of years now. Thanks for
all the great work! I started messing with LRP for fun and began production
use at some offices with LRP 2.9.4. The offices have been updated over the
years, moving up through Dachstein and Eig
