Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

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

    Scheduled Pinned Locked Moved NAT
    2 Posts 1 Posters 352 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      planetinse
      last edited by planetinse

      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?

      P 1 Reply Last reply Reply Quote 0
      • P
        planetinse @planetinse
        last edited by planetinse

        @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.

        4afaf369-0836-4869-8489-a186b256120a-bild.png

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.