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

    WANGroup(s) for NAT rules

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 2 Posters 864 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.
    • M
      Malakym
      last edited by

      When I first started seeing the default WANGroup being setup, you couldn't use it for NAT forwarding, just Rules.

      I have now noticed you can select this as an Interface under NAT forwarding. Though doing a quick test on this does not seem to work as I would hope.

      Am I looking at a configuration issue or this is not expected to work?

      It would be nice not to have to duplicate rules for every WAN.

      stephenw10S 1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator @Malakym
        last edited by

        You mean an interface group as opposed to a gateway group?

        Port forward (inbound) NAT rules?

        In pfSense 2.5.2?

        Steve

        M 1 Reply Last reply Reply Quote 0
        • M
          Malakym @stephenw10
          last edited by Malakym

          @stephenw10 said in WANGroup(s) for NAT rules:

          You mean an interface group as opposed to a gateway group?
          Port forward (inbound) NAT rules?
          In pfSense 2.5.2?

          Yes, yes and actually 2.4.4 though could test on the new boxes we're about to migrate to.

          Edit: Just checked on 2.5.2, not working either.

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            Ah, OK. Then, yes, definitely test in 2.5.2 first if you can. There are also a number of fixes in 2.6 that are probably worth testing here.

            Steve

            M 1 Reply Last reply Reply Quote 0
            • M
              Malakym @stephenw10
              last edited by

              @stephenw10

              Just beat me to my stealth edit, 2.5.2 also not working.

              Would probably just wait until 2.6 is offered before trying it.

              Am I wrong that its supposed to work in this way though?

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Unclear. If the gui allows it though I'd expect it to. Conversely it should throw an error if it doesn't work. Let me see if I can replicate it...

                M 1 Reply Last reply Reply Quote 0
                • M
                  Malakym @stephenw10
                  last edited by

                  @stephenw10

                  It does seem to work, something else was getting in the way.

                  I was doing my initial testing with ssh port 22, when that is set to WANGroup (instead of wan1,wan2,etc) it seems to want to go to the ssh server on the router.

                  Instead tested it with something else (that pfSense wouldn't have its own port listening) and that works okay.

                  This is on 2.5.x, it does not work on 2.4.x.

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