From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e7204c2d95f34802c2719cce613e4c7aafabb687
Date: Thu, 21 Aug 2014 16:13:59 +0200 [thread overview]
Message-ID: <20140821141359.DD87B21101@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1654 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 e7204c2d95f34802c2719cce613e4c7aafabb687 (commit)
from 6de2306a6a7f8836c5d5ea7f1541a2cf68a09377 (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 e7204c2d95f34802c2719cce613e4c7aafabb687
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Aug 21 16:12:43 2014 +0200
firewall: Fix initialization when RED has not been brought up yet
-----------------------------------------------------------------------
Summary of changes:
src/initscripts/init.d/firewall | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/src/initscripts/init.d/firewall b/src/initscripts/init.d/firewall
index 0d80e7c..c7f8b67 100644
--- a/src/initscripts/init.d/firewall
+++ b/src/initscripts/init.d/firewall
@@ -369,8 +369,10 @@ iptables_red_down() {
# while the wan interface is down - this is required to
# circumvent udp related NAT issues
# http://forum.ipfire.org/index.php?topic=11127.0
- iptables -F REDFORWARD
- iptables -A REDFORWARD -o $IFACE -j DROP
+ if [ -n "${IFACE}" ]; then
+ iptables -F REDFORWARD
+ iptables -A REDFORWARD -o "${IFACE}" -j DROP
+ fi
# Reload all rules.
/usr/local/bin/firewallctrl
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-08-21 14: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=20140821141359.DD87B21101@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