No, I do not need nft if I only intend to use iptables. This is just additional complexity. They think I need it sure, since they want to immediately start the transition to nft.
But I can just see this breaking things for people who like me built their own kernel for specific needs, such as servers where a lot of people will do just for performance or security reasons and will not include any nft support. Actually, if they insist on transitioning to nft then at least they should warn during upgrade that the 'legacy' (as it's for some reason called) iptables has moved path. Cheers, chillfan ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Saturday, February 16, 2019 6:35 PM, Alessandro Selli <alessandrose...@linux.com> wrote: > On 16/02/19 at 11:26, chillfan--- via Dng wrote: > > > And of course I don't need nft > > Yes, you do. > > For some reason you don't want it, but that's a different matter. > > > ---------------------------------------------------------------------------------------- > > Alessandro Selli alessandrose...@linux.com > VOIP SIP: dhatarat...@ekiga.net > Chiave firma e cifratura PGP/GPG signing and encoding key: > BA651E4050DDFC31E17384BABCE7BD1A1B0DF2AE
publickey - chillfan@protonmail.com - 0xB179B25B.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
