Feature #7704
closed
Destination port range "Any" in Port Forward UI doesn't work
100%
Description
If you set "Any" as the Destination port range for a Port Forward TCP or UDP entry, upon saving the new rule you get the following errors:
The following input errors were detected: - The field Destination port from is required. - The field Destination port to is required.
If you also do not set the Redirect target port for the same entry, which arguably is expected for a "Any" rule, you get the additional error:
- The field Redirect target IP is required.
This has the very easy workaround of manually setting the port range from 1 to 65535, and the redirect port to 1.
(I'm marking this as a Feature as the "Any" label was probably intended for other protocol choices, but definitely makes sense for TCP and UDP too.)
Updated by Jim Pingle over 5 years ago
- Category changed from Interfaces to Rules / NAT
Updated by Viktor Gurov over 4 years ago
This PR sets the port range from 1 to 65535, the redirect port to 1 and hide 'Redirect target port' input if "Any" is selected:
https://github.com/pfsense/pfsense/pull/4283
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Viktor Gurov over 4 years ago
- Status changed from Feedback to Resolved
works as expected on 2.5.0.a.20200423.1513
"10.11.11.1 -> 88.88.99.99 tcp any" example:
/tmp/rules.debug:
rdr on vtnet1 proto tcp from any to 10.11.11.1 -> 88.88.99.99
rdr on { vtnet0 vtnet2 vtnet3 } proto tcp from any to 10.11.11.1 -> 88.88.99.99
pass in quick on $WAN1 inet proto tcp from any to 88.88.99.99 tracker 1587725295 flags S/SA keep state label "USER_RULE: NAT "
Updated by Jim Pingle over 4 years ago
- Status changed from Resolved to Feedback
- Target version changed from 2.5.0 to 2.4.5-p1
Updated by Jim Pingle over 4 years ago
- Status changed from Feedback to Resolved
Rule is now formed correctly and functions as expected.