Outbound NAT rules stopped working after 2.5.0 ? (multiple WAN interfaces)

planetinse · Aug 13, 2021, 9:03 AM

My outbound rules has stopped working (after upgrade from 2.5 to 2.5.2)

it seems its ignoring GW that is set for the the specific WAN interface (in Firewall/Rules) and always use default interface instead (from Routing/Gateways) - and if there is a mismatch traffic will get "stuck" or "lost" because its using the wrong GW

so tested to swap default GW in Routing/Gateways then the outbound rules for that GW works and the rules for the other GW stops working. so its clear its ignoring the routing rule under Firewall/Rules)

known issue?

planetinse · Aug 13, 2021, 9:08 AM

@planetinse

The problem is now I can only rely on one of the WAN's (the default in Routing/Gateways) for outgoing traffic with Outbound NAT rules.

I will have to revert back to 2.5.0 again.

I think the root cause is that the Gateway setting in advanced options for the FW Rules on LAN side is simply not used, it always using the default gateway regardless of what is selected in the rule.

🔒 Log in to view