summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNico Felbinger <26925347+felbinger@users.noreply.github.com>2026-06-23 12:26:54 +0200
committerGitHub <noreply@github.com>2026-06-23 11:26:54 +0100
commitc1fd4992e4c8bb16c388f255fc2a612dc5dc4251 (patch)
treed60ab2f52066e1c0b5f3556c69532645e27d27c7 /docs
parent55ed500de0baba3beeea8779f2aed4866abfe8f5 (diff)
downloadvyos-documentation-c1fd4992e4c8bb16c388f255fc2a612dc5dc4251.tar.gz
vyos-documentation-c1fd4992e4c8bb16c388f255fc2a612dc5dc4251.zip
configexamples/inter-vrf-routing-vrf-lite: fix formatting (#2112)
* configexamples/inter-vrf-routing-vrf-lite: fix formatting * configexamples/inter-vrf-routing-vrf-lite: reformat text to limit line length
Diffstat (limited to 'docs')
-rw-r--r--docs/configexamples/inter-vrf-routing-vrf-lite.md16
1 files changed, 9 insertions, 7 deletions
diff --git a/docs/configexamples/inter-vrf-routing-vrf-lite.md b/docs/configexamples/inter-vrf-routing-vrf-lite.md
index 2ac36904..cd726c34 100644
--- a/docs/configexamples/inter-vrf-routing-vrf-lite.md
+++ b/docs/configexamples/inter-vrf-routing-vrf-lite.md
@@ -53,15 +53,17 @@ need for MPLS.
MP-BGP or MultiProtocol BGP introduces two main concepts to solve this
limitation:
-\- Route Distinguisher (RD): Is used to distinguish between different VRFs
+
+- Route Distinguisher (RD): Is used to distinguish between different VRFs
–called VPNs- inside the BGP Process. The RD is appended to each IPv4 Network
that is advertised into BGP for that VPN making it a unique VPNv4 route.
-\- Route Target (RT): This is an extended BGP community append to the VPNv4 route
-in the Import/Export process. When a route passes from the VRF routing table
-into the BGP process it will add the configured export extended community(ies)
-for that VPN. When that route needs to go from BGP into the VRF routing table
-will only pass if that given VPN import policy matches any of the appended
-community(ies) into that prefix.
+
+- Route Target (RT): This is an extended BGP community append to the VPNv4
+route in the Import/Export process. When a route passes from the VRF routing
+table into the BGP process it will add the configured export extended
+community(ies) for that VPN. When that route needs to go from BGP into the VRF
+routing table will only pass if that given VPN import policy matches any of the
+appended community(ies) into that prefix.
## Topology