From: Larsen <larsen007@web.de>
To: development@lists.ipfire.org
Subject: IPsec: Default to rekey=no
Date: Tue, 19 May 2015 17:19:31 +0200 [thread overview]
Message-ID: <op.xyv16t1gcahio0@atl-uetersen.atlantisgmbh.local> (raw)
[-- Attachment #1: Type: text/plain, Size: 653 bytes --]
Hi,
we noticed interruptions with our IPsec roadwarrriors. The problem turned
out to be caused by the server trying to rekey with the client that is
sitting behind a NAT (Windows 7 client at colleague's home). See
https://wiki.strongswan.org/projects/strongswan/wiki/Windows7#Rekeying-behavior
This was solved by adding "rekey=no" to "/etc/ipsec.user.conf" for each
connection.
I wonder if this should be added by IPFire by default as I guess that all
roadwarriors behind a NAT (probably the majority) might have this problem.
So, adding
print CONF "\trekey=no\n";
to
/srv/web/ipfire/cgi-bin/vpnmain.cgi
Lars
next reply other threads:[~2015-05-19 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 15:19 Larsen [this message]
2015-05-19 15:45 ` Michael Tremer
2015-05-19 15:56 ` Larsen
2015-05-19 16:06 ` Michael Tremer
2015-05-20 8:54 ` Wolfgang Apolinarski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=op.xyv16t1gcahio0@atl-uetersen.atlantisgmbh.local \
--to=larsen007@web.de \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox