From: Jason Cash (cash2001@xxxxxxxxxx)
Date: Tue Jul 16 2002 - 00:54:07 GMT-3
Thanks to everyone! I search the archive prior to asking but was unable
to locate the answer.
-----Original Message-----
From: Jim Brown [mailto:Jim.Brown@caselogic.com]
Sent: Monday, July 15, 2002 10:20 PM
To: 'Jason Cash'; ccielab@groupstudy.com
Subject: RE: OSPF route propagation with Loopback interfaces
Under the loopback interface add the line ip ospf network point-to-point
-----Original Message-----
From: Jason Cash [mailto:cash2001@swbell.net]
Sent: Monday, July 15, 2002 9:01 PM
To: ccielab@groupstudy.com
Subject: OSPF route propagation with Loopback interfaces
I am doing a lab that calls for multiple Eth. Interfaces; however, I
only have 2501's. So I substituted the Eth. Interface(s) with a
Loopback0 interface and assigned it the following:
R2
interface Loopback0
ip address 152.1.1.129 255.255.255.192
My question is that the route shows up as a / 26 on the connected
router, but show up as a /32 route on the neighboring router:
r2#sh ip ro 152.1.1.129
Routing entry for 152.1.1.128/26
Known via "connected", distance 0, metric 0 (connected, via interface)
Routing Descriptor Blocks:
* directly connected, via Loopback0
Route metric is 0, traffic share count is 1
R3 (neighbor)
r3#sh ip ro 152.1.1.129
Routing entry for 152.1.1.129/32
Known via "ospf 1", distance 110, metric 11, type intra area
Last update from 152.1.1.1 on Ethernet0, 00:24:25 ago
Routing Descriptor Blocks:
* 152.1.1.1, from 192.1.1.2, 00:24:25 ago, via Ethernet0
Route metric is 11, traffic share count is 1
Is this normal activity for loopback interfaces or can I rectify the
situation? I will have to do this for several labs and was looking for
a workaround.
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:31 GMT-3