Re: [systemd-devel] [HEADSUP] nspawn/networkd: moving from iptables to nftables

2015-10-26 Thread Felipe Sateler
On Fri, 29 May 2015 17:49:12 +0200, Lennart Poettering wrote: > Yes, we are aware this is unfortunate, and that many people are still > using iptables. For this reason we would like to make the switch quickly > to ensure not too many users start using the iptables hook-up before it > goes away.

Re: [systemd-devel] [HEADSUP] nspawn/networkd: moving from iptables to nftables

2015-06-01 Thread Ian Pilcher
Is this going to make nspawn/networkd fundamentally incompatible with distributions that use iptables-based tools (such as firewalld)? -- Ian Pilcher arequip...@gmail.com I

[systemd-devel] [HEADSUP] nspawn/networkd: moving from iptables to nftables

2015-05-29 Thread Lennart Poettering
Heya, just a small heads-up: Currently there are two firewall APIs used on Linux: iptables and nftables. iptables is the older one, nftables the new replacement. systemd-nspawn and systemd-networkd currently interface with iptables via the libiptc library: nspawn to implement the --port= switch