From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 32465@debbugs.gnu.org
Subject: [bug#32465] Add iptables service
Date: Tue, 18 Sep 2018 11:54:31 +0530 [thread overview]
Message-ID: <cu736u7cogw.fsf@systemreboot.net> (raw)
In-Reply-To: <87va734yxd.fsf@gnu.org>
>> - Is the example I added for the iptables.rules sufficient? I couldn't
>> find upstream documentation for the iptables.rules format. I suspect
>> it doesn't exist. Do you know of any upstream documentation that can
>> be referred to here?
>
> From a quick search it must be <https://netfilter.org/documentation/>,
> specifically <https://netfilter.org/documentation/HOWTO//packet-filtering-HOWTO.html>.
This is general documentation for netfilter, not specific documentation
about the iptables.rules format. For that, I don't think there is
upstream documentation.
https://unix.stackexchange.com/questions/400163/netfilter-iptables-restore-file-format-documentation/400203
>> + (stop #~(lambda _
>> + (invoke #$iptables-restore #$%iptables-accept-all-rules)
>> + (invoke #$ip6tables-restore #$%iptables-accept-all-rules))))))))
>
> There’s a peculiarity of ‘stop’ which is that it must return #f on
> success. So here, you just need to add a trailing #f after the second
> ‘invoke’ call. If you do that, I suppose the test that stops the
> firewall will pass.
There was one problem with stop-service being an unbound variable. I
fixed that by adding (use-modules (gnu services herd)). But, now the
test just freezes up. I wonder if it is waiting for some timeout. Here
is the snippet for the test I am currently using. Also, returning #f
from stop didn't make a difference.
(test-assert "inetd echo service is accessible after iptables firewall is stopped"
(begin
(marionette-eval
'(begin
(use-modules (gnu services herd))
(stop-service 'iptables))
marionette)
(wait-for-tcp-port inetd-echo-port marionette #:timeout 5)))
next prev parent reply other threads:[~2018-09-18 6:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 11:24 [bug#32465] Add iptables service Arun Isaac
2018-09-04 13:14 ` Ludovic Courtès
2018-09-04 13:52 ` Julien Lepiller
2018-09-05 9:40 ` Arun Isaac
2018-09-10 12:51 ` Ludovic Courtès
2018-09-05 9:42 ` Arun Isaac
2018-09-14 10:59 ` Arun Isaac
2018-09-17 21:05 ` Ludovic Courtès
2018-09-18 6:24 ` Arun Isaac [this message]
2018-09-18 14:39 ` Ludovic Courtès
2018-09-18 16:02 ` Arun Isaac
2018-09-19 20:41 ` Ludovic Courtès
2018-09-20 7:50 ` bug#32465: " Arun Isaac
2018-09-11 6:53 ` [bug#32465] " Björn Höfling
2018-09-11 8:43 ` Arun Isaac
2018-09-15 12:27 ` Rutger Helling
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu736u7cogw.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=32465@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).