summaryrefslogtreecommitdiff
path: root/ospfd/ospf_lsa.c
AgeCommit message (Collapse)Author
2003-05-06Reverting the NSSA maxage walker loop addition for now, until all the otherpaul
problems with NSSA are resolved, and we can determine whether this had any point.
2003-05-06NSSA /might/ be missing this. I'm not sure.paul
It didnt solve a particular problem of Hasso's, but i'm committing it just for posterities sakes, so i dont lose it (i'll revert it immediately).
2003-04-13From: Hasso Tepper <hasso@estpak.ee>paul
To: zebra@zebra.org Subject: [zebra 18648] [PATCH] Selforiginated Type-7 LSA's are not flushed from lsdb
2003-04-13Author: amirpaul
Date: 2003-04-10 14:32:31 +0200 (Thu, 10 Apr 2003) New Revision: 212 Modified: zebra-ag/trunk/ospfd/ospf_lsa.c Log: I've fixed a small opaque lsa bug which got triggered when deleting opaque lsa of type 11. It used area->ospf->.. when area was null. This was replaced by a ospf = ospf_lookyp(); ospf->...
2003-04-05Add tests for debug enabled to PtMP LSA creation functionspaul
2003-04-042003-04-04 Paul Jakma <paul@dishone.st>paul
* Sync to Zebra CVS * Fix lib/thread.h leak * Fix small Opaque LSA leak * Do not configure OSPF interfaces for secondary addresses * vtysh fixes from Hasso * Dave Watson's missing ntohs fix
2003-04-03From: David Watson <dwatson@eecs.umich.edu>paul
Subject: [zebra 18573] PATCH ospfd: byte order error in assert statement I found a bug in the ospfd code tickled this morning by a Type 1 LSA with exactly 62 entries (LSA length of 768, or 0x0300). A missing ntohs in ospf_lsa.c:ospf_lsa_different() causes an assert statement to fail, stopping ospfd. > assert (l1->data->length > OSPF_LSA_HEADER_SIZE); So, a length of type 768 turns into a length of 3 which is obviously less than 20. David
2003-03-252003-03-25 Paul Jakma <paul@dishone.st>paul
* sync to latest zebra CVS * spec file: updated and added define for ospf-api/client NB: OSPF-API has been broken by the zebra.org changes, which has added struct ospf * as a new arg to many functions
2003-02-13Fix debug statement in ospf_packet.c and merge error in ospf_lsa.cpaul
2003-02-03Merge to zebra.org CVS 20030203 16:30GMTpaul
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.
2002-12-13 Kevin C Miller <kevinm@andrew.cmu.edu>paul
[zebra 16681] OSPF NSSA Patches
2002-12-13zebra link state detection supportpaul
2002-12-13ospfd Point-to-Multipoint supportpaul
2002-12-13Initial revisionpaul