All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: "José Pekkarinen" <jose.pekkarinen@unikie.com>,
	buildroot@buildroot.org, "Baruch Siach" <baruch@tkos.co.il>
Subject: Re: [Buildroot] [PATCH v3] package/iptables: add init script
Date: Wed, 22 Sep 2021 23:33:56 +0200	[thread overview]
Message-ID: <12c37043-7099-cba8-3394-48501f377502@mind.be> (raw)
In-Reply-To: <20210915130620.3162787-1-jose.pekkarinen@unikie.com>



On 15/09/2021 15:06, José Pekkarinen wrote:
> This patch will add an init script that allows
> to set a ruleset in /etc/iptables.conf to be loaded
> on boot, or flushed on stop, as well as a saving
> command to generate a new file.
> 
> Signed-off-by: José Pekkarinen <jose.pekkarinen@unikie.com>
> ---
> [v1 -> v2] s/touch $(DESTDIR)/touch $(TARGET_DIR)/
> [v2 -> v3] Execute before networking script, handle ro rootfs
> 
>   package/iptables/S35iptables | 62 ++++++++++++++++++++++++++++++++++++
>   package/iptables/iptables.mk |  6 ++++
>   2 files changed, 68 insertions(+)
>   create mode 100644 package/iptables/S35iptables
> 
> diff --git a/package/iptables/S35iptables b/package/iptables/S35iptables
> new file mode 100644
> index 0000000000..6023297236
> --- /dev/null
> +++ b/package/iptables/S35iptables
> @@ -0,0 +1,62 @@
> +#!/bin/sh
> +
> +DAEMON="iptables"
> +
> +IPTABLES_ARGS=""
> +
> +start() {
> +	printf 'Starting %s: ' "$DAEMON"
> +	iptables-restore < /etc/iptables.conf
> +	status=$?
> +	if [ "$status" -eq 0 ]; then
> +		echo "OK"
> +	else
> +		echo "FAIL"
> +	fi
> +	return "$status"
> +}
> +
> +stop() {
> +	printf 'Stopping %s: ' "$DAEMON"
> +	iptables -F
> +	status=$?
> +	if [ "$status" -eq 0 ]; then
> +		echo "OK"
> +	else
> +		echo "FAIL"
> +	fi
> +	return "$status"
> +}
> +
> +restart() {
> +	stop
> +	sleep 1
> +	start
> +}
> +
> +save() {
> +	printf 'Saving %s: ' "$DAEMON"
> +	if iptables-save > /etc/iptables.conf; then
> +		status=$?
> +		if [ "$status" -eq 0 ]; then

  This makes no sense - if you enter the if branch, then status is by definition 
0...

  Since it's not terribly important IMHO (I don't think the complexity of the 
S20urandom stuff is really warranted, since 'save' is just a manual operation), 
I fixed it up so it just prints OK in the if branch and SKIP in the else branch.

  Baruch, any objections?


  BTW, I have no problem with this in the default installation, because by 
default it doesn't do anything (iptables.conf is an empty file). Personally I'd 
have implemented it by testing if it exists in the init script, but that's 
really bikeshedding.

  Thus, applied to master, thanks.

  Regards,
  Arnout

> +			echo "OK"
> +		else
> +			echo "FAIL"
> +		fi
> +	else
> +		status=$?
> +		echo "SKIP (read-only file system detected)"
> +	fi
> +	return "$status"
> +}
> +
> +case "$1" in
> +	start|stop|restart|save)
> +		"$1";;
> +	reload)
> +		# Restart, since there is no true "reload" feature.
> +		restart;;
> +	*)
> +		echo "Usage: $0 {start|stop|restart|reload}"
> +		exit 1
> +esac
> diff --git a/package/iptables/iptables.mk b/package/iptables/iptables.mk
> index dc01466607..f0ddca8f9a 100644
> --- a/package/iptables/iptables.mk
> +++ b/package/iptables/iptables.mk
> @@ -57,4 +57,10 @@ define IPTABLES_LINUX_CONFIG_FIXUPS
>   	$(call KCONFIG_ENABLE_OPT,CONFIG_NETFILTER_XTABLES)
>   endef
>   
> +define IPTABLES_INSTALL_INIT_SYSV
> +	$(INSTALL) -m 0755 -D package/iptables/S35iptables \
> +		$(TARGET_DIR)/etc/init.d/S35iptables
> +	touch $(TARGET_DIR)/etc/iptables.conf
> +endef
> +
>   $(eval $(autotools-package))
> 
_______________________________________________
buildroot mailing list
buildroot@lists.buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-09-22 21:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-15 13:06 [Buildroot] [PATCH v3] package/iptables: add init script José Pekkarinen
2021-09-22 21:33 ` Arnout Vandecappelle [this message]
2021-10-05 13:41 ` Peter Korsgaard
2021-10-05 16:28   ` José Pekkarinen
2021-10-05 16:54     ` Peter Korsgaard
2021-10-06  6:23       ` José Pekkarinen

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=12c37043-7099-cba8-3394-48501f377502@mind.be \
    --to=arnout@mind.be \
    --cc=baruch@tkos.co.il \
    --cc=buildroot@buildroot.org \
    --cc=jose.pekkarinen@unikie.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.