Mailing List Archive

ospfd 2 bugs
Hi, I found 2 bugs in the quagga ospfd.

Bug 1:

Network: RT0( area 1 ) <-> RT1 ( area 1 ) <-> RT2(backbone)<->
RT3(area 2)


RT3 with 2 interfaces in the area 2: 10.222.1.1/24 and 10.222.2.1/24
So, I specify 'area 2 range 10.222.0.0/16', after quagga restart RT0
know 10.222.0.0/16 route, but
after some time ... no 10.222.0.0/16 route on the RT0.


Bug 2:

Same network: RT0( area 1 ) <-> RT1 ( area 1 ) <->
RT2(backbone)<2-2> RT3(area 2)

RT2 and RT3 have 2 links between them in the backbone area.

When changing ospf cost of RT2 <-> RT3 links RT0 have no routes to
backbone. After rebuilding LSA database on the RT0 routes to area 2 goes up.


So, I think, this is not 'area range' bug, I think there is error in
the LSA database updates between areas.
I've programming skills to fix this, but have no time to work for free.
If anybody need this fixed and could pay, please mail.
Re: ospfd 2 bugs [ In reply to ]
On Wed, Jun 30, 2004 at 01:22:46AM +0600, Kir Kostuchenko wrote:
> Hi, I found 2 bugs in the quagga ospfd.
>
>
> So, I think, this is not 'area range' bug, I think there is error in
> the LSA database updates between areas.
> I've programming skills to fix this, but have no time to work for free.
> If anybody need this fixed and could pay, please mail.

Don't you have to use area number 0 for the backbone?

-Andy
Re: ospfd 2 bugs [ In reply to ]
Andrew J. Schorr wrote:

>On Wed, Jun 30, 2004 at 01:22:46AM +0600, Kir Kostuchenko wrote:
>
>
>> Hi, I found 2 bugs in the quagga ospfd.
>>
>>
>> So, I think, this is not 'area range' bug, I think there is error in
>>the LSA database updates between areas.
>>I've programming skills to fix this, but have no time to work for free.
>>If anybody need this fixed and could pay, please mail.
>>
>>
>
>Don't you have to use area number 0 for the backbone?
>
>

number 0 for backbone.