From: Chua, Parry (Parry.Chua@xxxxxxxxxx)
Date: Wed Mar 06 2002 - 22:35:27 GMT-3
Hi JP,
Have you receive my respond ?
I suggest you to do some test :
1. create a loopback int at R3 said 172.16.3.3 255.255.255.0 and adverise it in
OSPF.
set the ip ospf network type point-to-point
2. Create a loopback interface at R1 said 172.16.11.1 255.255.255.0
3. Routing table, R1 should have 172.16.3.0 and at R3 should have 172.16.11.0
4. Do a extended ping from R1 to 172.16.3.3 using 172.16.11.1 as R1 source addr
ess
5. Do a extended ping from R3 to 172.16.11.1 using 172.16.3.3 as R3 source addr
ess.
Below is my last reply to you, any comment ?
"I guess Jeonqwoo has some problem with this setup, let me try to explain and s
ee it help.
OSPF
====
Shold run on R2 and R3, this has not problem except it has different mask as co
mpare to RIP
RIP
====
should run on R1 and R2 but RIP is a classful protocol so it will enable on all
interface
in R2. In clude the serial link between R2 amd R3, this should be in OSPF only,
but no way to exclude fro RIP. But R1 will not see this network due to the mas
k different.
If you want R1 to see the network 172.16.1.0/30 without redistribution, create
a secondary address
between R1 and R2 with /30 mask. Or create a tunnel between R1 and R2 with /30
mask will do the same.
Mutual redistribution at R2
===========================
When you redistbute RIP to OSPF,at least you should block network 172.16.1.0/30
, it belong to OSPF.
If you want 172.16.1.0/30 to redistribute from OSPF into RIP as /24, then I kno
w two ways :
1. At R2, create a dummay area, R2 become ABR, do area 0 range 172.16.1.0 255.2
55.255.0
2. Create another OSPF process and redistrbute 172.17.1.0/30 to it and summary
address at this
new OSPF process., At R2 RIP, redistribute this OSPF process to RIP"
> Parry Chua
>"
Parry Chua
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:55 GMT-3