Sam Sgro wrote:
I have a problem getting FreeSWAN to work. The problem seems do be the same as described in April 2002 for FreeSWAN 1.92-1.96:
http://lists.freeswan.org/pipermail/bugs/2002-April/000241.html

Have you confirmed the source of the error to be blocked IKE packets with your monitoring program engaged?

Doing a tcpdump on the connection between the routers, intended to etsablish an IPSec-Tunnel, I've seen only a few udp-packets an port 500 going in one direction. Stopping the monitoring program there was a lot more communication(udp,port500) until the tunnel was established. I have not much knowledge about ipsec, but if I have understood the docs right, IKE is done with such udp-packets.
I have also set up a connection between two routers with dachstein, a version of LRP, using FreeSWAN 1.91, using the same ipsec.conf. In this constallation the tunnel is established even if the monitoring-program is active.


My environment:
fli4l 2.0.7
kernel 2.2.22
FreeSWAN 1.99 (authby=secret)
a little program using SOCK_PACKET monitoring all interfaces

The effect is, that the IPSec-Tunnel is not established. After stopping the monitoring-program everything works fine.


Please provide the output of the ipsec barf command, with
plutodebug/klipsdebug=all. This can be large, so accessing it via the web is preferred.

I have put the output of 'ipsec barf' to the following URL: http://www.paranoidtimes.de/ipsec_barf.txt

- -- Sam Sgro
[EMAIL PROTECTED]

Joachim Vogelsang




Reply via email to