When creating a firewall where a destination port is specified it appears that upon saving the port is ignored and the default value of any is used instead.
My steps are
Add a new rule
Specify TCP or UDP (haven't tried other protocols)
Set a destination to port (either from the existing entries in the drop down or specify a custom port)
Provide a description
Save
Generated rule is a wildcard rules with the destination set to any.
To rule out my browser, I've tested Safari, Chrome and Firefox. Same results on all three browsers.
I've reproduced the issue on a stock 19.1.4 install and a fully up to date 19.1.8 install.
A screen recording from a fresh vm showing the issue (http://sevan.sdf.org/opnsense.mov)
Image for those who don't want to play a movie:
(http://sevan.sdf.org/opnsense1.png)
(http://sevan.sdf.org/opnsense2.png)
(http://sevan.sdf.org/opnsense3.png)
If you specify a port range from ANY to SPECIFIC, the range is still ANY.
You should specify range from: SPECIFIC to SPECIFIC.
See attached screenshot.
Wow, totally skipped the destination is section is for specifying ranges.
I'd assumed it was for specifying a port & using notation to imply ranges (and ignored the left hand field).
Thanks for highlighting my mistake, much appreciated :)