Loopback Interfaces
Learn about loopback interfaces and how to configure loopback interfaces with examples.
The Internet Protocol (IP) defines a loopback network with the (IPv4) address
127.0.0.0/8. Most IP implementations support a loopback interface
(lo0) to represent the loopback facility. Traffic sent on the
loopback network is addressed to the same computer. Common loopback addresses are
127.0.0.1 for IPv4 and ::1 for IPv6. The standard
domain name for the address is localhost.
A network device has an internal loopback interface (lo0.16384) with a
logical unit number 16384. The loopback interface identifies the device. While any
interface address can check if the device is online, the loopback address is preferred
because it remains unchanged despite network topology changes.
Pinging an interface address does not always reflect device health. Subnet mismatches or unrelated issues can make interfaces appear offline. The loopback interface avoids these problems and provides reliable results.
Junos OS Evolved supports two different filters to control the flow of local packets: one for network control traffic (loopback traffic) and one for management traffic. For additional information, see Top Differences Between Junos OS Evolved and Junos OS.
Benefits
-
As the loopback address never changes, network administrators use the loopback address as the best way to identify a device in the network.
-
The loopback interface remains up and reachable if the IP address route exists in the routing table. You can use it for diagnostics and troubleshooting.
-
Protocols like OSPF use the loopback address to determine protocol-specific properties for devices or networks. Commands like
ping mplsrequire a loopback address to function correctly. -
Junos OS creates a separate loopback interface for the internal routing instance, which prevents any filter on
lo0.0from disrupting internal traffic.
Loopback Interface Configuration
You (a system administrator, network administrator, or end user) can use this procedure to configure the loopback interface on your device.
- Configure the Loopback Interface
- Example: Configure Two Addresses on the Loopback Interface with Host Routes
Configure the Loopback Interface
When specifying the loopback address on a device, do not include a destination prefix. Also, in most cases, specify a loopback address only on unit 0 and no others.
For Layer 3 virtual private networks (VPNs), you can configure multiple logical units for the loopback interface. This allows you to configure a logical loopback interface for each virtual routing and forwarding (VRF) routing instance.
For some applications, such as SSL for Junos XML protocol, at least one address
for the interface lo0.0 must be 127.0.0.1.
You can configure loopback interfaces using a host (recommended), a subnetwork
address for both inet and inet6 address families,
or an ISO network entity title (NET) address for the iso address
family. Many protocols require a loopback address as their source address.
Configuring a loopback address as a donor interface for unnumbered interfaces
enables these protocols to run on unnumbered interfaces.
In some cases, the loopback interface can also be the router identifier (router ID). If the router ID is not explicitly configured, the device determines its router ID as shown in the following table:
| If the loopback interface is: | Then the default router ID is: |
|---|---|
| Configured | The loopback interface |
| Not configured | The lowest IP address of any interface in operational state
up |
In both cases, the router ID changes when the operational state of the interface changes. Therefore, we recommend configuring the address on a stable loopback interface.
If you configure more than one address on the loopback interface, we recommend that you configure one to be the primary address. The device selects the primary address as the router ID when the router ID is not configured. The device also uses the primary address as the default source address for traffic sourced from the loopback interface by the Routing Engine.
To configure the physical loopback interface (lo0), include the
following statements at the [edit interfaces] hierarchy level:
[edit interfaces]
lo0 {
unit 0 {
family inet {
address loopback-address;
address <loopback-address2>;
...
}
family inet6 {
address loopback-address;
}
}
}
You can configure one or more addresses on the loopback interface. You can configure
more than just unit 0 for lo0, but you must place
each additional unit in a separate routing instance.
Example: Configure Two Addresses on the Loopback Interface with Host Routes
In the following example, the user configures two addresses on the loopback interface with host routes:
[edit]
user@host# edit interfaces lo0 unit 0 family inet
[edit interfaces lo0 unit 0 family inet]
user@host# set address 10.0.0.1
[edit interfaces lo0 unit 0 family inet]
user@host# set address 172.16.0.1
[edit interfaces lo0 unit 0 family inet]
user@host# top
[edit]
user@host# show interfaces
lo0 {
unit 0 {
family inet {
10.0.0.1/32;
172.16.0.1/32;
}
}
}