summaryrefslogtreecommitdiff
path: root/docs/configuration/vrf
diff options
context:
space:
mode:
authorYuriy Andamasov <yuriy@vyos.io>2026-04-21 20:35:22 +0300
committerYuriy Andamasov <yuriy@vyos.io>2026-04-21 20:35:22 +0300
commitd0a0fd4998b35af5b4e59374a5706ffeb27c7ee5 (patch)
treebebe87c3f28f8f7bb8aaa2fbdd091749f629f95b /docs/configuration/vrf
parent5d4cdc95200e8ef8fa9ef0f52c5607b76e980692 (diff)
downloadvyos-documentation-d0a0fd4998b35af5b4e59374a5706ffeb27c7ee5.tar.gz
vyos-documentation-d0a0fd4998b35af5b4e59374a5706ffeb27c7ee5.zip
fix: resolve all line-length lint warnings across 14 RST files
Wrap prose lines exceeding 80 chars and apply stop/start_vyoslinter markers around cfgcmd/opcmd directive lines that cannot be shortened (e.g. long option names with placeholder arguments). Affected files: bonding, wireguard, pim, conntrack-sync, dmvpn, ipsec_general, site2site_ipsec, vrf/index, bare-metal, inter-vrf-routing-vrf-lite, lac-lns, tunnelbroker, OpenVPN_with_LDAP, dmvpn-dualhub-dualcloud. 🤖 Generated by [robots](https://vyos.io)
Diffstat (limited to 'docs/configuration/vrf')
-rw-r--r--docs/configuration/vrf/index.rst21
1 files changed, 11 insertions, 10 deletions
diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst
index d8b81bac..5965f857 100644
--- a/docs/configuration/vrf/index.rst
+++ b/docs/configuration/vrf/index.rst
@@ -20,8 +20,8 @@ then enslaved to a VRF device.
.. cfgcmd:: set vrf name <name> table <id>
- Create a new VRF instance with `<name>` and `<id>`. The name is used when placing
- individual interfaces into the VRF.
+ Create a new VRF instance with `<name>` and `<id>`. The name is
+ used when placing individual interfaces into the VRF.
.. note:: A routing table ID can not be modified once it is assigned. It can
only be changed by deleting and re-adding the VRF instance.
@@ -66,9 +66,10 @@ can be used to filter which routes zebra will install in the kernel.
Nexthop Tracking
----------------
-Nexthop tracking resolve nexthops via the default route by default. This is enabled
-by default for a traditional profile of FRR which we use. It and can be disabled if
-you do not want to e.g. allow BGP to peer across the default route.
+Nexthop tracking resolve nexthops via the default route by default.
+This is enabled by default for a traditional profile of FRR which we
+use. It and can be disabled if you do not want to e.g. allow BGP to
+peer across the default route.
.. cfgcmd:: set vrf name <name> ip nht no-resolve-via-default
@@ -230,8 +231,8 @@ For VRF maintenance the following operational commands are in place.
the round-trip time of these packets is used in calculating the minimum/
average/maximum round-trip time numbers.
- .. note:: Ping command can be interrupted at any given time using ``<Ctrl>+c``.
- A brief statistic is shown afterwards.
+ .. note:: Ping command can be interrupted at any given time using
+ ``<Ctrl>+c``. A brief statistic is shown afterwards.
.. code-block:: none
@@ -535,9 +536,9 @@ address-family.
.. cfgcmd:: set vrf name <name> protocols bgp interface <interface> mpls
forwarding
- It is possible to permit BGP install VPN prefixes without transport labels.
- This configuration will install VPN prefixes originated from an e-bgp session,
- and with the next-hop directly connected.
+ It is possible to permit BGP install VPN prefixes without transport
+ labels. This configuration will install VPN prefixes originated
+ from an e-bgp session, and with the next-hop directly connected.
.. _l3vpn-vrf example operation: