lib/table.c | 17 ----------------- lib/vty.c | 6 ++++++ ospf6d/ospf6_lsa.c | 11 ++++------- 3 files changed, 10 insertions(+), 24 deletions(-)
New commits: commit 0d6388abc7a5da2a20a4854c400c8e176127e480 Author: Denis Ovsienko <[email protected]> Date: Mon Dec 7 19:19:13 2009 +0300 lib: remove unused function: route_dump_node() commit 78e6cd98dd88393d0863388caf37dae45435db7a Author: heasley <[email protected]> Date: Mon Dec 7 16:41:14 2009 +0300 lib: log source of vty connections (bug #566) heasley: I've used this for a while to track usage. commit 64bf3ab7291cc5c39c5add0dc1a7de447914248b Author: Ondrej Zajicek <[email protected]> Date: Mon Dec 7 12:33:20 2009 +0300 ospf6d: review LSA sequence number comparison It seems that there is a bug in ospf6d in ospf6_lsa_compare(): If LSA A has sequence number smaller than 0x80000000 and LSA B has sequence number larger than 0x80000000, ospf6_lsa_compare() returns that B is more recent than A, although RFC says that sequence numbers should be compared as signed numbers (0x8000001 smallest and 0x7FFFFFFF largest). In ospfd, the function ospf_lsa_more_recent() has it right. The problem appears when Quagga is used together with OSPFv3 in development version of BIRD daemon ( http://bird.network.cz/ ), which creates LSAs with maximum sequence number (0x7FFFFFFF) as a part of flushing/premature aging LSA from OSPF area. Because both daemons has different idea of which LSA instance is more recent, it would lead to LSA storm. http://suva.vyatta.com/git/?p=vyatta-quagga.git;a=commitdiff;h=0d6388abc7a5da2a20a4854c400c8e176127e480 http://suva.vyatta.com/git/?p=vyatta-quagga.git;a=commitdiff;h=78e6cd98dd88393d0863388caf37dae45435db7a http://suva.vyatta.com/git/?p=vyatta-quagga.git;a=commitdiff;h=64bf3ab7291cc5c39c5add0dc1a7de447914248b _______________________________________________ svn mailing list [email protected] http://mailman.vyatta.com/mailman/listinfo/svn
