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

    [solved] Missing Group Port Fowarding rule on 2.3B1

    Scheduled Pinned Locked Moved 2.3-RC Snapshot Feedback and Issues - ARCHIVED
    5 Posts 3 Posters 967 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.
    • J
      Jabroni
      last edited by

      Im tyring to setup a group port forward as I did on previous version. This is what im doing

      • Go to Firewall - Aliases - Port groups
      • Added a definition of a port group alias
      • Went to the NAT -> Add new rule
      • On the Rule addition, there is no option to use this Alias (on pre2.2 I would be able to type the alias name on the from (other) Destination port foward ). It just lets me input port numbers

      Could someone confirm if there is another way to do this on 2.3 or if I should open a bug report ??

      1 Reply Last reply Reply Quote 0
      • S
        Steve_B Netgate
        last edited by

        That does appear to be a problem. Let me check v2.2.x and see how that worked.

        Als ik kan

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

          That worked at least semi-recently, but yeah it is missing port alias capability now.

          1 Reply Last reply Reply Quote 0
          • S
            Steve_B Netgate
            last edited by

            It seems that autocomplete doesn't work with element type "number"

            Just pushed a fix. Please gitsync or wait for the next snapshot

            Als ik kan

            1 Reply Last reply Reply Quote 0
            • J
              Jabroni
              last edited by

              @Steve_B:

              It seems that autocomplete doesn't work with element type "number"

              Just pushed a fix. Please gitsync or wait for the next snapshot

              That was quick :) I'll update when the next snapshot gets compiled and report back

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