From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4cd51e20ae17ee55e46708650055727cffe3443a
Date: Thu, 19 Apr 2018 15:37:58 +0100 [thread overview]
Message-ID: <20180419143758.E0F701081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 4cd51e20ae17ee55e46708650055727cffe3443a (commit)
from bbaa7993bd99d0e31145f84277861fd8dbde3e34 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 4cd51e20ae17ee55e46708650055727cffe3443a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Apr 19 15:36:37 2018 +0100
Revert "IPsec: Try to restart always-on tunnels immediately"
This reverts commit a261cb06c6cdd3ba14ad0163c8c9e714ae94fc5b.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/vpnmain.cgi | 6 ------
1 file changed, 6 deletions(-)
Difference in files:
diff --git a/html/cgi-bin/vpnmain.cgi b/html/cgi-bin/vpnmain.cgi
index a52b4d64d..378acb326 100644
--- a/html/cgi-bin/vpnmain.cgi
+++ b/html/cgi-bin/vpnmain.cgi
@@ -436,12 +436,6 @@ sub writeipsecfiles {
if ($start_action eq 'route' && $inactivity_timeout > 0) {
print CONF "\tinactivity=$inactivity_timeout\n";
}
-
- # Restart the connection immediately when it has gone down
- # unexpectedly
- if ($start_action eq 'start') {
- print CONF "\tcloseaction=restart\n";
- }
}
# Fragmentation
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-04-19 14:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180419143758.E0F701081DF2@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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