summaryrefslogtreecommitdiff
path: root/ospfd
AgeCommit message (Collapse)Author
2003-02-03Initial revisionpaul
2003-01-27Revert comment out of:paul
if (ospf_debug_packet & OSPF_DEBUG_RECV) which was causing unconditional ospf_ip_header_dump (ibuf). (introduced with kevin millers patch)
2003-01-27revert unchecked debug info generated by Kevin Miller's patchpaul
2003-01-25Paul Jakma:paul
[zebra 17352] ospf network matching (aka need for peer /32 for PtP) change behaviour of network <prefix> area N statement wrt to PtP.
2003-01-22Matthew Grant <grantma@anathoth.gen.nz>paul
[zebra 17290] [PATCHES] - Fixes for problems in 0.93b portfix patch
2003-01-18Date: Fri, 20 Dec 2002 17:28:45 +0900paul
From: Masahiko Endo <endo@suri.co.jp> Reply-To: zebra@zebra.org To: zebra@zebra.org Cc: kunihiro@zebra.org, yokota@kddlabs.co.jp Subject: [zebra 16823] [PATCH] Bugfix and new feature in Opaque-LSA handling. ----- * ----- * ----- * ----- * ----- * ----- * ----- * ----- * ----- * ----- Changes 2002.12.20 1. Bug fixes 1.1 When an opaque LSA is being removed from (or added to) the LSDB, it does not mean a change in network topology. Therefore, SPF recalculation should not be triggered in that case. There was an assertion failure problem "assert (rn && rn->info)" inside the function "ospf_ase_incremental_update()", because the upper function "ospf_lsa_maxage_walker_remover()" called it when a type-11 opaque LSA is removed due to MaxAge. 1.2 Type-9 LSA is defined to have "link-local" flooding scope. In the Database exchange procedure with a new neighbor, a type-9 LSA was added in the database summary of a DD message, even if the link is different from the one that have bound to. 2. Feature enhancements 2.1 Though a "wildcard" concept to handle type-9/10/11 LSAs altogether has introduced about a year ago, it was only a symbol definition and actual handling mechanism was not implemented. Now it works.
2003-01-17From endo@suri.co.jp Fri Jan 17 23:36:30 2003paul
Date: Fri, 20 Dec 2002 17:58:43 +0900 From: Masahiko Endo <endo@suri.co.jp> Reply-To: zebra@zebra.org To: zebra@zebra.org Cc: kunihiro@zebra.org Subject: [zebra 16824] [PATCH] nsm_kill_neighbor [ The following text is in the "ISO-2022-JP" character set. ] [ Your display is set for the "ISO-8859-1" character set. ] [ Some characters may be displayed incorrectly. ] Hi Ishiguro-san, Here is my problem analysis against the case that the ospfd crashes when an interface is brought down. When the ospfd receives a ZEBRA message "ZEBRA_INTERFACE_DOWN" from zebra daemon, the ospfd performs bunch of ospf-interface cleanup for the notified zebra-interface. There are cases that neighbor instance "nbr", which will be removed afterward, may scheduled in the NSM thread event queue. And when the NSM event thread is fired, dereference for this already freed "nbr" pointer causes SIGSEGV. Please take a look at following timeline of processing sequences.
2002-12-13 Kevin C Miller <kevinm@andrew.cmu.edu>paul
[zebra 16681] OSPF NSSA Patches
2002-12-13[zebra 14631] Generic PtP and RFC3021 interface addressing supportpaul
2002-12-13zebra link state detection supportpaul
2002-12-13ospfd Point-to-Multipoint supportpaul
2002-12-13Greg Troxel <gdt@ir.bbn.com>paul
[zebra 15715] FIX for ospf md5 authentication problem, finally! fix copy of ospf packet buffer
2002-12-13zebra-ospfd-md5auth-seqnum.patch - paulj - change OSPF md5 sequence numberpaul
to be derived from time() to speed up synching after restart of ospfd
2002-12-13Initial revisionpaul