From bafc84f32635dd00850a334b7802e6afa28e2b0c Mon Sep 17 00:00:00 2001
From: Christian Poessinger <christian@poessinger.com>
Date: Sun, 25 Apr 2021 20:51:49 +0200
Subject: policy: T3490: lower priority to keep up with Policy-Based-Routing
 (PBR)

PBR is implemented in vyatta-cfg-firewall and the new policy framework uses one
script to rule them all that is triggered from the main policy level.

As the PBR configuration is a subnode with a lower priority we get an inversion,
thus all policy based configuration which applies to FRR only, is set to
priority 200.

Automated tests did not show any regression.
---
 interface-definitions/policy.xml.in | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

(limited to 'interface-definitions')

diff --git a/interface-definitions/policy.xml.in b/interface-definitions/policy.xml.in
index cd22052f0..08e2ce2c6 100644
--- a/interface-definitions/policy.xml.in
+++ b/interface-definitions/policy.xml.in
@@ -2,14 +2,13 @@
 <interfaceDefinition>
   <node name="policy" owner="${vyos_conf_scripts_dir}/policy.py">
     <properties>
-      <priority>470</priority>
+      <priority>200</priority>
       <help>Routing policy</help>
     </properties>
     <children>
       <tagNode name="access-list">
         <properties>
           <help>IP access-list filter</help>
-
           <valueHelp>
             <format>u32:1-99</format>
             <description>IP standard access list</description>
@@ -238,7 +237,6 @@
       <tagNode name="extcommunity-list">
         <properties>
           <help>Border Gateway Protocol (BGP) extended community-list filter</help>
-          <priority>490</priority>
           <valueHelp>
             <format>txt</format>
             <description>Border Gateway Protocol (BGP) extended community-list filter</description>
-- 
cgit v1.2.3