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

    NAT/Port Forwarding - Unable to change redirect target port

    Scheduled Pinned Locked Moved NAT
    2 Posts 2 Posters 551 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
      townsenk64
      last edited by townsenk64

      Currently using 22.05 Devel Base 22.05.a.20220426.1313.
      While attempting to edit an existing NAT forwarding rule I'm able to change the target redirect port in the GUI and the settings can be saved and changes applied. However it reverts to an Asterisks in the GUI after saving. I assume that this would mean "Any". A crash report is also generated with the errors listed below. Can anyone else duplicate this? This also happens when creating new rules. I'm cautious about submitting a bug report until I can confirm this issue because I usually get my input dismissed by the Devs because I'm not always able to fully explain the problem.

      UPDATE: It appears that this problem has already been fixed in Regression #13126

      Thank You

      Crash report

      amd64
      12.3-STABLE
      FreeBSD 12.3-STABLE plus-devel-12-n202664-041fc0bc0fd pfSense

      Crash report details:

      PHP Errors:
      [06-May-2022 18:06:18 America/Chicago] PHP Warning: strstr() expects at least 2 parameters, 1 given in /usr/local/pfSense/include/www/firewall_nat.inc on line 520
      [06-May-2022 18:06:18 America/Chicago] PHP Warning: strstr() expects at least 2 parameters, 1 given in /usr/local/pfSense/include/www/firewall_nat.inc on line 521

      No FreeBSD crash data found.

      luckman212L 1 Reply Last reply Reply Quote 0
      • luckman212L
        luckman212 LAYER 8 @townsenk64
        last edited by

        @townsenk64 yep, known issue

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

        fix should be in the next snapshot or you can use system patches to apply the commit now

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