[prev in list] [next in list] [prev in thread] [next in thread] 

List:       netfilter
Subject:    Re: [ANNOUNCE] iptables 1.8.0 release
From:       Jan Engelhardt <jengelh () inai ! de>
Date:       2018-07-10 8:30:54
Message-ID: nycvar.YFH.7.76.1807101025450.24058 () n3 ! vanv ! qr
[Download RAW message or body]


On Friday 2018-07-06 11:32, Florian Westphal wrote:
>iptables 1.8
>
>This release introduces a more prominent distinction between the
>'classic' iptables and 'new' iptables front-end that internally uses the
>nf_tables API to talk to the kernel.
>
>legacy commandline tools:
>ip6tables-legacy-save ip6tables-legacy-restore ip6tables-legacy
>iptables-legacy-save iptables-legacy-restore iptables-legacy
>
>nf_tables commandline tools:
>ip6tables-nft-save ip6tables-nft-restore ip6tables-nft
>iptables-nft-save iptables-nft-restore iptables-nft

With the distro hat on, I found that the "arptables" and "ebtables"
programs in iptables.git could perhaps be named arptables-nft and
ebtables-nft too, to enjoy the choose-your-engine symlinking that
iptables-legacy-* vs iptables-nft-* received.

For iptables.git, it is just cosmetic, since in distro packaging,
renames can always be done unilaterally anyway. (It follows,
for example, that exactly such a change would also need to
be made to ebtables.spec to even enable that.)
What do you think?
--
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]