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

    RC 2.1 (i386) - Port alias not working

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    8 Posts 2 Posters 1.9k 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.
    • S
      software
      last edited by

      Hello,

      I noticed in the 2.1 release that Port Alias is not working as expected.
      I made some screenshots to make it a bit more clear.

      There are (for testing) 2 ports defined in the port Alias group (called EXT_port_TCP_global). My wireless subnet may access those ports, so I placed a accept rule for this alias.
      But the firewall status tells me the port is blocked.

      When I create a accept rule without port alias, but with port 5228 (example port) it works as expected.

      You will see in the screenshots multiple port aliasses, none of them are working.

      Is this a bug or my wrong thinking ?
      pfsense.jpg
      pfsense.jpg_thumb
      pfsense2.jpg
      pfsense2.jpg_thumb

      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        Your protocol there is UDP. You get TCP blocked.

        1 Reply Last reply Reply Quote 0
        • S
          software
          last edited by

          @doktornotor:

          Your protocol there is UDP. You get TCP blocked.

          Sorry, I was not clear. I'm talking about the rule before the last one.
          The one with EXT_port_TCP_global.

          1 Reply Last reply Reply Quote 0
          • S
            software
            last edited by

            Ok, back to basics.
            I removed all my INT_subnet_* rules and made a new screenshot.

            Still no luck.

            How can you explain, If I put a accept rule with only port 5228, it works ?

            pfsense3.jpg
            pfsense3.jpg_thumb

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              Great. What is "blackstain"WIRELESS in the firewall log?

              1 Reply Last reply Reply Quote 0
              • S
                software
                last edited by

                Ok, new firewall log with the rules from reply #3
                10.80.4.0/24 is my vlan4wireless network

                pfsense4.jpg
                pfsense4.jpg_thumb

                1 Reply Last reply Reply Quote 0
                • S
                  software
                  last edited by

                  Damn, it was my mistake.
                  I took vlan4wireless address instead of vlan4wireless net as source.

                  I changed it to to "vlan4wireless net" as source and it works now.

                  1 Reply Last reply Reply Quote 0
                  • D
                    doktornotor Banned
                    last edited by

                    Well, good that it works. Other than that, it helps to name the aliases so that they make things more obvious, rather than obscuring them. :D

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