Christoph Egger writes:
I forgot to mention, that the SuSE firewall 7.2 definitely causes my problem.
FreeSWAN works fine for me as long as the firewall is down. But calling "/etc/init.d/SuSEfirewall_init start" and restarting FreeSWAN to not loose its firewall rules already causes my problem.
In a non-related FreeSWAN/VPN comment: I had problems with SuSEfirewall 4.5 on a 2.2 series kernel. It wasn't obeying my security rules where I was Masquerade-forwarding connections from my firewall to my web machine on the masqueraded DMZ connection. Machines on the DMZ or internal couldn't reach the web server by going to the firewall on port 80, even though I had specified: 0/0,internal.web.address,http \ 0/0,internal.web.address,https \ Upgrading to SuSEfirewall 4.9 from http://www.suse.de/~marc/SuSE.html did the trick. -- Argentium G. Tiger (agtiger@kc.rr.com) "Walkin' through Hell in a gasoline suit."