Router blew a gasket

From: John Underhill (stepnwlf@magma.ca)
Date: Sun Jan 04 2004 - 15:36:40 GMT-3


I was looking through the routing tables and noticed a route I didn't
advertise. This is really strange, because it says loop0 is connected on this
box in the route table, and is advertising it into OSPF, but the loop0 address
that is configured is not the same, (not even close), and I never advertised
this network in OSPF. Router has been rebooted and erased since the last
config, but it looks like it's keeping it in memory.. pretty weird..

     172.16.0.0/16 is variably subnetted, 9 subnets, 5 masks
C 172.16.134.0/24 is directly connected, Serial0.2
O IA 172.16.44.0/29 [110/65] via 172.16.134.4, 00:03:52, Serial0.2
O IA 172.16.22.0/27 [110/65] via 172.16.123.2, 00:03:52, Serial0.1
C 172.16.1.0/24 is directly connected, Serial1
C 172.16.123.0/24 is directly connected, Serial0.1
C 172.16.104.0/21 is directly connected, Loopback0 <-- This one --
R1#
!
interface Loopback0
 ip address 172.16.111.1 255.255.248.0
 no ip directed-broadcast
 no ip route-cache
 ip ospf network point-to-point

router ospf 110
 area 111 virtual-link 172.16.134.4
 network 172.16.111.0 0.0.0.7 area 11
 network 172.16.123.0 0.0.0.255 area 0
 network 172.16.134.0 0.0.0.255 area 111

Routing table on another box shows the route..

C 172.16.122.0/27 is directly connected, Loopback0
C 172.16.22.0/24 is directly connected, Dialer0
C 172.16.22.1/32 is directly connected, Dialer0
C 172.16.123.0/24 is directly connected, Serial0.1
O IA 172.16.104.0/21 [110/65] via 172.16.123.1, 00:01:58, Serial0.1
R2#



This archive was generated by hypermail 2.1.4 : Mon Feb 02 2004 - 09:07:36 GMT-3