summaryrefslogtreecommitdiff
path: root/docs/configuration/interfaces/loopback.rst
diff options
context:
space:
mode:
authorLiudmylaNad <l.nadolina@vyos.io>2026-01-27 10:52:27 +0100
committerGitHub <noreply@github.com>2026-01-27 09:52:27 +0000
commit22c81723b32ea39f7466edfe7f546821b396333c (patch)
tree999fa078220fc13f2cb79a9bca38cb3ac805536e /docs/configuration/interfaces/loopback.rst
parentb1fc782abce7abc73d17ae0ceeeffa61dd238727 (diff)
downloadvyos-documentation-22c81723b32ea39f7466edfe7f546821b396333c.tar.gz
vyos-documentation-22c81723b32ea39f7466edfe7f546821b396333c.zip
DOC: Proofreading virtual, loopback, and dummy interfaces (#1745)
Diffstat (limited to 'docs/configuration/interfaces/loopback.rst')
-rw-r--r--docs/configuration/interfaces/loopback.rst26
1 files changed, 13 insertions, 13 deletions
diff --git a/docs/configuration/interfaces/loopback.rst b/docs/configuration/interfaces/loopback.rst
index b5fbdf83..77b6e475 100644
--- a/docs/configuration/interfaces/loopback.rst
+++ b/docs/configuration/interfaces/loopback.rst
@@ -1,4 +1,4 @@
-:lastproofread: 2023-01-20
+:lastproofread: 2026-01-23
.. _loopback-interface:
@@ -6,20 +6,20 @@
Loopback
########
-The loopback networking interface is a virtual network device implemented
-entirely in software. All traffic sent to it "loops back" and just targets
-services on your local machine.
+The loopback interface is a virtual, software-based network interface. All
+traffic sent to it loops back and only targets services on the local host.
-.. note:: There can only be one loopback ``lo`` interface on the system. If
- you need multiple interfaces, please use the :ref:`dummy-interface`
+.. note:: Only one loopback ``lo`` interface is allowed per operating system.
+ If you require multiple virtual interfaces, use the :ref:`dummy-interface`
interface type.
-.. hint:: A loopback interface is always up, thus it could be used for
- management traffic or as source/destination for and :abbr:`IGP (Interior
- Gateway Protocol)` like :ref:`routing-bgp` so your internal BGP link is not
- dependent on physical link states and multiple routes can be chosen to the
- destination. A :ref:`dummy-interface` Interface should always be preferred
- over a :ref:`loopback-interface` interface.
+.. hint:: The loopback interface is always operational, making it suitable for
+ management traffic or as a stable source/destination for routing protocols such
+ as BGP. This ensures internal routing sessions remain independent of physical
+ link states.
+
+ However, in most cases, the dummy interface is preferred over the loopback
+ interface.
*************
Configuration
@@ -55,7 +55,7 @@ Operation
.. opcmd:: show interfaces loopback lo
- Show detailed information on the given loopback interface `lo`.
+ Show detailed interface information.
.. code-block:: none