OPNsense firewall rule that makes me angry

[Calimarina]

In Firewall:NAT:Destination NAT I'm creating this entry

Interface = HOME
Version = IPv4
Protocol = TCP
Source Address = Home net
Source Port = any
Destination Address = Ventaxia_Public_IP
Destination Port = HTTPS
Redirect Target IP = Ventaxia_Private_IP
Redirect Target Port = 443

Is there a reason why I can't use, "HTTPS" with, "Redirect Target Port"? It won't let me use that. It gives me the error, "Please specify a valid port number or alias". I know there's got to be some logical reasoning for it. It's just that I suffer from OCD and it makes my eye twitch every time I look at it.

[OPNenthu]

I think this was fixed in 26.1.1.  Check for updates?

https://forum.opnsense.org/index.php?topic=50704.0

o firewall: local-port field in destination NAT does not support range and well-known name

[Calimarina]

Strange, because I'm using v26.1.2. Thank you for the quick reply though, I appreciate it.

[OPNenthu]

I'm on 26.1.2_5 and the Redirect Target Port definitely has HTTPS among others, but DNS is missing.  I hadn't noticed that.  Maybe there are still some gaps.

[franco]

It's being discussed right now. There are some ups and downs to "well known" ports in the new GUI at the moment.

https://github.com/opnsense/core/pull/9880


Cheers,
Franco