[c-nsp] router ospf limitations

[Marcus Keane]

Hi,

In answer to your second question, the answer is no. Yes, it'll probably
prevent an accidental adjacency on account of the different timers, but
it won't prevent somebody who's determined: if they change the timers on
the new router on the LAN, they're good to go.

You're best bet is to configure md5 authentication with a key that you
don't use elsewhere.
Marcus

-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Volodymyr
Yakovenko
Sent: Wednesday, 10 August 2005 3:04 AM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] router ospf limitations

Hello!

 There is well-known feature of global 'router ospf' process - the 
 'passive interface' command which is handy in some scenarios.

 For some reason VRF-specific ospf process does not support this handy
command.
 Could someone (from Cisco, probably?) comment reasons? Will it be
supported
 in the IOS releases?

 Am I right that similar behavior (manual block of OSPF negotations on
specific
 interface) can be achieved by interface-specific 

	ip ospf network non-broadcast

 command (I am talking about Ethernet interfaces)?

 
-- 
Regards,
Volodymyr.

_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/