From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8089b78d9d955cc7b4c4a6284b2499c9e234a799
Date: Sat, 29 Mar 2014 15:07:12 +0100 [thread overview]
Message-ID: <20140329140716.2BC7B20A37@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2558 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 8089b78d9d955cc7b4c4a6284b2499c9e234a799 (commit)
from ea219d3a0f77a4d45cf42d8e7d3ee9dc3db63bbc (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 8089b78d9d955cc7b4c4a6284b2499c9e234a799
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Mar 29 15:06:35 2014 +0100
firewall-policy: fix drop and logging on red0;
-----------------------------------------------------------------------
Summary of changes:
config/firewall/firewall-policy | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
Difference in files:
diff --git a/config/firewall/firewall-policy b/config/firewall/firewall-policy
index 2c583c5..6990fa9 100755
--- a/config/firewall/firewall-policy
+++ b/config/firewall/firewall-policy
@@ -112,11 +112,29 @@ case "${POLICY}" in
*)
if [ -n "${IFACE}" ]; then
if [ "${HAVE_BLUE}" = "true" ] && [ -n "${BLUE_DEV}" ]; then
+ if [ "${DROPFORWARD}" = "on" ]; then
+ iptables -A POLICYFWD -i "${BLUE_DEV}" ! -o "${IFACE}" -m limit --limit 10/minute -j LOG --log-prefix "DROP_FORWARD "
+ fi
iptables -A POLICYFWD -i "${BLUE_DEV}" ! -o "${IFACE}" -j DROP
fi
if [ "${HAVE_ORANGE}" = "true" ] && [ -n "${ORANGE_DEV}" ]; then
+ if [ "${DROPFORWARD}" = "on" ]; then
+ iptables -A POLICYFWD -i "${ORANGE_DEV}" ! -o "${IFACE}" -m limit --limit 10/minute -j LOG --log-prefix "DROP_FORWARD "
+ fi
iptables -A POLICYFWD -i "${ORANGE_DEV}" ! -o "${IFACE}" -j DROP
fi
+
+ if [ "${DROPFORWARD}" = "on" ]; then
+ iptables -A POLICYFWD -i "${IFACE}" -m limit --limit 10/minute -j LOG --log-prefix "DROP_FORWARD "
+ fi
+ iptables -A POLICYFWD -i "${IFACE}" -j DROP
+
+ if [ "${IFACE}" != "${RED_DEV}" ]; then
+ if [ "${DROPFORWARD}" = "on" ]; then
+ iptables -A POLICYFWD -i "${RED_DEV}" -m limit --limit 10/minute -j LOG --log-prefix "DROP_FORWARD "
+ fi
+ iptables -A POLICYFWD -i "${RED_DEV}" -j DROP
+ fi
fi
iptables -A POLICYFWD -j ACCEPT
iptables -A POLICYFWD -m comment --comment "DROP_FORWARD" -j DROP
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-03-29 14:07 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=20140329140716.2BC7B20A37@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