On Sun, Jul 17, 2005 at 01:14:26PM -0700, Michael DeMan wrote:
>I'm not a super-expert with OSPF, but also keep in mind that there are
>a few fundamental features Quagga is still missing.
Thanks for the pointers, from those commands you mentioned I was able to
find the following URLs which has some good discussions of them:
It does indeed look like passive-interface is what I'm looking for. Too
bad it's not available. I think setting up as a stub will get rid of the
extra announcements, I'll have to do some testing of that.
>would be to effectively use areas. At least then, even though area 0
>will see all the little routes, it is my understanding, that the other
>non-0 areas will not see the routes to other non-0 areas. Finally,
I'm kind of more worried about having a neighbor show up for every
subnet I define. While setting up a passive-interface default would be
ideal, I can work with manually specifying the passive interface. In fact,
I could even directly connect the two routers on a different interface just
for the OSPF and packet exchange, and make the internal interface (which
has all the subnets) passive.
>read up on stubby areas and not-so-stubby areas, those can at least
>help the leaf areas of your network to not worry about getting huge
>route table updates.
I don't really have any leaf areas. OSPF is only used between my pair of
Zebra routers and the facility network.
You know you're in Canada when: The weather reports starts with "All
temperatures are degrees below zero unless otherwise stated."
Sean Reifschneider, Member of Technical Staff <jafo@xxxxxxxxx>
tummy.com, ltd. - Linux Consulting since 1995: Ask me about High Availability
Zebra mailing list