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

    Cannot specify destination port. Is this a bug?

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 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.
    • D Offline
      dkinley
      last edited by

      Hi,

      I'm just starting with pfSense.

      I configured my interfaces and started defining Firewall Rules.
      I defined a floating rule applied to LAN interfaces inbound; Source: any, Destination: <dns ip="" addr="">and port: 53 (DNS)
      That worked.

      Then I decided to define some Firewall aliases for hosts (lists of AD servers to be precise).
      Then I defined a floating rule applied to LAN interfaces inbound; Source: any, Destination <alias>and 389 (LDAP).
      but after Save and turning to the list of rules Destination Port is still: * and any new rule cannot have its destination port set.

      I've reset to factory default and am using IP addresses (no aliases) and have the same result.

      Has anyone seen this before?

      Darren</alias></dns>

      1 Reply Last reply Reply Quote 0
      • P Offline
        phil.davis
        last edited by

        I just tried making some floating rules with alias as a destination and specifying a port. The combinations I tried worked fine. I tested on a 2.3.4 system.

        If you can reproduce it easily, then post screen shots of the settings you are entering. That will help us understand the exact data entered on the webGUI.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • D Offline
          dkinley
          last edited by

          Hi,

          Thanks for responding.

          I just don't get it. I reinstalled, reconfigured all of my interfaces and tried to create another rule with the same result.

          Please see attached config.png and result.png.

          Darren

          config.PNG
          config.PNG_thumb
          result.PNG
          result.PNG_thumb

          1 Reply Last reply Reply Quote 0
          • jimpJ Offline
            jimp Rebel Alliance Developer Netgate
            last edited by

            Destination port "From" should also be set to DNS – that defines a range, and for a single port you set "from" and "to" to the same value.

            Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

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