From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 25ac8dbdcf88184daa9e41bcc4cc489a5d3a5f11
Date: Fri, 25 Apr 2025 10:31:15 +0000 (UTC) [thread overview]
Message-ID: <4ZkTdv3rWKz2y6T@people01.haj.ipfire.org> (raw)
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 25ac8dbdcf88184daa9e41bcc4cc489a5d3a5f11 (commit)
from 9638ab6ea9223e41dc21bc52ee189ab760c02327 (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 25ac8dbdcf88184daa9e41bcc4cc489a5d3a5f11
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Fri Apr 25 12:30:37 2025 +0200
wireguard-functions.pl: Dereference another array for local subnets
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/cfgroot/wireguard-functions.pl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/cfgroot/wireguard-functions.pl b/config/cfgroot/wireguard-functions.pl
index 8fd873d74..219f9282d 100644
--- a/config/cfgroot/wireguard-functions.pl
+++ b/config/cfgroot/wireguard-functions.pl
@@ -388,7 +388,7 @@ sub generate_peer_configuration($$) {
my @allowed_ips = ();
# Convert all subnets into CIDR notation
- foreach my $subnet ($peer->{'LOCAL_SUBNETS'}) {
+ foreach my $subnet (@{ $peer->{'LOCAL_SUBNETS'} }) {
my $netaddress = &Network::get_netaddress($subnet);
my $prefix = &Network::get_prefix($subnet);
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-04-25 10:31 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=4ZkTdv3rWKz2y6T@people01.haj.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