This is the 4th time this has happened now. In the past it's resolved itself after like 8-24 hours automatically, but I'm not sure why (why it happens or why it resolves itself). It could be an OPNsense issue I suppose, since it's been happening consistently after I restart my router with their recent updates. But I don't see how, everything else on my network is fine. I've also been experiencing some other odd issues in Unraid that might be related:

• Duplicati docker container failed to stop (cli or gui) and my Docker tab wouldn't load at all. Couldn't stop the Docker service itself either, had to reboot.

• WebUI is crazy slow. Takes like 30 seconds for the terminal or log popups to populate.

• Last restart it was stuck on "Starting Recycle Bin" (presumably related to the plugin) and had to be hard reset.

At first I thought it was an issue with swag or the docker service, but when I try a ping command from the console itself it times out:

The fact that the issue usually "fixes" itself leads me to believe this isn't an issue with my settings (haven't touched em in years) or with OPNsense's settings (also haven't changed in years).

All of my externally accessible services are down, and even if it resolves itself again overnight (fingers crossed) I'd really appreciate help getting to the root cause of this.

(edit:) I'm on version 7.1.2

Edited October 9, 2025Oct 9 by GeekyGecko
more details

Figured it out. The problem was on OPNSense's end after all. After going through a bunch of things with ChatGPT it eventually suggested running the command pfctl -F all -f /tmp/rules.debug on the router - and that did the trick! Called it a "hard reset and manual reload of the packet filter (PF) ruleset". Apparently the issue caused by one of the following:
it meant PF had either:

1. A stale or corrupted in-memory ruleset,
   often caused by interface state desyncs after reboot, NIC driver reloads, or manual changes in Interface Assignments.

2. Rules applied before the LAN interface was ready,
   which can happen if PF starts before ix or ixl NICs are fully initialized — especially on systems using Intel X520/X710 cards or virtual NICs under Unraid/Proxmox.

3. Temporary rules override stuck active,
   e.g. “quick” rules from dynamic updates, floating rules, or auto-generated DNS rules that didn’t clear properly.

By flushing and reloading from /tmp/rules.debug, you forced PF to:

• Drop all previous state tables, NAT mappings, and stale interface bindings.

• Rebind the filter engine to the current ix0 (LAN) and ix1 (WAN) devices.

• Reapply your GUI-defined firewall rules correctly.

After this reload, packets were once again being matched against your “allow LAN to any” rule, not a broken placeholder or orphaned rule that denied local traffic.

-----

No idea if any of that is accurate, but it makes sense to me.

Edited October 9, 2025Oct 9 by GeekyGecko

Alright so things aren't completely fixed after all. I'm still running into weird issues all over the place.

This morning I noticed my linuxserver/unifi-network-application container was down because it couldn't see the MongoDB container. After a bunch of messing around I finally tried changing the MongoDB network type from "Bridge" to "bond0" and gave it its own IP address. That fixed that issue.... but I don't know why.

Later I realized my UniFi Network integration in HomeAssistant was down, and could not reach the unifi-network-application docker container either. I've screwed around with NAT > Outbound settings, my Port Forward Settings, my NAT reflection...... all I do is break more things.

Does anyone else here use OPNsense? I can't be the only one running into this.