Print Page - OPNsense firewall rule that makes me angry

Title: OPNsense firewall rule that makes me angry
Post by: Calimarina on March 02, 2026, 12:57:43 AM

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.

Title: Re: OPNsense firewall rule that makes me angry
Post by: OPNenthu on March 02, 2026, 01:12:39 AM

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

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

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

Title: Re: OPNsense firewall rule that makes me angry
Post by: Calimarina on March 02, 2026, 01:27:03 AM

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

Title: Re: OPNsense firewall rule that makes me angry
Post by: OPNenthu on March 02, 2026, 01:56:47 AM

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.

Title: Re: OPNsense firewall rule that makes me angry
Post by: franco on March 02, 2026, 11:47:54 AM

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

OPNsense Forum

English Forums => General Discussion => Topic started by: Calimarina on March 02, 2026, 12:57:43 AM