====== Loopback Addresses ======

A **loopback address** is a special IP address that always refers to the local device itself.

Packets sent to a loopback address never leave the computer. Instead, they are immediately returned by the operating system's network stack.

Loopback addresses are primarily used for:

  * Testing network software
  * Diagnosing TCP/IP configuration
  * Local services
  * Software development

-----

===== The IPv4 Loopback Range =====

The entire IPv4 block:

<code>
127.0.0.0/8
</code>

is reserved for loopback.

The most commonly used address is:

<code>
127.0.0.1
</code>

This address is often referred to as:

  * localhost
  * the local host
  * loopback interface

-----

===== IPv6 Loopback Address =====

IPv6 defines a single loopback address:

<code>
::1
</code>

This serves the same purpose as 127.0.0.1 in IPv4.

-----

===== How Loopback Works =====

Suppose an application sends data to:

<code>
127.0.0.1
</code>

The operating system immediately routes the packet back to itself.

The packet never reaches:

  * your router
  * your switch
  * the Internet

Example:

<code>
Application
      │
      ▼
127.0.0.1
      │
      ▼
Operating System
      │
      └──────────────┐
                     │
                     ▼
          Same Computer
</code>

-----

===== Localhost =====

The hostname:

<code>
localhost
</code>

normally resolves to:

IPv4

<code>
127.0.0.1
</code>

IPv6

<code>
::1
</code>

Most operating systems include this mapping by default.

-----

===== Common Uses =====

Loopback addresses are commonly used for:

  * Web server testing
  * Database servers
  * Local APIs
  * Development environments
  * Network diagnostics

Example:

<code>
http://127.0.0.1

or

http://localhost
</code>

Both normally access a web server running on the same computer.

-----

===== Testing TCP/IP =====

One of the simplest networking tests is:

<code>
ping 127.0.0.1
</code>

If this succeeds, the operating system's TCP/IP stack is functioning correctly.

Example output:

<code>
Reply from 127.0.0.1

bytes=32

time<1ms
</code>

If this test fails, the problem is usually within the local operating system rather than the physical network.

-----

===== Can Other Devices Reach My Loopback Address? =====

No.

Every device has its own loopback interface.

For example:

Computer A

<code>
127.0.0.1
</code>

and

Computer B

<code>
127.0.0.1
</code>

refer to different computers.

A loopback address is never reachable across the network.

-----

===== Loopback vs Private IP =====

^ Loopback ^ Private Address ^
| Refers to the local computer | Refers to a device on a local network |
| Never leaves the operating system | Can communicate with other devices on the LAN |
| 127.0.0.1 | 192.168.1.25 |

-----

===== Loopback in Telenegar =====

Telenegar IP Check automatically identifies loopback addresses.

Example:

<code>
Input:

127.0.0.1

Classification:

Loopback Address
</code>

This helps distinguish loopback addresses from public and private IP addresses.

-----

===== Common Misconceptions =====

  * **127.0.0.1 is a private IP address.**
    * False. It is a loopback address, not a private address.

  * **Other computers can connect to my 127.0.0.1.**
    * False. Every computer has its own loopback interface.

  * **Only 127.0.0.1 is reserved for loopback.**
    * False. The entire 127.0.0.0/8 block is reserved for loopback, although 127.0.0.1 is by far the most commonly used address.

-----

===== Related Topics =====

  * [[networking:internet:ip-addresses|IP Addresses]]
  * [[networking:internet:ipv4|IPv4]]
  * [[networking:internet:ipv6|IPv6]]
  * [[networking:internet:private-public|Private vs Public IP]]
  * [[tools:ipcheck|IP Check]]
  * [[tools:pingcheck|Ping Check]]

-----

{{tag>loopback localhost 127.0.0.1 ipv4 ipv6 networking}}