From: James.Jackson@broadwing.com
Date: Mon Jun 23 2003 - 19:09:28 GMT-3
Problem is that your BVI interface has a different mask than your Ethernet
interface but is in the same major net. First question would be why you have
a /26 on R1 eth but soln has /24 on R2 eth ?
-----Original Message-----
From: Jason Cash [mailto:cash2001@swbell.net]
Sent: Monday, June 23, 2003 4:53 PM
To: ccielab@groupstudy.com
Subject: RIP routes / summary
I am working on IPE Section 31 and having a problem with the BVI interface
on R1. R1 and R2 are running RIP v1 (between them). The problem I am
facing is that for some reason, the BVI interface (172.31.10.0
255.255.255.0) is not showing up in the route table of R2. It is listing in
the RIP db of R1, but not R2:
R1(e1)----(e0)R2
The tasks instruct "RIP updates b/w R1 and R2 should not contain subnet mask
info" so that limits me to version 1. Also, as part of the solution for R2,
there is a summary address listed on R2. Does this serve any purpose being
that R1 is running RipV1? I as because this route is not showing in R1s RIP
db.
RIP SUMMRY
interface Ethernet0
ip address 172.31.12.2 255.255.255.0
ip rip send version 1
ip rip receive version 1
ip summary-address rip 172.31.52.0 255.255.255.0 <<<<<<<<
r1#sh ip rip data
0.0.0.0/0 auto-summary
0.0.0.0/0
[2] via 172.31.12.2, 00:00:22, Ethernet1
172.31.0.0/16 auto-summary
172.31.10.0/24 directly connected, BVI1 <<<<<<<<<<<
172.31.12.0/26 directly connected, Ethernet1
192.168.1.0/24 auto-summary
192.168.1.1/32 directly connected, Loopback0
192.168.2.0/24 auto-summary
192.168.2.0/24
[1] via 172.31.12.2, 00:00:22, Ethernet1
192.168.5.0/24 auto-summary
192.168.5.0/24
[2] via 172.31.12.2, 00:00:22, Ethernet1
r2#sh ip rip data
0.0.0.0/0 auto-summary
0.0.0.0/0
[1] via 172.31.52.1, 00:00:21, Serial0
172.31.0.0/16 auto-summary
172.31.12.0/26 directly connected, Ethernet0
172.31.25.0/24 directly connected, BRI0
172.31.52.0/24 int-summary
172.31.52.0/30 directly connected, Serial0
172.31.100.0/28
[1] via 172.31.52.1, 00:00:21, Serial0
172.31.200.0/25
[1] via 172.31.52.1, 00:00:21, Serial0
192.168.1.0/24 auto-summary
192.168.1.0/24
[1] via 172.31.12.1, 00:00:09, Ethernet0
192.168.2.0/24 auto-summary
192.168.2.2/32 directly connected, Loopback0
192.168.5.0/24 auto-summary
192.168.5.5/32
[1] via 172.31.52.1, 00:00:21, Serial0
Here is the config of R1:
hostname r1
!
ip subnet-zero
no ip domain-lookup
!
bridge irb
!
interface Loopback0
ip address 192.168.1.1 255.255.255.255
!
interface Ethernet0
description ethernet to BB1
no ip address
bridge-group 1
!
interface Ethernet1
description ethernet connected to R2
ip address 172.31.12.1 255.255.255.192
ip rip send version 1
ip rip receive version 1
!
interface BVI1
ip address 172.31.10.1 255.255.255.0
!
router rip
redistribute connected
passive-interface BVI1
passive-interface Loopback0
network 172.31.0.0
!
router bgp 12
no synchronization
bgp log-neighbor-changes
neighbor 172.31.12.2 remote-as 12
no auto-summary
!
ip classless
no ip http server
!
!
ip access-list standard connected
permit 192.168.1.1
permit 172.31.12.0 0.0.0.255
permit 172.31.10.0 0.0.0.255
route-map crip permit 10
match ip address connected
!
!
bridge 1 protocol ieee
bridge 1 route ip
alias exec c config t
alias exec shi sh ip int brief
alias exec si sh ip route
alias exec sb sh ip bgp
!
line con 0
session-timeout 120
exec-timeout 60 0
length 30
line aux 0
transport input all
line vty 0 4
password cisco
login
!
end
I don't think I am missing anything but can't figure this out! This will
cause a problem as R2 will send packets to R5 (via default) if this route is
not received.
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:08 GMT-3