diff options
| author | Christian Poessinger <christian@poessinger.com> | 2020-10-18 18:04:34 +0200 |
|---|---|---|
| committer | Christian Poessinger <christian@poessinger.com> | 2020-10-18 18:15:30 +0200 |
| commit | 029f9839c21317ec5959b331eee25da472d08dc1 (patch) | |
| tree | 4d4d9b8d3d142f783e0cc84015303a9e2920cfc7 /op-mode-definitions/show-raid.xml | |
| parent | b3e486604c46c4aec858706ac90c833f3b4ebe5c (diff) | |
| download | vyos-1x-029f9839c21317ec5959b331eee25da472d08dc1.tar.gz vyos-1x-029f9839c21317ec5959b331eee25da472d08dc1.zip | |
openvpn: T2969: force creation of tunnel interfaces
A lot of VyOS code requires the Kernel interface to be present in order to
properly work and adjust the interface to the users CLI intends (alias, ipv6,
vrf - just to name a few).
OpenVPN - when run in client mode - only creates the interface (e.g. vtun1) when
the connection to the OpenVPN server was successful. This can't be always the
case due to e.g. software-updates or routing issues to the remote side. This
will in the end result in a zombie OpenVPN client interface where some config
items might not have been set when the interface finally comes up - imagine a
wrong assigned VRF instance.
By always creating the OpenVPN interface manuall we ensure that all the CLI
settings are properly configured in the OS kernel.
Diffstat (limited to 'op-mode-definitions/show-raid.xml')
0 files changed, 0 insertions, 0 deletions