From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 32465@debbugs.gnu.org, Rutger Helling <rhelling@mykolab.com>
Subject: [bug#32465] Add iptables service
Date: Tue, 11 Sep 2018 08:53:29 +0200 [thread overview]
Message-ID: <20180911085329.2c625c63@alma-ubu> (raw)
In-Reply-To: <cu7tvnt6xss.fsf@systemreboot.net>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Fri, 17 Aug 2018 16:54:19 +0530
Arun Isaac <arunisaac@systemreboot.net> wrote:
> After we have iterated a few times, and converged on the final patch
> for this service, I will also contribute a similar service for
> ip6tables.
Hi Arun,
thanks for the patch. I have one little comment:
During holidays I read an article about nftables:
https://netfilter.org/projects/nftables/
https://wiki.archlinux.org/index.php/nftables
It aims to be the successor for iptables and is ipv4, ipv6 and others
in one tool/ruleset.
I have no knowledge about the firewall tools, I have no idea of how
mature or accepted that is, I just thought it might be worth
considering instead of writing 3 services.
We already have the userspace package 'nftables' and 'libnftnl' thanks
to Rutger Helling. Maybe he knows more? I put him on CC.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2018-09-11 6:54 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
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 ` Björn Höfling [this message]
2018-09-11 8:43 ` [bug#32465] " 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180911085329.2c625c63@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=32465@debbugs.gnu.org \
--cc=arunisaac@systemreboot.net \
--cc=rhelling@mykolab.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.