From: Richard Hanks (ccieingroup@hotmail.com)
Date: Sun Dec 22 2002 - 13:50:02 GMT-3
Hi Sage,
CCO is right. The distribute-list here mentioned is "distribute-list 1 in" but
not distribute-list 1 in serial 1/0". You can not use the interface distribute
list on OSPF, it wouldn't work. So if you want to filter the 160.160.0.0/22 on
R1, you are supposed to do the commands on R1 but not R2. Try this one:
Config on R1 here:
distribute-list 1 in
access-list 1 deny 160.160.0.0
access-list 1 permit any
I think it will work. But if your scenario need you to config on on R2, I
think there must be another way. But I need more detail information about your
scenario, such as the Stub or ABR or ASBR information.
Richard Hanks
----- Original Message -----
From: Sage Vadi
To: ccielab@groupstudy.com
Sent: Sunday, December 22, 2002 5:20 AM
Subject: OSPF: distribute-lists
This is what CCO says:
Q: Can I use the distribute-list in/out command with
OSPF to filter routes?
A: OSPF routes can't be filtered from entering the
OSPF database. The distribute-list in command only
filters routes from entering the routing table, but it
doesn't prevent link-state packets from being
propagated.
~~~ MY PROBLEM ~~~
Diagram:
R1
|
R2--R3
R1 learns 160.160.0.0/22 from R2, R2 learns this from
R3. Fairly simple right?
I want to put a distribute-list inbound on R2's serial
interface to prevent R1 from learning this
route/network.
Config on R2 here:
distribute-list 108 in Serial1/0
access-list 108 deny ip 160.160.0.0 0.0.3.255 any
Problem:
R1 still has the route in it's routing table!!! Doh!
CCO says it should not be in the routing table, but it
should be in the OSPF database.
Q) Any tips/help/suggestions?
rgds,
Sage
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
.
.
This archive was generated by hypermail 2.1.4 : Fri Jan 17 2003 - 17:21:51 GMT-3