NLSR

We recently reset a testbed router, causing it to lose/forget its sequence number. Upon restarting, its updates were not fetched by other routers since they had sequence numbers in the 1-20 range, while other routers thought the lower sequence numbers were already fetched.

In the logs, you could see the original sequence number it lost, in part because other routers were trying to fetch it. Stopping NLSR, modifying the nlsrSeqNo.txt file's numbers to be greater than the one observed, and restarting NLSR fixed the problem, causing the other routers to fetch its updates. Ideally, there would be some logic inside NLSR to handle this issue automatically in some way, since modifying the state file felt like a hack.