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

    2.3.2 Outbound NAT - Possible Bug?

    Scheduled Pinned Locked Moved NAT
    3 Posts 2 Posters 673 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
      TheIlleist
      last edited by

      Hi,

      Can someone sanity check the attached image for me. I get the error as shown when trying to save this outbound NAT rule (and as a result, can't save it), but I believe it is a valid rule?

      EDIT: More explicitly, I hit this error when cloning from and existing rule an editing it, or when editing an existing rule (that works). Don't seem to encounter it when I create a new rule from scratch.

      pfsense_nat.png
      pfsense_nat.png_thumb

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

        Bug in your Chrome browser. Upgrade to 2.3.2_1 as it includes a workaround for it. Or use another browser in the meantime.

        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
        • T
          TheIlleist
          last edited by

          Thanks, will try another browser.

          EDIT: Same issue in Opera and Chrome, but worked in Firefox, thanks.

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