Project

General

Profile

Actions
Copy link

Bug #16073

open

Nested aliases used with OpenVPN do not always load routes

Added by Chris W about 2 months ago. Updated 17 days ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
OpenVPN
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
24.11
Release Notes:
Default
Affected Version:
Affected Architecture:

Description

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.

The routes can unpredictably disappear from the server configuration so are not pushed to clients. When this happens, only the name of AliasParent appears. Example:

push "route 10.2.0.0 255.255.0.0" 
push "route 10.10.0.0 255.255.255.0" 
...

becomes this in the VPN server configuration file:
push "route AliasParent 0.0.0.0"

The client sees:

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

This is temporarily fixed by editing AliasParent and re-saving it without making any changes.

Possibly related: https://redmine.pfsense.org/issues/13624

Actions
Copy link

Also available in: Atom PDF