Firewall rules only work correctly after an update

[Praelia7or]

Had this issue twice now, first time it was kind of a relief after wrestling with trying to get it to work and seeing nothing wrong in the settings at all. 2nd time it's a bit more of an annoyance of do I really have to wait for an update to play the games I want correctly?!

I have 2 internet connections, one low ping gaming optimised wired and one starlink for bandwidth, downloads streaming etc. I have these set up as 2 group gateways - one with failover from wired, one failover from starlink. I'm using the ports that games use as a firewall rule to select the failover from wired group, with failover from starlink as the default rule.

The first game added worked fine after an update - weird but ok, great, I can play without turning off starlink all the time now. The second I copied all of the rules, groups, aliases etc and correct names/ports to the 2nd game and... nothing. Uses the default starlink connection, disable starlink, it works fine on the wired connection. Tried rebooting, flushing states tables. Still nothing, so I thought it's worth a try maybe there is an update available - there was, and it now works as intended.

So what gets reset during an update that doesn't while rebooting and flushing firewall states table that I need to do to poke it into action?

[lrosenman]

I had a similar weirdness.  I have 2 rules in my WAN interface to allow SSH and BACULA in, and one or the other would be active but not both.

I wound up deleting and recreating them both, and it SEEMS to be working now.