From: Vaughan Lee (vaughan.lee@xxxxxxxxxxx)
Date: Fri Jul 23 1999 - 06:03:12 GMT-3
If you want to stop the 12.0.0.0 route from being redistributed from rip
into ospf, you need to have your distribute list under ospf, as in
'distribute-list 10 out rip', and not under rip. It's one of those
oddities.
Although it may not be strictly true, I tend to think of it in terms of
rip routes being distributed out of the routing table into OSPF - it's
the only way I can get to think of the out parameter being used
logically!
Regards,
Vaughan
Vaughan Lee, Network Specialist.
debis IT Services (UK) Ltd.
E-mail: vaughan.lee@debis.co.uk
Direct Phone: 01908 279561
Direct Fax: 01908 279061
http://www.debis.co.uk/
-----Original Message-----
From: Bill Carter [mailto:bcarter@family-net.net]
Sent: 23 July 1999 06:04
To: CCIE Lab group
Subject: Redist dist-list problems
I am doing mutual redistribution between RIP and OSPF. OSPF and RIP
share 150.100.X.X. All interfaces can ping each other. I added a
12.0.0.0 interface to the RIP domain (no on the Redist router). I want
to filter the redistribution so the 12.X.X.X network is not advertised
into the OSPF domain.
After a clear ip route * the ospf routers learn the 12.0.0.0 network
form ospf. Why??
router ospf 1
redistribute rip subnets
passive-interface Ethernet0
passive-interface Serial1
network 150.100.1.0 0.0.0.255 area 0 (interface s0.1 ospf domain)
router rip
redistribute ospf 1
passive-interface Serial0.1
network 150.100.0.0
default-information originate
distribute-list 10 out ospf 1
access-list 10 deny 12.0.0.0 0.255.255.255
access-list 10 deny 150.100.1.0 0.0.0.255 (serial 0.1 interface to
OSPF domain)
access-list 10 permit any
-- ~~~~~~~~~~~~~~~~~~~~~~~~ Bill CarterFavorite Quote "bodega stuck again... " -Cisco Bug CSCdk37204 ~~~~~~~~~~~~~~~~~~~~~~~~
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:42 GMT-3