From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core84, updated. 24d36c80a6ce4eef0131dbf22862fb9fbc997478
Date: Sun, 05 Oct 2014 15:13:43 +0200 [thread overview]
Message-ID: <20141005131343.A7A32211AF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1383 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, core84 has been updated
via 24d36c80a6ce4eef0131dbf22862fb9fbc997478 (commit)
from 2a5b19c56f8593e78906d716afe123a6ff0ee6db (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 24d36c80a6ce4eef0131dbf22862fb9fbc997478
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Oct 5 15:12:44 2014 +0200
p2pblock: fix flush rules if all p2p's are allowed.
-----------------------------------------------------------------------
Summary of changes:
config/firewall/rules.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/firewall/rules.pl b/config/firewall/rules.pl
index 20f97be..75a9357 100755
--- a/config/firewall/rules.pl
+++ b/config/firewall/rules.pl
@@ -564,8 +564,8 @@ sub p2pblock {
}
close(FILE);
+ run("$IPTABLES -F P2PBLOCK");
if (@protocols) {
- run("$IPTABLES -F P2PBLOCK");
run("$IPTABLES -A P2PBLOCK -m ipp2p @protocols -j DROP");
}
}
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-10-05 13:13 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=20141005131343.A7A32211AF@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