W dniu 2011-03-20 23:03, Adrian Czapek pisze:
I have no idea. It is true that BIRD does not check checksums of LSAs later when they are stored, but it checks that when it receives them. If you did restart of a BIRD (or at least OSPF protocol) then no bad LSA could survive that. It might be useful if you could get a tcpdump copy of the OSPF communication [*] on the problematic link (when there is a problem). and output of 'show ospf lsadb'.
[*] tcpdump -i ethX -s 0 -w dumpfile ip proto 89
I am not quite sure if it is LSA checksum. I don't have tcpdump stored anywhere, because I was watching it "live", but it looked like RouterOS had a problem with Hello packet itself. The moment I've seen Hello packet broadcasted to the link, the wrong checksum entry poped in RouterOS logs.
I am back with this issue after few months. I encountered the same issue on the other subnet, when I was trying to upgrade bird. Everytime I shutdown bird and start it again, my OSPF don't go UP. On mikrotiks, I have "wrong checksum" as described in previous mails. Here is 'show ospf lsadb' during that state: bird> show ospf lsadb Global Type LS ID Router Age Sequence Checksum 0005 0.0.0.0 78.31.136.246 23 80000001 c2ed 0005 10.100.64.0 78.31.136.246 23 80000001 c839 0005 10.111.65.0 78.31.136.246 23 80000001 de26 0005 10.128.0.0 78.31.136.246 23 80000001 35f1 0005 78.31.138.128 78.31.136.246 23 80000001 5d5a Area 0.0.0.1 Type LS ID Router Age Sequence Checksum 0001 78.31.136.246 78.31.136.246 14 80000001 ec42 tcpdump file sent private. Regards -- Adrian Czapek