From: Brian Van Benschoten (vader@xxxxxxxxxxxx)
Date: Sun Jun 06 1999 - 16:51:36 GMT-3
I have a router (R1) running RIP and OSPF. it's connected to R2 via
token-ring. R2 runs only RIP (version 1)
R2 cannot see one attached interface on R1
This is the classic VLSM problem.
The shared link between R1 and R2 is a /24 network so RIP on R2 will only
see /24 routes.
R1 has loopback 0 with 170.100.24.0 / 27 it's in OSPF area 4 and is
summarized with the area range command into a /24. This route shows up on
the other side of the OSPF cloud properly redistributed into IGRP on another
router as a /24. (my point here is to show that I properly summarized the
OSPF area 4 as a /24)
I'm redistribuiting OSPF into RIP on R1. all the other routes from across
the network show up on R2 except for the connected loopback interface.
It seems that when you issue the "router rip..... network 170.100.0.0"
commands it over-rides the redistributed OSPF routes because it's a
connected interface on network 170.100.0.0 . I've tried setting the admin
distance, default metrics. Nothing works. Below are the important parts of
the router configs on both routers.
--------------------------------ROUTER
1----------------------------------------------------
---------------------------------CONFIG-------------------------------------
----------------
interface Loopback0
ip address 170.100.24.1 255.255.255.224
interface TokenRing0
ip address 170.100.150.1 255.255.255.0
ring-speed 16
router ospf 100
network 170.100.16.1 0.0.0.0 area 2
network 170.100.24.1 0.0.0.0 area 4
area 2 virtual-link 170.100.250.1
area 4 range 170.100.24.0 255.255.255.0
!
router rip
version 1
redistribute connected metric 200
redistribute ospf 100 metric 1
passive-interface Async1
passive-interface Loopback0
passive-interface Loopback1
network 170.100.0.0
distance 200
!
ip classless
-----------------------------------SHOW IP
ROUTE-----------------------------------------------------
170.100.0.0/16 is variably subnetted, 14 subnets, 3 masks
O E1 170.100.200.0/24 [110/2795] via 170.100.16.2, 00:21:19, Async1
C 170.100.251.0/24 is directly connected, Loopback1
C 170.100.150.0/24 is directly connected, TokenRing0
O IA 170.100.8.0/24 [110/2641] via 170.100.16.2, 00:21:19, Async1
O 170.100.2.1/32 [110/2695] via 170.100.16.2, 00:21:19, Async1
O 170.100.2.2/32 [110/2759] via 170.100.16.2, 00:21:19, Async1
O E1 170.100.1.0/24 [110/2715] via 170.100.16.2, 00:21:19, Async1
O 170.100.2.3/32 [110/2631] via 170.100.16.2, 00:21:19, Async1
C 170.100.24.0/27 is directly connected, Loopback0
C 170.100.16.2/32 is directly connected, Async1
C 170.100.16.0/24 is directly connected, Async1
O E1 170.100.42.0/24 [110/2715] via 170.100.16.2, 00:21:20, Async1
O E1 170.100.32.0/24 [110/2779] via 170.100.16.2, 00:21:20, Async1
O E1 170.100.51.0/24 [110/2795] via 170.100.16.2, 00:21:21, Async1
------------------------------ROUTER
------------------------------------------------------
---------------------------------CONFIG-------------------------------------
----------------
interface TokenRing0/0
ip address 170.100.150.2 255.255.255.0
ring-speed 16
router rip
passive-interface Ethernet4/0
network 170.100.0.0
-------------------------------SH IP
ROUTE--------------------------------------------------
C 1.0.0.0 is directly connected, Loopback0
170.100.0.0 is variably subnetted, 13 subnets, 2 masks
C 170.100.200.0 255.255.255.0 is directly connected, Ethernet4/0
R 170.100.251.0 255.255.255.0
[120/1] via 170.100.150.1, 00:00:28, TokenRing0/0
C 170.100.150.0 255.255.255.0 is directly connected, TokenRing0/0
R 170.100.8.0 255.255.255.0
[120/1] via 170.100.150.1, 00:00:28, TokenRing0/0
R 170.100.2.1 255.255.255.255
[120/1] via 170.100.150.1, 00:00:28, TokenRing0/0
R 170.100.2.2 255.255.255.255
[120/1] via 170.100.150.1, 00:00:28, TokenRing0/0
R 170.100.2.3 255.255.255.255
[120/1] via 170.100.150.1, 00:00:28, TokenRing0/0
R 170.100.1.0 255.255.255.0
[120/1] via 170.100.150.1, 00:00:28, TokenRing0/0
R 170.100.16.2 255.255.255.255
[120/1] via 170.100.150.1, 00:00:00, TokenRing0/0
R 170.100.16.0 255.255.255.0
[120/1] via 170.100.150.1, 00:00:00, TokenRing0/0
R 170.100.42.0 255.255.255.0
[120/1] via 170.100.150.1, 00:00:00, TokenRing0/0
R 170.100.32.0 255.255.255.0
[120/1] via 170.100.150.1, 00:00:00, TokenRing0/0
R 170.100.51.0 255.255.255.0
[120/1] via 170.100.150.1, 00:00:00, TokenRing0/0
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:38 GMT-3