Debian 13 nftables Rules Not Loaded at Boot

📖 ~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

Firewall appears active during runtime but disappears after reboot.

Environment & Reproduction

Seen when rules were loaded manually but not persisted.

Root Cause Analysis

`nftables.service` is disabled or config path is invalid.

Quick Triage

Check service enablement and configured rules file.

Step-by-Step Diagnosis

Review boot-time service logs for parse errors.

Solution – Primary Fix

Store valid rules in `/etc/nftables.conf` and enable service.

Solution – Alternative Approaches

Use configuration management to enforce firewall state at boot.

Verification & Acceptance Criteria

After reboot, expected nftables chains and policies are present.

Rollback Plan

Restore previous firewall config if new rules block critical access.

Prevention & Hardening

Validate ruleset syntax in CI before deployment.

Related Errors & Cross-Refs

Related to iptables-nft backend conflicts and policy mismatch issues.

Related tutorial: View the step-by-step tutorial for Debian 13.

View all Debian 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian nftables persistence and service management docs.