Patrick Ramsey wrote:
>
> Anyone remember how to ACL ospf?
>
> basically I have area 0 on one interface of a router that
> touches another company's area 0 (we're splitting) And I want
> to stop sending them updates and stop receiving updates from
> them.
>
> The real kicker is that I still
]]
Sent: Thursday, September 13, 2001 3:33 PM
To: [EMAIL PROTECTED]
Subject: RE: filtering ospf [7:19856]
How about a passive interface with a neighbor statement. Changes the
behavior from multicast to unicast, thereby eliminating traffic to the rouge
router.
-Original Message-
From
Hi Patrick,
I may need you to elaborate on your question a bit, because I am a little
unclear on your desired OSPF outcome here, but
Besides the obvious passive interface -- which does allow the interface
address to be advertised via OSPF, but will not allow the router to form an
adjacen
224.0.0.5 and 224.0.0.6, in fact I just did this to stop OSPF from
becoming an interesting packet and firing up an ISDN backup link!!
Dave
Patrick Ramsey wrote:
>
> Anyone remember how to ACL ospf?
>
> basically I have area 0 on one interface of a router that touches another
> company's area
use an access list that filters on ip protocol number 89
access-list 101 deny ospf source destination
access-list 101 permit etc
but based on what you say about a router of yours on "their" side? maybe
"they" should take responsibility for the filtering on the appropriate
interfaces?
Chuck
---
How about a passive interface with a neighbor statement. Changes the
behavior from multicast to unicast, thereby eliminating traffic to the rouge
router.
-Original Message-
From: Patrick Ramsey [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 3:06 PM
To: [EMAIL PROTECTED]
Su
6 matches
Mail list logo
