Project

General

Profile

Actions
Copy link

Bug #3778

closed
PL

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

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

Added by Patrik Lundquist about 12 years ago. Updated about 12 years ago.

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

100%

Estimated time:
Plus Target Version:
Release Notes:
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.

RB Updated by Renato Botelho about 12 years ago Actions
Copy link
 #1

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

Applied in changeset commit:0e2eaa1bfd43b097597b71a1d6e91751fddbe714.

RB Updated by Renato Botelho about 12 years ago Actions
Copy link
 #2

Applied in changeset commit:e35ec763337b9c3430391bdc400daf6c7b7df84b.

PL Updated by Patrik Lundquist about 12 years ago Actions
Copy link
 #3

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.

RB Updated by Renato Botelho about 12 years ago Actions
Copy link
 #4

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.

PL Updated by Patrik Lundquist about 12 years ago Actions
Copy link
 #5

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.

RB Updated by Renato Botelho about 12 years ago Actions
Copy link
 #6

  • Status changed from Feedback to Resolved
Actions
Copy link

Also available in: Atom