Visibility of aliases

Started by keeka, Today at 11:07:59 AM

Previous topic - Next topic
Today at 11:07:59 AM Last Edit: Today at 11:10:50 AM by keeka
I think it would streamline configuration for the user if aliases were expanded and exposed in more sections of the OPNsense web interface.
Host interface aliases, for example, would make make it possible to configure DHCP and VPN without hardcoding a firewall IP address. Maybe I am overlooking something, but I have found myself looking for interface aliases and either not finding them in the dropdown or no aliases are offered/supported.

Aliases are a special way in pf(4) packet firewall format pf.conf(5) to hold immensely large lists of content. Mapping them to third party components like DHCP or similar would reduce their utility or lead to users complaining of interoperability challenges in the same subsystem, because the separation is not clear and never will be.

There's also no way to clamp down on specific network aliases.. could be hosts, networks, etc. Most services expect one or the other adding more wrenches to the system leading to slightly modified copies and further UX problems for "someone" to solve.


Cheers,
Franco