public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. a47376207fbce85385dc6086a87d54ec2e6aa0f1
Date: Tue, 21 Apr 2015 19:53:04 +0200	[thread overview]
Message-ID: <20150421175304.EA4C421EA6@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1409 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  a47376207fbce85385dc6086a87d54ec2e6aa0f1 (commit)
      from  2b4830c5ab71ce04cc14979ec3ed9c91049c8d4c (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 a47376207fbce85385dc6086a87d54ec2e6aa0f1
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date:   Tue Apr 21 19:36:40 2015 +0200

    ipsec: Always enable support for IKE fragmentation

-----------------------------------------------------------------------

Summary of changes:
 html/cgi-bin/vpnmain.cgi | 4 ++++
 1 file changed, 4 insertions(+)

Difference in files:
diff --git a/html/cgi-bin/vpnmain.cgi b/html/cgi-bin/vpnmain.cgi
index 4138f4d..b25cb6a 100644
--- a/html/cgi-bin/vpnmain.cgi
+++ b/html/cgi-bin/vpnmain.cgi
@@ -435,6 +435,10 @@ sub writeipsecfiles {
 	} else {
 	    print CONF "\tauto=start\n";
 	}
+
+	# Fragmentation
+	print CONF "\tfragmentation=yes\n";
+
 	print CONF "\n";
     }#foreach key
     print SECRETS $last_secrets if ($last_secrets);


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2015-04-21 17:53 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=20150421175304.EA4C421EA6@argus.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