diff options
| author | Christian Breunig <christian@breunig.cc> | 2024-05-01 20:55:57 +0200 |
|---|---|---|
| committer | Christian Breunig <christian@breunig.cc> | 2024-05-01 20:55:57 +0200 |
| commit | e7bb65894f86372dc0f6e8fd39b1628e0a224c68 (patch) | |
| tree | 123cf624b461fb8891b6d8a659bd14d55b0e357b /interface-definitions | |
| parent | 5ebcbddb0842c570284cd17553395fcc2e2edad0 (diff) | |
| download | vyos-1x-e7bb65894f86372dc0f6e8fd39b1628e0a224c68.tar.gz vyos-1x-e7bb65894f86372dc0f6e8fd39b1628e0a224c68.zip | |
vrf: T6189: render FRR L3VNI configuration when creating VRF instance
When adding and removing VRF instances on the fly it was noticed that the vni
statement under the VRF instance in FRR vanishes. This was caused by a race
condition which was previously designed to fix another bug.
The wierd design of a Python helper below the VRF tree to only generate the
VNI configuration nodes is now gone and all is rendered in the proper place.
Diffstat (limited to 'interface-definitions')
| -rw-r--r-- | interface-definitions/vrf.xml.in | 15 |
1 files changed, 1 insertions, 14 deletions
diff --git a/interface-definitions/vrf.xml.in b/interface-definitions/vrf.xml.in index 94ed96e4b..a20be995a 100644 --- a/interface-definitions/vrf.xml.in +++ b/interface-definitions/vrf.xml.in @@ -120,20 +120,7 @@ <constraintErrorMessage>VRF routing table must be in range from 100 to 65535</constraintErrorMessage> </properties> </leafNode> - <leafNode name="vni" owner="${vyos_conf_scripts_dir}/vrf_vni.py $VAR(../@)"> - <properties> - <help>Virtual Network Identifier</help> - <!-- must be after BGP to keep correct order when removing L3VNIs in FRR --> - <priority>822</priority> - <valueHelp> - <format>u32:0-16777214</format> - <description>VXLAN virtual network identifier</description> - </valueHelp> - <constraint> - <validator name="numeric" argument="--range 0-16777214"/> - </constraint> - </properties> - </leafNode> + #include <include/vni.xml.i> </children> </tagNode> </children> |