Skip to content

feat(firewall): use direct nftables when supported#3157

Draft
qdm12 wants to merge 4 commits intomasterfrom
nftables
Draft

feat(firewall): use direct nftables when supported#3157
qdm12 wants to merge 4 commits intomasterfrom
nftables

Conversation

@qdm12
Copy link
Owner

@qdm12 qdm12 commented Feb 25, 2026

Description

  • If the nftables backend is supported, use it with raw calls to it in Go (no iptables-nft etc). Otherwise, fallback on using iptables.
  • Still use iptables for custom post rules (to be removed in v4)

Prerequirements

  • Separate iptables specific code an implementation of the firewall
  • Make iptables code more "atomic" so it resembles nftables' built-in atomicity

Issue

Assertions

  • I am aware that we do not accept manual changes to the servers.json file
  • I am aware that any changes to settings should be reflected in the wiki

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: enabling firewall fails, Couldn't load match `conntrack' Feature request: use google/nftables to handle nftables firewall

1 participant