The platform is up, but one dependency path is not.

Use this when firewall behavior looks corrected until the next restart or policy reload restores the bad state. These issues are easy to misread because the operating system still responds while one control path, runtime dependency, or trust assumption is already out of alignment.

The symptom usually appears downstream from the real change.

• Linux assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• firewalld assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• nftables assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.
• Networking assumptions are often changed indirectly by updates, policy, hardware changes, or cleanup work that looked harmless at the time.