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

    Port Alias

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 416 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
      Jhendo6
      last edited by

      Hello,

      I am having an issue using a port alias with particular rules and wanted to run it by the community to see if I am missing something in my understanding of port aliases.

      I have created an port alias with 1:24, 26:52, 54:586, 588:65535 for port ranges. When creating rules with TCP/UDP protocol, my goal is to use this alias to equate to "all ports except for 25, 53, and 587". So if I reject all packets against this alias, the source will still have access to 25, 53, and 587.

      Am I correct in this logic?

      Thanks.

      1 Reply Last reply Reply Quote 0
      • KOMK
        KOM
        last edited by

        Yes.

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

          Sweet! Thanks!

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Anther way that might make more sense when (possibly someone years from now) is reading the rule set would be to make four rules:

            pass TCP 25
            pass TCP 587
            pass TCP/UDP 53
            reject any

            You could combine 25 and 587 into a port alias but not sure it's worth it for just two ports. Anyway, that's what I would do.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

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