← Problem Library
Network L5 NETWORK-1481 · 12 min

A pfSense policy route looks correct and return traffic still escapes because state entries were created before the gateway group priority changed

The rule is right, but active states keep steering replies by the old gateway preference until they are rebuilt.

NetworkFoundation OpsLevel 5Free12 min
Scenario

Return traffic still uses the old WAN path after a gateway group failover policy update.

What to check first
  • Identify the primary failure signal in the The Route Rule Changed and the Firewall Kept Trusting the Conversation It Had Already Memorized scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Inspect existing state entries before changing routes or NAT again.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.