NLSR

Current code: An lsa is detected by Chronosync. Then the code tries to express interest for this lsa. If the interest times out the code will re-express the interest till deadline (which is set to own lsa refresh time). Now in the meantime a new lsa is detected by Chronosync. So a new interest is expressed for this new lsa. But interest for old lsa is still being re-expressed (if the time is still within the deadline).

Hence to fix this I map the lsa sequence number to a router and update the lsa sequence number for that router if a new lsa is detected. Then in timeout I check whether lsa sequence number is still the same and if not I stop expressing the interest. Before mapping a new lsa sequence number to a router I also check whether the lsa seq number is greater than the one already mapped to the router.

Similar check is applied for revalidation of content (i.e. we need to stop trying to re-validate an old lsa).