If you don't mind the pesky breaking fundamental rules of IP thing, it saves
burning 4 Ip addresses (255.255.255.252 = 4 addresses) for a loopback
interface. Since the Loopback is often set to give a router a "Name" for
OSPF or BGP, it works okay.
Ejay Hire
804-220-7724
877-200-7020,x7724
... An
It provides an interface that is always up. Good thing as if you were
pointing to a spwecific addres, ie ethernet, and it went down, there would
be a failure. On a loopback the routing process can determine the best path
to it - more redundancy
Andrew Larkins
-Original Message-
From: Jac
It is also good for
Setting up a BGP peering session when you have multiple links between the
two routers .
Monitoring a router using an NMS, lets say you want to monitor a router
that has 20 interfaces on it. If you list one of those interfaces as the
primary connection in the NMS config then i
""Jacques Lee"" <[EMAIL PROTECTED]> wrote in message
8ge6qu$6vk$[EMAIL PROTECTED]">news:8ge6qu$6vk$[EMAIL PROTECTED]...
> What is a loopback interface for, besides the Router ID in OSPF ?
You might well use the loopback interface IP address for the configuration
of DLSw peers. This is quite commo
4 matches
Mail list logo
