Franco Fichtner
Franco Fichtner
> State tables shows correct matching What does "correct" mean here? Step 0 is obviously adding a new rule or else the apply would not be needed and the states...
I think the basic issue is the diagnostics tool will offer states per rulenum, which shifts as soon as the rules reload with a different ruleset. I'm unsure how to...
@KiNgMaR the patch is included and the cron job can fix the issue as it happens. However, we've been unable to find a good fix in the core for dpinger...
@KiNgMaR Good, can you look up the states for the stuck gateway monitor and try to clear them to see if that helps it to recover on its own?
@LucidityCrash best fit seems #7027 indeed. Looks like route-to sends to the old gateway which makes this fail permanently until the state is flushed. Thanks a lot for this piece...
@LucidityCrash is rule 104 one of your rules? Or at least a route where you added the gateway (route-to) yourself? Does it point to a gateway group or a single...
@LucidityCrash can you try this patch? 73e837d7d3 # opnsense-patch 73e837d7d3
"Firewall -> Settings -> Advanced -> Disable Forced Gateway" makes sense as the origin. So disabling this (all strings attached) would be a workaround. Take your time. I believe this...
In multi-WAN you want this behaviour in general so it's harder to switch the rules off although it only pertains to outgoing connections (and maybe outbound NAT). It really depends...
Hmm, I think 24.7.5 should patch just fine :)