pfSense

Indeed, this would be really helpful.

I'd like to push things a bit since this would really help a lot.

Jim P wrote:

Some ideas:

• Local Networks

I'm using this one but keeping track with additions/deletions of network segments is a pain.

• ipv4_private (or perhaps rfc1918) - 192.168.0.0/16, 10.0.0.0/8, and 172.16.0.0/12
• ipv6_linklocal - fe80::/10
• ipv6_private - fc00::/7
• ipv6_multicast - ff00::/8

How about a set of aliases covering ports as well?

Having those available would save users from having to look them up, hardcode them, or make their own aliases for the same values on every system.

Any idea when somebody might have time to implement this?

as with anything else - when someone's willing to pay for it, or someone does it and submits a merge request.

Not sure we'd need much in the way of port aliases. We already have a ton of ports in the drop-down list on firewall and NAT rules.
I'd rather pull info from /etc/services into there before I'd want to pre-create port aliases.

And like Chris said, it will happen when funding appears or code appears. It's a nice to have feature but not critical.

IIrc you already can use the names of a port in /etc/services wherever a port is asked.
So instead of typing 80 you can type http and so on.

I made the changes quite some time ago to support this, unless it has been broken moving on with changes it should work.

That issue along with some others from other feedback has been fixed for the next build.