[j-nsp] Restricting OSPF prefixes listen from neighbor

[Leigh Porter]

Indeed Cisco do, filtering LSAs will break (very much) the LSA DB and cause routing inconsistency.
 
The whole idea is that every router has the same DB. There is always a better way to do things :)
 
--
Leigh
 

________________________________

From: juniper-nsp-bounces at puck.nether.net on behalf of Jonathan Looney
Sent: Wed 9/6/2006 2:58 PM
To: Vladimir S. Blazhkun
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Restricting OSPF prefixes listen from neighbor



On 9/6/06, Vladimir S. Blazhkun <v.blazhkun at pcs-net.net> wrote:
>
> > Dear All
> >
> > I have a scenario, where i have created a OSPF neighborship with my client.
> > Client is advertising me all of its routes, but i have to restric this
> > advertisement at my input interface end.
> > Juniper ospf import policy doesnot work.  Is there any way to restrict it as
> > CISCO has distribute-list option to filter out the listen prefix lists.
>
> import policy for OSPF works only for external (calculated from Type-5/7
> LSAs) routes. But it doesn't filter any LSAs, because it will break
> consistency of link-state databases.
>
> There is no way to restrict routes from OSPF neighbors in JUNOS (except
> external routing information).

Incidentally, I think Cisco has the same restrictions on filtering
OSPF routes for the same reasons.

-Jon
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp