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

    Can no longer set destination port for rule

    Scheduled Pinned Locked Moved Firewalling
    4 Posts 3 Posters 3.4k 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.
    • T
      thallam08
      last edited by

      Just upgraded to 2.3.2_1 for fix "invalid format" bug.  Unfortunately this patch does not fix all instances of the bug and introduces a new one.  I can no longer set the destination port for a rule after upgrading.  Could set it before.  Using another browser does not fix this one.

      Any ideas for a workaround other than manually editing the backed up XML config?

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        Which protocol? Port is only available for TCP and UDP.

        1 Reply Last reply Reply Quote 0
        • T
          thallam08
          last edited by

          Tried, TCP and UDP.

          Not interested in trying to specify ports on protocols that do not have ports. ;-)

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

            Destination port for what kind of rule? Where? What's the exact circumstance?

            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.