https://redmine.pfsense.org/https://redmine.pfsense.org/favicon.ico?16780521162014-08-11T12:30:12ZpfSense bugtrackerpfSense - Bug #3778: Destination port range not displayed when it's an associated NAT rule and "other" portshttps://redmine.pfsense.org/issues/3778?journal_id=144402014-08-11T12:30:12ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Feedback</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="Do not reset source and destination port range values when it's an associated rule created by nat..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/0e2eaa1bfd43b097597b71a1d6e91751fddbe714">0e2eaa1bfd43b097597b71a1d6e91751fddbe714</a>.</p> pfSense - Bug #3778: Destination port range not displayed when it's an associated NAT rule and "other" portshttps://redmine.pfsense.org/issues/3778?journal_id=144432014-08-11T14:20:11ZRenato Botelhorenato@netgate.com
<ul></ul><p>Applied in changeset <a class="changeset" title="Do not reset source and destination port range values when it's an associated rule created by nat..." href="https://redmine.pfsense.org/projects/pfsense/repository/2/revisions/e35ec763337b9c3430391bdc400daf6c7b7df84b">e35ec763337b9c3430391bdc400daf6c7b7df84b</a>.</p> pfSense - Bug #3778: Destination port range not displayed when it's an associated NAT rule and "other" portshttps://redmine.pfsense.org/issues/3778?journal_id=144502014-08-12T15:45:16ZPatrik Lundquistpatrik.lundquist@gmail.com
<ul></ul><p>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.</p>
<p>I still don't see the ports. Do I have to do something else? I'd rather not reboot the firewall.</p> pfSense - Bug #3778: Destination port range not displayed when it's an associated NAT rule and "other" portshttps://redmine.pfsense.org/issues/3778?journal_id=146362014-08-27T13:24:41ZRenato Botelhorenato@netgate.com
<ul></ul><p>Patrik Lundquist wrote:</p>
<blockquote>
<p>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.</p>
<p>I still don't see the ports. Do I have to do something else? I'd rather not reboot the firewall.</p>
</blockquote>
<p>Maybe you need to clean your browser's cache just to be sure the new .js file is used.</p> pfSense - Bug #3778: Destination port range not displayed when it's an associated NAT rule and "other" portshttps://redmine.pfsense.org/issues/3778?journal_id=146532014-08-28T16:45:26ZPatrik Lundquistpatrik.lundquist@gmail.com
<ul></ul><p>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.<br /><code><br /> <script type="text/javascript" src="/javascript/firewall_rules_edit/firewall_rules_edit.js"></script><br /> <script type="text/javascript" src="/javascript/firewall_rules_edit/firewall_rules_edit.js.bak"></script><br /></code></p>
<p>It works after I removed the backup file.</p> pfSense - Bug #3778: Destination port range not displayed when it's an associated NAT rule and "other" portshttps://redmine.pfsense.org/issues/3778?journal_id=146542014-08-28T16:59:43ZRenato Botelhorenato@netgate.com
<ul><li><strong>Status</strong> changed from <i>Feedback</i> to <i>Resolved</i></li></ul>