Alias in openVPN's routing networks

Started by VN, January 13, 2026, 01:55:06 PM

Previous topic - Next topic
Hi,

I am using OPNsense as firewall and openVPN server.
In some server instance, I start to have quit a lot of prefixes in routing local and remote network.

It would be convenient to use alias so:
  • I would not repeat some prefixes, it prevents from errors
  • I could put a description in front of each prefixes, it will help in futur maintenance

Here (https://github.com/opnsense/core/issues/9105) I had the answer that will not come because of dynamic caracteristic of alias.

Did you get into this problem?
Did you found any solution?

Vincent

Hi VN, welcome!

That would be very much appreciated, and I fully understand the dynamic nature of aliases.

That said, I wouldn't mind if adding a new network to HQ_NETWORKS_ALIAS triggered a reload of the OpenVPN service that references this alias. This is not something I would do frequently, and when I do, I would already be clicking Apply on the OpenVPN configuration page, which reloads the service anyway.

This behavior would also be a significant facilitator for static routes, Wireguard, OpenVPN, and IPsec.

For now, doing the manual approach...
- nothing broken, nothing missing;