Loopback Interfaces; Loopbacks Configuration; Figure 225: Loopback Configuration-Create - D-Link DWS-4026 User Manual

Software User Manual
12/10/09
L I
OOPBACK NTERFACES
D-Link software provides for the creation, deletion, and management of loopback interfaces. They are dynamic interfaces
that are created and deleted via user-configuration. D-Link software supports multiple loopback interfaces.
A loopback interface is always expected to be up. As such, it provides a means to configure a stable IP address on the device
that may be referred to by other switches. This interface provides the source address for sent packets and can receive both
local and remote packets. It is typically used by routing protocols.
A loopback interface is a pseudo-device for assigning local addresses so that the router can be communicated with by this
address, which is always up and can receive traffic from any of the existing active interfaces. Thus, given reachability from
a remote client, the address of the loopback can be used to communicate with the router through various services such as
telnet and SSH. In this way, the address on a loopback behaves identically to any of the local addresses of the router in
terms of the processing of incoming packets.
The LAN > L3 Features > Loopbacks folder and LAN > Monitoring > L3 Status folder contain links to the following web
pages that configure and display loopback parameters and data:
•

"Loopbacks Configuration"

• "Loopback Summary"
L C
OOPBACKS ONFIGURATION
Use the Loopbacks Configuration page to create, configure, or remove loopback interfaces. You can also set up or delete a
secondary address for a loopback.
To display the page, click LAN > L3 Features > Loopbacks > Configuration in the navigation tree. If no loopback interfaces
exist on the system, the page only has two fields, as
Additional fields display depending on whether or not a loopback has already been created, as shown in
Document 34CSFP6XXUWS-SWUM100-D7
Figure 225
Figure 225: Loopback Configuration—Create
D-Link Unified Access System
shows.
Figure 226.

Loopback Interfaces

Page 321