Skip to content

Install iptables-nft explicitly#521

Open
jovial wants to merge 5 commits intostackhpc/2025.1from
bugfix/2025.1/nftables
Open

Install iptables-nft explicitly#521
jovial wants to merge 5 commits intostackhpc/2025.1from
bugfix/2025.1/nftables

Conversation

@jovial
Copy link

@jovial jovial commented Mar 16, 2026

We installed this package in previous releases, so to prevent a mixture of legacy and nftables firewall rules, we should explitly install the iptables-nft package.

Closes-Bug: #2144562
Change-Id: I2bba43407a10edb283d8605d579667cb8d8e3126

@jovial jovial requested a review from a team as a code owner March 16, 2026 14:05
We installed this package in previous releases, so to prevent a mixture
of legacy and nftables firewall rules, we should explitly install the
iptables-nft package.

Closes-Bug: #2144562
Change-Id: I2bba43407a10edb283d8605d579667cb8d8e3126
Signed-off-by: Will Szumski <will@stackhpc.com>
@jovial jovial force-pushed the bugfix/2025.1/nftables branch from 71f2bd8 to e3f80e4 Compare March 16, 2026 14:19
jovial added 4 commits March 18, 2026 17:56
There was a regression in 2025.1 where we switched back to using
iptables-legacy. Explicitly installing iptables-nft restores the
old behaviour.

Closes-Bug: #2144562
Change-Id: I2bba43407a10edb283d8605d579667cb8d8e3126
Signed-off-by: Will Szumski <will@stackhpc.com>
There was a regression in 2025.1 where we switched back to using
iptables-legacy. Explicitly installing iptables-nft restores the
old behaviour.

Closes-Bug: #2144562
Change-Id: I2bba43407a10edb283d8605d579667cb8d8e3126
Signed-off-by: Will Szumski <will@stackhpc.com>
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.

1 participant