diff options
| author | Christian Breunig <christian@breunig.cc> | 2024-03-20 20:53:47 +0100 |
|---|---|---|
| committer | Mergify <37929162+mergify[bot]@users.noreply.github.com> | 2024-03-21 09:23:10 +0000 |
| commit | c104f9aea60416dbff3bf8de994921069ee6a928 (patch) | |
| tree | 451d395fa95b2584c1df017238d1999c9c1a6607 /interface-definitions/include/name-server-ipv4.xml.i | |
| parent | f7a005ebecdfabc0a0af75ed9ad84b44ef1d6d5b (diff) | |
| download | vyos-1x-c104f9aea60416dbff3bf8de994921069ee6a928.tar.gz vyos-1x-c104f9aea60416dbff3bf8de994921069ee6a928.zip | |
vti: T6085: interface is always down and only enabled by IPSec daemon
When a VTI interface is just created, it is in ADMIN UP state by default, even
if an IPSec peer is not connected. After the peer is disconnected the interface
goes to DOWN state as expected.
This breaks routing logic - for example, static routes through VTI interfaces
will be active even if a peer is not connected.
This changes to logic so ADMIN UP/DOWN state can only be changed by the
vti-up-down helper script.
Error was introduced during the Perl -> Python migration and move to the generic
vyos.ifconfig abstraction during the 1.4 development cycle.
(cherry picked from commit 9eb018c4935235d292d7c693ac15da5761be064a)
Diffstat (limited to 'interface-definitions/include/name-server-ipv4.xml.i')
0 files changed, 0 insertions, 0 deletions