From: Jung, Jin (jin.jung@lmco.com)
Date: Sat Jun 21 2003 - 22:16:49 GMT-3
Hi all,,
That is correct behavior,
/32 routes is generated by ospf point-to-multipoint interfaces,
So you are running point-to-multipoint on r5 and r6 and r2 is running both
ptp and ptm sub interfaces.
And you have RIP and OSPF on r2, with 172.30.0.0 network under RIP.
And since r2 does not have /32 for its own ptm interface, you will not see
one at r4.
And remember that /32 is classful, just like /24 /16 /8
Now looks like you have 172.30.100.0 /29 under r2, you need to summarize
this route of /24.
And r4 will see it as 172.30.100.0 /24 and you will be able to ping r2.
Jin jung...
-----Original Message-----
From: Jason Cash [mailto:cash2001@swbell.net]
Sent: Friday, June 20, 2003 7:19 PM
To: ccielab@groupstudy.com
Subject: Rip v1 installing /32 routes.
I have a question regarding the behavior of RIP v1 and classless routes. I
have a router (r4) that is running RipV1, neighbored with R2, also running
RipV1 but OSPF and BGP as well. My problem is that, for some reason., R4 is
installing /32 routes in it's route table. These routes are part of R2's
multipoint interface (s0.100). The problem that I am facing is that R4 is
able to ping 172.30.100.5 and .6, but not .2 which is r2's interface. How
can I propagate the 172.30.100.2/32 route into RIP and why is this even
happening?
r4#si rip
R 192.168.9.0/24 [120/3] via 172.30.24.2, 02:24:04, Serial0/0.24
172.30.0.0/16 is variably subnetted, 10 subnets, 2 masks
R 172.30.200.0/24 [120/3] via 172.30.24.2, 02:24:04, Serial0/0.24
R 172.30.25.0/24 [120/1] via 172.30.24.2, 02:24:18, Serial0/0.24
R 172.30.12.0/24 [120/3] via 172.30.24.2, 02:24:18, Serial0/0.24
R 172.30.100.6/32 [120/3] via 172.30.24.2, 02:23:52, Serial0/0.24
R 172.30.100.5/32 [120/3] via 172.30.24.2, 02:24:04, Serial0/0.24
hostname r4
!
interface Loopback0
ip address 192.168.4.4 255.255.255.255
!
interface FastEthernet0/0
ip address 172.30.40.4 255.255.255.0
no keepalive
speed 100
full-duplex
!
interface Serial0/0
no ip address
encapsulation frame-relay
no frame-relay inverse-arp
!
interface Serial0/0.24 point-to-point
ip address 172.30.24.4 255.255.255.0
ip rip triggered
frame-relay interface-dlci 401
!
router rip
timers basic 30 180 0 240
passive-interface FastEthernet0/0
passive-interface Loopback0
offset-list 0 out 4
network 172.30.0.0
network 192.168.4.0
r4#ping 172.30.100.5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.100.5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/63/68 ms
r4#ping 172.30.100.6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.100.6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 60/60/60 ms
r4#ping 172.30.100.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.30.100.2, timeout is 2 seconds:
..
R2
hostname r2
!
interface Loopback0
ip address 192.168.2.2 255.255.255.255
!
interface Ethernet0
description to R1 E0 (crossover)
ip address 172.30.12.2 255.255.255.192
!
interface Serial0
no ip address
encapsulation frame-relay
no fair-queue
no frame-relay inverse-arp
!
interface Serial0.24 point-to-point
ip address 172.30.24.2 255.255.255.0
ip rip triggered
frame-relay interface-dlci 104
!
interface Serial0.100 multipoint
ip address 172.30.100.2 255.255.255.248
ip ospf network point-to-multipoint
ip ospf hello-interval 10
ip ospf transmit-delay 2
frame-relay map ip 172.30.100.2 105
frame-relay map ip 172.30.100.5 105 broadcast
frame-relay map ip 172.30.100.6 106 broadcast
!
router ospf 1
router-id 192.168.2.2
log-adjacency-changes
timers spf 6 12
summary-address 172.30.12.0 255.255.255.0
redistribute connected subnets route-map ospfconn
redistribute rip subnets route-map rip2ospf
network 172.30.100.0 0.0.0.7 area 0
network 192.168.2.2 0.0.0.0 area 1
!
router rip
timers basic 30 180 0 240
redistribute connected metric 3
redistribute ospf 1 metric 3
passive-interface BRI0
passive-interface Ethernet0
passive-interface Loopback0
passive-interface Serial0.100
network 172.30.0.0
distance 109
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:05 GMT-3