From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: network@lists.ipfire.org
Subject: [PATCH 6/7] ipv6-auto: prevent multiple configs for the same zone
Date: Tue, 04 Jul 2017 17:46:10 +0200 [thread overview]
Message-ID: <1499183171-24236-6-git-send-email-jonatan.schlag@ipfire.org> (raw)
In-Reply-To: <1499183171-24236-1-git-send-email-jonatan.schlag@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
It is senseless to configure the ipv6-auto hook
multiple times for a zone.
Signed-off-by: Jonatan Schlag <jonatan.schlag(a)ipfire.org>
---
src/hooks/configs/ipv6-auto | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/hooks/configs/ipv6-auto b/src/hooks/configs/ipv6-auto
index 44cef48..c362797 100644
--- a/src/hooks/configs/ipv6-auto
+++ b/src/hooks/configs/ipv6-auto
@@ -34,6 +34,11 @@ hook_new() {
local zone="${1}"
shift
+ if zone_config_hook_is_configured ${zone} "ipv6-auto"; then
+ log ERROR "You can configure the ipv6-auto hook only once for a zone"
+ return ${EXIT_ERROR}
+ fi
+
while read arg; do
case "${arg}" in
--privacy-extensions=*)
--
2.6.3
next prev parent reply other threads:[~2017-07-04 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 15:46 [PATCH 1/7] settings: remove dot from log message Jonatan Schlag
2017-07-04 15:46 ` [PATCH 2/7] inetcalc: do not print the default prefix Jonatan Schlag
2017-07-04 15:46 ` [PATCH 3/7] zone: add function to avoid multiple configs which are senseless Jonatan Schlag
2017-07-04 16:07 ` Michael Tremer
2017-07-04 15:46 ` [PATCH 4/7] ipv4-dhcp: prevent multiple configs for the same zone Jonatan Schlag
2017-07-04 15:46 ` [PATCH 5/7] ipv6-dhcp: " Jonatan Schlag
2017-07-04 15:46 ` Jonatan Schlag [this message]
2017-07-04 15:46 ` [PATCH 7/7] pppoe-server: " Jonatan Schlag
2017-07-04 16:06 ` [PATCH 1/7] settings: remove dot from log message Michael Tremer
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=1499183171-24236-6-git-send-email-jonatan.schlag@ipfire.org \
--to=jonatan.schlag@ipfire.org \
--cc=network@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