Project

General

Profile

Bug #3778

Destination port range not displayed when it's an associated NAT rule and "other" ports

Added by Patrik Lundquist about 6 years ago. Updated almost 6 years ago.

Status:
Resolved
Priority:
Low
Assignee:
-
Category:
Web Interface
Target version:
-
Start date:
07/26/2014
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.1.x
Affected Architecture:

Description

firewall_rules_edit.php doesn't display Destination Port Range when it's an associated NAT rule and From and To are "other" (edit_disabled).

I created a NAT Port Forward for a range of FTP data ports and while the port range 65500-65535 is displayed on the editable firewall_nat_edit.php page it's not displayed on the ghosted/locked firewall_rules_edit.php.

The Destination Address is displayed just fine.

Associated revisions

Revision 0e2eaa1b (diff)
Added by Renato Botelho almost 6 years ago

Do not reset source and destination port range values when it's an associated rule created by nat port forward. It fixes #3778

Revision e35ec763 (diff)
Added by Renato Botelho almost 6 years ago

Do not reset source and destination port range values when it's an associated rule created by nat port forward. It fixes #3778

History

#1 Updated by Renato Botelho almost 6 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100

#3 Updated by Patrik Lundquist almost 6 years ago

I copied the updated firewall_rules_edit.js to /usr/local/www/javascript/firewall_rules_edit/ on the fw, restarted webConfigurator via SSH, and logged in on the pfSense web again.

I still don't see the ports. Do I have to do something else? I'd rather not reboot the firewall.

#4 Updated by Renato Botelho almost 6 years ago

Patrik Lundquist wrote:

I copied the updated firewall_rules_edit.js to /usr/local/www/javascript/firewall_rules_edit/ on the fw, restarted webConfigurator via SSH, and logged in on the pfSense web again.

I still don't see the ports. Do I have to do something else? I'd rather not reboot the firewall.

Maybe you need to clean your browser's cache just to be sure the new .js file is used.

#5 Updated by Patrik Lundquist almost 6 years ago

Found the problem. I renamed the old file to firewall_rules_edit.js.bak but didn't realize that both script files would then be included by firewall_rules_edit.php.

<script type="text/javascript" src="/javascript/firewall_rules_edit/firewall_rules_edit.js"></script>
<script type="text/javascript" src="/javascript/firewall_rules_edit/firewall_rules_edit.js.bak"></script>

It works after I removed the backup file.

#6 Updated by Renato Botelho almost 6 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF