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

    2.3 issues with changing default gateway routing

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 801 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.
    • F
      FlashEngineer
      last edited by

      I'm not sure what's going on but on one of my VLAN, the last firewall rule is a pass all rule to access internet via OpenVPN client gateway.  Now if modify this rule and change the gateway back to default, nothing works.  I can't get access to internet.  My 7 other VLANS have no issues if I modify the rule like this.

      What's going on here?  I never had an issue modifying the gateway on a rule before in 2.2.6

      Here's my rules set.

      rrrrrr.png_thumb
      rrrrrr.png

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        No change between versions there. Guessing maybe you have manual outbound NAT configured and it doesn't cover that VLAN's subnet out WAN.

        1 Reply Last reply Reply Quote 0
        • F
          FlashEngineer
          last edited by

          @cmb:

          No change between versions there. Guessing maybe you have manual outbound NAT configured and it doesn't cover that VLAN's subnet out WAN.

          Yeah it's manual outbound NAT, but it's configured for the vlan's subnet for openvpn out and of course the default rules which allow it to go without VPN.

          The problem is when switching it to non vpn gateway.  I don't understand, maybe I'll delete the last rule and remake it again?

          1 Reply Last reply Reply Quote 0
          • F
            FlashEngineer
            last edited by

            @cmb:

            No change between versions there. Guessing maybe you have manual outbound NAT configured and it doesn't cover that VLAN's subnet out WAN.

            Hmm you are correct, 1 rule has been missing from outbound NAT, must have been due to new GUI and I probably hit the wrong icon to copy+add new.

            I have another issue I'm investigating, I will update once I figure out if it's a true bug or not.

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