06.03.2017 02:14, Paul Jakma пишет:
On Sat, 4 Mar 2017, Dmitry Melekhov wrote:
Hello!
Looks like this patch fixes this problem, i.e. LSA5 is generated from
LSA7:
Great.
But I found another problem- LSA7 MaxAge does not remove routes from
local table and does produce LSA7:
2017/03/04 11:11:44 OSPF: LSA[Type7:10.236.16.0]: MaxAge LSA removed
from list
2017/03/04 11:11:44 OSPF: LSA[Type7:10.236.16.0]: data freed
0x7efe18430f00
And that's all , still have:
10.236.16.0 10.18.0.254 239 0x80000003 0xcebc E2
10.236.16.0/24 [0xfdf3]
10.236.16.0 172.17.0.18 891 0x80000001 0x0473 E2
10.236.16.0/24 [0xfde8]
Hmm, is it perhaps that the type-5 wasn't flushed at the same time?
No, I guess that type-5 was not generated because of this bug.
Although even local (on NSSA-ABR ) routing database was not altered:
netstat -rn | grep 10.236.16.
10.236.16.0 10.18.0.1 255.255.255.0 UG 0 0 0
eth1
I.e. quagga just ignores MaxAge LSA Type 7.
At least it looks like this.
I.e. the type-7 is gone, but the synthesised type-5 that was
translated from it hung around and is leading to this and the route?
What does 'show ip ospf database' say?
This (on NSSA-ABR):
10.236.16.0 10.18.0.254 239 0x80000003 0xcebc E2 10.236.16.0/24
[0xfdf3]
10.236.16.0 172.17.0.18 891 0x80000001 0x0473 E2 10.236.16.0/24
[0xfde8]
netstat -rn | grep 10.236.16.
10.236.16.0 10.18.0.1 255.255.255.0 UG 0
0 0 eth1
btw, nssa translation only works with nssa translate-always with
translate-candidate Configure NSSA-ABR for translate election
(default) it does not translate all routes, although there is only
one NSSA-ABR here...
Ah.
regards,
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
