Project

General

Profile

Actions

Bug #3651

closed

NLSR not setting router name command prefix correctly

Added by Ashlesh Gawande almost 9 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Normal
Target version:
-
Start date:
06/15/2016
Due date:
% Done:

100%

Estimated time:

Description

Currently nlsrc is supposed to listen on localhost and router name prefix (http://redmine.named-data.net/issues/2737) but it only listens for localhost correctly.

It registers the correct router prefix but then sets interest filter for /lsdb (LsdbDatasetInterestHandler) instead of <$RouterName>/lsdb.
(Can be checked by running NLSR with DEBUG log level).

This is happening because LsdbDatasetInterestHandler is initialized in Nlsr constructor where it is passed m_confParam.getRouterPrefix()
before it is built later in Nlsr::initialize m_confParam.buildRouterPrefix().

Hence in the constructor an empty string is passed for router name.


Related issues 2 (0 open2 closed)

Related to NLSR - Task #2737: Serve LSDB dataset over localhost prefixClosedVince Lehman04/08/2015

Actions
Blocks NLSR - Task #2806: Implement NDN routing status page which uses Interests to fetch the NLSR LSDB datasetClosedMuktadir Chowdhury05/12/2015

Actions
Actions #1

Updated by Ashlesh Gawande almost 9 years ago

  • Related to Task #2737: Serve LSDB dataset over localhost prefix added
Actions #2

Updated by Ashlesh Gawande almost 9 years ago

  • Assignee set to Muktadir Chowdhury
Actions #3

Updated by Ashlesh Gawande almost 9 years ago

  • Blocks Task #2806: Implement NDN routing status page which uses Interests to fetch the NLSR LSDB dataset added
Actions #4

Updated by Ashlesh Gawande almost 9 years ago

  • Description updated (diff)
Actions #5

Updated by Ashlesh Gawande over 8 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF