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

    Error with outbound creation rule

    Scheduled Pinned Locked Moved NAT
    9 Posts 4 Posters 1.1k 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.
    • R
      r3animation
      last edited by

      Basically a newb and am trying to create a rule for an OpenVpn connection.

      I can't create a new outbound NAT rule as this error comes up.

      Steps:

      • Add new outbound NAT rule
      • Select interface: OpenVPNblahblah
      • Protocol: Any
      • Select source: Network - 127.0.0.0/8 - (port blank)
      • Select destination: any - (ip blank) - (port blank)
      • Translation: Interace Address - NAT Port: 1024:65535
      • Description: (anything)
      • Save

      Error: "You must supply a valid port for the NAT port entry."

      I know I'm missing something probably stupid. Any suggestions?

      edit: I'm on 2.2.4

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

        What is it that you're really trying to do?

        1 Reply Last reply Reply Quote 0
        • R
          r3animation
          last edited by

          From the torguard guide, the last entry.

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

            Sorry, what Torguard guide are you referring to?

            Edit:

            https://torguard.net/knowledgebase.php?action=displayarticle&id=122

            From their guide, it seems that this outbound NAT rule somehow is auto-created.  They don't actually show you adding this rule, nor do they list any steps.  They tell you to switch to Manual and the rule is just there.  I didn't follow their guide close enough to see what they're doing, but it appears that the pfSense port field validation will prevent you from manually creating the rule.

            1 Reply Last reply Reply Quote 0
            • R
              r3animation
              last edited by

              I thought it was quite similiar to this old bug in 2.2.1.

              https://redmine.pfsense.org/issues/4300

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

                Yes, it does look like that bug.  If you can reproduce it, perhaps you should log it on redmine.

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

                  That doesn't look like 2.2.4.  It looks like 2.1.5.

                  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
                  • KOMK
                    KOM
                    last edited by

                    Those TorGuard screens were probably taken using 2.1.5.

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

                      If you want it to be 1024:65535, leave the box blank and that's what it will do. They should update those instructions to omit the ports.

                      That said, that should work. Similar issue to #4300 for a different field.

                      https://redmine.pfsense.org/issues/5156
                      Fixed.

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