Oracle Linux 10 – Common Problem 029 – 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

Opened ports work temporarily but close after system reboot.

Environment & Reproduction

firewall-cmd –list-ports differs between runtime and permanent configs.

Root Cause Analysis

Run firewall-cmd –runtime-to-permanent check and inspect active zone.

Quick Triage

Rules were added without –permanent or placed in wrong zone.

Step-by-Step Diagnosis

Re-add ports with –permanent and reload firewalld.

Solution – Primary Fix

After reboot, confirm firewall-cmd –list-all still shows expected rules.

Solution – Alternative Approaches

Standardize zone assignment and persistent rule automation.

Verification & Acceptance Criteria

Remove accidental rules using firewall-cmd –permanent –remove-port.

Rollback Plan

Manage rules via firewall system role or Ansible modules.

Prevention & Hardening

firewall-cmd –add-service=http –permanent; firewall-cmd –reload

Related Errors & Cross-Refs

Provide zone XML from /etc/firewalld and service exposure requirements.

Related tutorial: View the step-by-step tutorial for oracle-linux-10.

View all oracle-linux-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

NetworkManager connection zone bindings can override expectations.