From 4d1fc6e91aef9a0e9e43b21b07368b7b081764f3 Mon Sep 17 00:00:00 2001 From: Christian Breunig Date: Sat, 30 Sep 2023 16:02:52 +0200 Subject: vrf: netns: T3829: T31: priority needs to be after netns A network namespace can have VRFs assigned, thus we need to get the priorities right. This lowers both priorities in general as a VRF or NETNS needs to be available very early as services can run on top of them. (cherry picked from commit 9dd5ff064a37b4e884f7bd9fb7630bf7829fa1ad) --- interface-definitions/netns.xml.in | 2 +- interface-definitions/vrf.xml.in | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/interface-definitions/netns.xml.in b/interface-definitions/netns.xml.in index 5d958968f..d5026bfae 100644 --- a/interface-definitions/netns.xml.in +++ b/interface-definitions/netns.xml.in @@ -3,7 +3,7 @@ Network namespace - 291 + 10 diff --git a/interface-definitions/vrf.xml.in b/interface-definitions/vrf.xml.in index 3783785ce..e5ec539d3 100644 --- a/interface-definitions/vrf.xml.in +++ b/interface-definitions/vrf.xml.in @@ -4,7 +4,7 @@ Virtual Routing and Forwarding - 299 + 11 -- cgit v1.2.3