Bug #16073
Updated by Chris W about 2 months ago
Given: - Alias @AliasParent@ contains various other aliases @AliasChild1@, @AliasChild2@, etc., however all children are either an IP address or subnet (iow, none of the children contain further aliases). - AliasParent is used in OpenVPN server's @IPv4 Local network(s)@ field. field The routes can unexpectedly and unpredictably disappear from not appear in the server configuration so are not pushed to clients. When this happens, only the name of AliasParent appears. Example: <pre> push "route 10.2.0.0 255.255.0.0" push "route 10.10.0.0 255.255.255.0" ... </pre> becomes this in the VPN server configuration file: <pre> push "route AliasParent 0.0.0.0" </pre> The client sees: <pre> Feb 28 17:09:34 lpf59mbj6 nm-openvpn[365694]: [...] Peer Connection Initiated with [AF_INET] ...:1194 Feb 28 17:09:36 lpf59mbj6 nm-openvpn[365694]: Options error: route parameter network/IP 'AliasParent' must be a valid address </pre> This is temporarily fixed by editing AliasParent and re-saving it without making any changes. Possibly related: https://redmine.pfsense.org/issues/13624