Hi Uwe
On Wed, Feb 23, 2011 at 02:26:24PM +0100, Uwe Storbeck wrote:
Hello Harald,
thanks for your offer.
No problem
Meanwhile my VPN is running again.
That's very good to hear!
Not
sure what the exact propblem was. I partially rewrote my config
from scratch, forced the use of the
Hi Harald
Hmmm I understand but this shouldn't have broken your config as the keyword is
still implemented by the parser (and removed keywords should be detected and
alerted by the init script).
I don't think it has broken my config. The best guess I can do
from what I remember is that I had
On Fri, Feb 25, 2011 at 02:09:22PM +0100, Uwe Storbeck wrote:
Hi Harald
Hi Uwe
Hmmm I understand but this shouldn't have broken your config as the keyword
is
still implemented by the parser (and removed keywords should be detected and
alerted by the init script).
I don't think it
Hello Harald,
thanks for your offer. Meanwhile my VPN is running again. Not
sure what the exact propblem was. I partially rewrote my config
from scratch, forced the use of the netkey protocol stack and
had to disable compression. The warnings about the obsolete
keyword probably were caused by the
Dear Uwe Storbeck,
thanks for your report, https://gsoc.xelerance.com/issues/1054 seems to fix
this problem, Rene Mayrhofer and me are currently discussing how to solve this
problem in the best way. In the meantime you may try to debug your ipsec.conf
by using ipsec addconn --checkconfig or, if
Package: openswan
Version: 1:2.6.28+dfsg-5
Severity: normal
The upgrade to squeeze broke my vpn connection. So far I do not
know why, maybe because of obsolete parameters in my config.
But getting a lot of warnings about obsolete keywords without
giving the name of the obsolete keyword and
6 matches
Mail list logo
