nftables is being used successfully with no difficulty.
Running iptables on my node receives a crash:
$ sudo iptables -nL free(): double free detected in tcache 2 Aborted (core dumped)
without sudo
# iptables -nL free(): double free detected in tcache 2 Aborted (core dumped)
This bug is known and was fixed in version 1.8.8 of iptables https://git.netfilter.org/iptables/commit/?id=4318961230bce82958df82b57f1796143bf2f421
1) The release of Ubuntu
$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04
2) The version of the package
$ apt info iptables Package: iptables Version: 1.8.7-1ubuntu5.1
3) What you expected to happen
not to crash with valid, working nftables rules
4) What happened instead
crash
A plausible workaround could be a backport of iptables 1.8.9 from mantic
ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: iptables 1.8.7-1ubuntu5.1 ProcVersionSignature: Ubuntu 5.15.0-91.101-generic 5.15.131 Uname: Linux 5.15.0-91-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Sun Jan 14 20:36:59 2024 InstallationDate: Installed on 2021-11-23 (782 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iptables UpgradeStatus: Upgraded to jammy on 2023-04-30 (259 days ago)
nftables is being used successfully with no difficulty.
Running iptables on my node receives a crash:
$ sudo iptables -nL
free(): double free detected in tcache 2
Aborted (core dumped)
without sudo
# iptables -nL
free(): double free detected in tcache 2
Aborted (core dumped)
This bug is known and was fixed in version 1.8.8 of iptables https:/ /git.netfilter. org/iptables/ commit/ ?id=4318961230b ce82958df82b57f 1796143bf2f421
1) The release of Ubuntu
$ lsb_release -rd
Description: Ubuntu 22.04.3 LTS
Release: 22.04
2) The version of the package
$ apt info iptables
Package: iptables
Version: 1.8.7-1ubuntu5.1
3) What you expected to happen
not to crash with valid, working nftables rules
4) What happened instead
crash
A plausible workaround could be a backport of iptables 1.8.9 from mantic
ProblemType: Bug ature: Ubuntu 5.15.0- 91.101- generic 5.15.131 esult: pass 256color
DistroRelease: Ubuntu 22.04
Package: iptables 1.8.7-1ubuntu5.1
ProcVersionSign
Uname: Linux 5.15.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckR
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
Date: Sun Jan 14 20:36:59 2024
InstallationDate: Installed on 2021-11-23 (782 days ago)
InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: iptables
UpgradeStatus: Upgraded to jammy on 2023-04-30 (259 days ago)