[c-nsp] ospf (passive-interface default)

[Blake Dunlap]

OSPF neighbor discovery is active by default on interfaces running
inside the process.

OSPF router processes do not get interfaces attached by default. That
is what your "network" statement above is accomplishing, it attaches
the matching interfaces to that process. The additional passive not
passive work is unneeded although it does protect from accidental
additions while it's there.

-Blake

On Tue, Mar 3, 2015 at 12:41 PM, CiscoNSP List
<cisconsp_list at hotmail.com> wrote:
> Hi Everyone,
>
> Dont have a lab handy to test this, so hoping someone can answer:
>
> If you configure:
>
> router ospf 1
> network 10.10.10.0 0.0.0.3 area 1
>
> without passive-int default, will ospf be "enabled" on all Interfaces, or just the Interface with 10.10.10.0/30 configured on it?
>
> I was always under the impression that (best practice) is to do the following, so that ospf is disabled on all ints, apart from the ones configured with "no passive int foo"
>
> router ospf 1
> passive-int default
> no passive int gi0/1
> network 10.10.10.0 0.0.0.3 area 1
>
> ...and,  (As an alternative) is configuring ospf under each interface now a method many use instead of the above example?
>
> ...I havent tried the "per int" method (I will later today), but in theory, I think having all the config under "router ospf xx" would be easier to maintain...i.e. all the config is in the one section for ospf?
>
> Cheers.
>
>
> _______________________________________________
> 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/