From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 95e9415ada2cd29399eec02c2748ca22792ec0a4
Date: Mon, 06 Jan 2014 14:17:33 +0100 [thread overview]
Message-ID: <20140106131733.6743A21543@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1522 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, fifteen has been updated
via 95e9415ada2cd29399eec02c2748ca22792ec0a4 (commit)
from 73cb6627fc3d44ecade787f3fd80cc91d53a42f8 (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 95e9415ada2cd29399eec02c2748ca22792ec0a4
Author: Alexander Marx <amarx(a)ipfire.org>
Date: Mon Jan 6 13:23:48 2014 +0100
firewall: Fix colouring when IPsec VPN subnets are denoted in CIDR.
-----------------------------------------------------------------------
Summary of changes:
html/cgi-bin/firewall.cgi | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/html/cgi-bin/firewall.cgi b/html/cgi-bin/firewall.cgi
index b313d4b..e7884ca 100755
--- a/html/cgi-bin/firewall.cgi
+++ b/html/cgi-bin/firewall.cgi
@@ -1351,6 +1351,7 @@ sub getcolor
#Check if IP is part of a IPsec N2N network
foreach my $key (sort keys %ipsecconf){
my ($a,$b) = split("/",$ipsecconf{$key}[11]);
+ $b=&General::iporsubtodec($b);
if (&General::IpInSubnet($c,$a,$b)){
$tdcolor="style='background-color: $Header::colourvpn;color:white;'";
return;
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-01-06 13:17 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=20140106131733.6743A21543@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