On Fri, 26 Jun 2015, Ondrej Zajicek wrote:
The described strategy was used in BIRD 1.4.5 (and older versions),
which did not have problems in this case (probably because there were
still enough LSUPD packets passing through).
Aha. Got it.
The new BIRD 1.5.0 (affected by the problem) uses more sane approach -
send the new LSREQ packet when all LSAs requests in the last LSREQ
packets were received by LSUPDs (and therefore removed from the LS
request list). And also retransmit LSREQ after RxmtInterval (default 5
s). I presume that is more-or-less the same approach as Quagga?
Yes, that sounds like the same thing Quagga ospfd does.
We have the same default RxmtInterval. I wonder, is that value perhaps too
high, in this day and age?
If i understand Andrew correctly, the Quaggas were not affected as they
run on different machines connected to different switch ports without
configured rate limitation.
Sounds plausible. Have to wait to hear from Andrew! :)
regards,
--
Paul Jakma [email protected] @pjakma Key ID: 64A2FF6A
Fortune:
From: Ean Schuessler <[email protected]>
The unrecognized minister of propaganda,
E
-- Debian, joking
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
