CentOS Stream 9 – Common Problem 109 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Legacy iptables rules silently no-op or fail to load at boot.

Environment & Reproduction

iptables on Stream 9 is the nft translation layer (iptables-nft).

Root Cause Analysis

Counters and table layout differ; raw nft rules and iptables-legacy can collide.

Quick Triage

rpm -q iptables-nft iptables-legacy shows installed variants.

Step-by-Step Diagnosis

iptables -V prints ‘(nf_tables)’ to confirm the backend.

Solution – Primary Fix

Convert rules with iptables-translate or rewrite in nft syntax.

Solution – Alternative Approaches

Use iptables-legacy package only for short-term compatibility.

Verification & Acceptance Criteria

nft list ruleset shows the converted rules and traffic counters increment.

Rollback Plan

Restore previous ruleset from /etc/sysconfig/iptables backup.

Prevention & Hardening

Manage firewall via firewalld or a single nft script under /etc/nftables/.

Related Errors & Cross-Refs

Related: firewalld backend selection and connection-tracking helpers.

Related tutorial: View the step-by-step tutorial for centos-stream-9.

View all centos-stream-9 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

nftables wiki and Red Hat networking docs.