On 8/12/19 1:56 PM, Michael Biebl wrote:
> Is libnftables a proper public API, i.e. supposed to be used by 3rd
> party applications?
>
Yes, totally. The first user is the nft itself.
You have a python bindings package and the library itself can ingest both native
nft syntax and JSON.
If some
Am 12.08.19 um 13:50 schrieb Arturo Borrero Gonzalez:
> On 8/12/19 1:26 PM, Michael Biebl wrote:
>> src/shared/firewall-util.* uses libiptc (which in turn uses iptables)
>>
>> ttbomk, mixing nftables and iptables is supported, otherwise we'd have
>> huge problems in buster (e.g. firewalld was expli
On 8/12/19 1:26 PM, Michael Biebl wrote:
> src/shared/firewall-util.* uses libiptc (which in turn uses iptables)
>
> ttbomk, mixing nftables and iptables is supported, otherwise we'd have
> huge problems in buster (e.g. firewalld was explicitly switched back to
> use iptables as quite a few compon
Am 12.08.19 um 10:52 schrieb Trent W. Buck:
> Package: systemd
> Version: 241-5
> Severity: normal
> File: /lib/systemd/network/80-container-ve.network
>
> Debian 10 defaults to nftables:
>
>
> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#nftables
>
> ...b
Package: systemd
Version: 241-5
Severity: normal
File: /lib/systemd/network/80-container-ve.network
Debian 10 defaults to nftables:
https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#nftables
...but systemd doesn't for IPMasquerade=, see below.
AFAICT the def
5 matches
Mail list logo
