From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b228aaf09d2c769535157440430d08a0f26b0e30
Date: Wed, 21 Nov 2012 16:56:16 +0100 [thread overview]
Message-ID: <20121121155616.B7D49203A1@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1445 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 b228aaf09d2c769535157440430d08a0f26b0e30 (commit)
from e81be1e1edb0df7e11c305938838caa6c776ae8c (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 b228aaf09d2c769535157440430d08a0f26b0e30
Author: Stefan Schantl <stefan.schantl(a)ipfire.org>
Date: Tue Nov 20 19:26:13 2012 +0100
ovpnmain.cgi: Path MTU Discovery defaults to Off on Net-to-Net connections.
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/ovpnmain.cgi | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/html/cgi-bin/ovpnmain.cgi b/html/cgi-bin/ovpnmain.cgi
index 9ae2a5f..9ab06fe 100755
--- a/html/cgi-bin/ovpnmain.cgi
+++ b/html/cgi-bin/ovpnmain.cgi
@@ -4012,6 +4012,7 @@ if ($cgiparams{'TYPE'} eq 'net') {
###
$cgiparams{'MSSFIX'} = 'on';
$cgiparams{'FRAGMENT'} = '1300';
+ $cgiparams{'PMTU_DISCOVERY'} = 'off';
###
# m.a.d n2n end
###
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-11-21 15:56 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=20121121155616.B7D49203A1@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