Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Loopback Interface Overview

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 mpls require a loopback address to function correctly.

  • Junos OS creates a separate loopback interface for the internal routing instance, which prevents any filter on lo0.0 from disrupting internal traffic.