Hi
I have 2 Bering 1.0_stable stations with FreeSwan 1.99 running over a
wireless link. Occasionally (especially on rainy and stormy days) the
tunnel breaks down. If I stop ipsec on one end and ping the remote ipsec
gateway I get good results. Starting the tunnel again removes the
capability
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We thought that we had a successful tunnel between our side, with DCD
gateway and freeswan v1.91, and a client with a cisco router. Both
sides successfully ping each other; but, the application on our side
cannot establish a tcp connection to the
Hi Lynn
I got it up and running after some debugging, finally it seems to boil down
to the fact that the zywall supports ranges on the ip addresses whereas
freeSwan only supports entire subnets. For ipsec a range from 0 to 255 is
_NOT_ a subnet.
I have now a tunnel between a Zywall10 and a
Hi everyone
I am finally attacking the ipsec connection planned for months,
unfortunately whithout much success, here is what I am trying:
internal C class network 194.124.158.0/24
|
Bering rc3
217.162.140.106
|
Internet through cable modem on both ends
actually hooked on the same switch which
On Sunday 17 November 2002 09:03, Erich Titl wrote:
+ sed -n 17,$p /var/log/messages
+ egrep -i ipsec|klips|pluto
+ cat
Nov 17 14:58:17 gatekeeper kernel: klips_info:pfkey_cleanup: shutting
down PF_KEY domain sockets.
Nov 17 15:07:26 gatekeeper kernel: klips_info:pfkey_cleanup: shutting
Hello,
I have setup an IPSec vpn for our office network. Our firewall is a Debian Woody
box with shorewall 1.2. It shares our DSL connection. Following the
documentation, I have enabled a roadwarrior type tunnel like this:
# TYPE ZONEGATEWAY GATEWAY ZONE
On Monday 28 October 2002 13:11, Mathieu Gauthier-Pilote wrote:
The exact problem with this one Win2k box is that the firewall drops
packets arriving on UDP port 500. Do I need to setup the tunnel
differently with Shorewall? I guess I could just apply global rules
to let all IPSec traffic in,
