[quagga-users 9684] Re: OSPF "summary-address"

[Seann Clark]

Mike Tancsa wrote:
> At 02:13 PM 6/27/2008, Steve Bertrand wrote:
>> Mike Tancsa wrote:
>>> Is there an equiv of
>>> summary-address
>>> in Quagga's ospf implementation ?  On a cisco, I would use something 
>>> like
>>> summary-address 192.168.140.0 255.255.255.0
>>> to prevent a router from flooding the database with a whole mess of 
>>> connected /32 interface routes.
>>
>> Hi Mike,
>>
>> I don't think this is possible, at least directly with Quagga, and I 
>> very rarely use OSPF myself so forgive me...
>>
>> However, (without being able to test it first-hand), will you get the 
>> same result if you install a pull-up route for the /24's and inject 
>> that into OSPF?
>
> Do you mean not redistribute connected interface routes ?  I guess the 
> other option would be to use an access list possibly and manually 
> announce the various interface routes.  The /24 is tied down to the 
> disc0 interface, so that already is announced.
>
> Thanks for the suggestion!
>
>         ---Mike
> _______________________________________________
> Quagga-users mailing list
> Quagga-users at lists.quagga.net
> http://lists.quagga.net/mailman/listinfo/quagga-users
>
a stab in the dark, but did you try distribute-list which states it 
filters route information? Not sure if that would work, but it may be a 
way to make it a little less chatty and more effective as you require.

-- 
Seann Clark
Tsukinokage.net
nombrandue at tsukinokage.net