Bug #4238
closed
Firewall rule: source port display issue
100%
Description
Hello,
it is a display issue and appears when i try to select saved aliases on source port range.
The red background is partially displayed on suggested aliases making difficult to choose.
This not happens when i select aliases on destination port field.
I have attached a screenshot to better understanding the issue.
Thanks for support
Files
Updated by Chris Buechler about 10 years ago
- Category changed from Rules / NAT to Web Interface
- Target version changed from 2.2 to 2.2.1
Updated by Bipin Chandra about 10 years ago
https://github.com/pfsense/pfsense/pull/1452
patch to fix this
Updated by Anonymous about 10 years ago
the fetch fails
i suppose that a / is missing on the patch
usr/local/www/firewall_rules_edit.php
Regards
Updated by Bipin Chandra about 10 years ago
Updated by Bipin Chandra about 10 years ago
the above link is the patch file but u can simply edit the page (/usr/local/www/firewall_rules_edit.php) by going to diahnostics->edit file and opening that file thens earching for style="display:none" and removing it
Updated by Anonymous about 10 years ago
Thanks,
after removing style="display:none" id="sprtable" the cosmetic issue is not present anymore.
Updated by Anonymous about 10 years ago
ben kenobi wrote:
Thanks,
after removing style="display:none" the cosmetic issue is not present anymore.
Updated by Bipin Chandra about 10 years ago
after its merged, this can be closed
Updated by Anonymous about 10 years ago
i noted also that the issue is present also for nat rules (port forwarding)
Updated by Bipin Chandra about 10 years ago
i checked and doesnt seem any issue in port forwarding ports, try clearing your browser cache and check again and if it still persists then send in a screenshot
Updated by Anonymous about 10 years ago
Bipin Chandra wrote:
i checked and doesnt seem any issue in port forwarding ports, try clearing your browser cache and check again and if it still persists then send in a screenshot
You are right. It was the browser cache
Updated by Renato Botelho about 10 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset 6672609b90a8e60a13ca471a3ad3e054eca542bd.
Updated by Renato Botelho about 10 years ago
Applied in changeset 4520b2d2b70caa48813f73f89ef5b9c942ea5b25.
Updated by Giuanin Piemunteis about 10 years ago
Chris Buechler wrote:
fixed
with the latest version i noted the issue is back and also is present in the destionation port field
Updated by Bipin Chandra about 10 years ago
seems fine for me, clear ur browser cache and retry