From 93f7ae7f1ed1e218ef64d2582d11ac0ed769a438 Mon Sep 17 00:00:00 2001
From: Christian Poessinger <christian@poessinger.com>
Date: Wed, 4 Mar 2020 19:53:58 +0100
Subject: vrf: T31: rename 'vrf disable-bind-to-all ipv4' to 'vrf bind-to-all'

By default the scope of the port bindings for unbound sockets is limited to the
default VRF. That is, it will not be matched by packets arriving on interfaces
enslaved to an l3mdev and processes may bind to the same port if they bind to
an l3mdev.

TCP & UDP services running in the default VRF context (ie., not bound to any
VRF device) can work across all VRF domains by enabling the 'vrf bind-to-all'
option.
---
 interface-definitions/vrf.xml.in | 15 ++++-----------
 1 file changed, 4 insertions(+), 11 deletions(-)

(limited to 'interface-definitions/vrf.xml.in')

diff --git a/interface-definitions/vrf.xml.in b/interface-definitions/vrf.xml.in
index a6c67e9dd..f1895598e 100644
--- a/interface-definitions/vrf.xml.in
+++ b/interface-definitions/vrf.xml.in
@@ -7,19 +7,12 @@
       <priority>210</priority>
     </properties>
     <children>
-      <node name="disable-bind-to-all">
+      <leafNode name="bind-to-all">
         <properties>
-          <help>Disable services running on the default VRF from other VRF (ssh, bgp, ...)</help>
+          <help>Enable binding services to all VRFs</help>
+          <valueless/>
         </properties>
-        <children>
-          <leafNode name="ipv4">
-            <properties>
-              <valueless/>
-              <help>Enable binding across all VRF domains for IPv4</help>
-            </properties>
-          </leafNode>
-        </children>
-      </node>
+      </leafNode>
       <tagNode name="name">
         <properties>
           <help>VRF instance name</help>
-- 
cgit v1.2.3