-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi,
I run quagga for doing some OSPF stuff on CentOS. MD5 authentication is being used within the OSPF entity. In total I have nine (ten, when I'm firing up one management host that only runs temporarily) machines in that setup. On CentOS 5 and 6 I run quagga 0.99.23.1 (built from source) now, before that 0.99.15 from repo, on CentOS 7 (the management machine) it's 0.99.22.4-4 from repo. Four of those machines act as L2TP LNS for some ten thousand sessions. Certain DSL connections are disconnected every 24 hours (due to historical reasons), so that it happens from time to time that within a few seconds several hundret or even two to four thousand routes are being flushed and added *very* quickly when the CPEs return. Only then I see this on several nodes running in that OSPF net: 2015/04/20 08:35:02 OSPF: interface ens4:12.34.56.130: ospf_check_md5 bad sequence 1429526867 (expect 1429526869) 2015/04/20 08:35:02 OSPF: interface ens4:12.34.56.130: ospf_check_md5 bad sequence 1429526868 (expect 1429526869) 2015/04/20 08:35:17 OSPF: interface ens4:12.34.56.130: ospf_check_md5 bad sequence 1429513257 (expect 1429513258) 2015/04/20 08:35:45 OSPF: interface ens4:12.34.56.130: ospf_check_md5 bad sequence 1429515808 (expect 1429515809) Is that a known issue? How could I circumvent it? Best regards, Timo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlU0oCoACgkQuSPmkPhAW0o5sQD+KEK+tBQEGTTMNNvz6bzK+jBt MoGk9bf1SxXdyuxHdncA/iR/cg92PXd7LTr2c4+cUhjCkCHMug6Qn/Ggt1kXJLz9 =6/5C -----END PGP SIGNATURE----- _______________________________________________ Quagga-users mailing list Quagga-users@lists.quagga.net https://lists.quagga.net/mailman/listinfo/quagga-users
