Project

General

Profile

Actions

Bug #4543

closed

NLSR no longer responds to remote status requests

Added by Ashlesh Gawande about 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
03/09/2018
Due date:
% Done:

100%

Estimated time:

Description

NLSR is not listening on router prefix anymore. Need to add a unit test to check this.

Actions #1

Updated by Ashlesh Gawande about 6 years ago

  • Description updated (diff)
Actions #2

Updated by Ashlesh Gawande about 6 years ago

  • Assignee set to Laqin Fan
Actions #3

Updated by Laqin Fan about 6 years ago

In NLSR, dispatcher can setInterestFilter for the remote router interests on dummy face without router prefix registration when I use addTopPrefix(topPrefix, false, m_signingInfo), so my unit test case for remote router retrieving dataset can pass successfully. But in reality nlsr doesn't register router name prefix.

Is there any way I can add in my unit test to check if the router prefix is registered successfully or not to avoid this error?

Actions #4

Updated by Junxiao Shi about 6 years ago

But in reality nlsr doesn't register router name prefix.

addTopPrefix invocation sets wantRegister=false so that the dispatcher does not register prefix. It must be changed to true.

Is there any way I can add in my unit test to check if the router prefix is registered successfully or not to avoid this error?

The test case needs to assert a prefix registration command was emitted.

Actions #5

Updated by Ashlesh Gawande about 6 years ago

  • Assignee changed from Laqin Fan to Ashlesh Gawande
Actions #6

Updated by Ashlesh Gawande about 6 years ago

  • Status changed from New to In Progress
Actions #7

Updated by Ashlesh Gawande about 6 years ago

NLSR should:

registerPrefix for:
/<router-name>/nlsr

set interest filter for:
/<router-name>/nlsr/INFO
/<router-name>/nlsr/KEY
/<router-name>/nlsr/lsdb/name
/<router-name>/nlsr/lsdb/coordinate
/<router-name>/nlsr/lsdb/adjacency
/<router-name>/nlsr/routing-table

NLSR is added because in the future /<router-name> might not be registered by NLSR.
Process ID will be added after NLSR component in #3277

For consistency, "/localhost/nlsr" should be changed to "/localhost/NLSR"
will keep this /localhost/nlsr otherwise change is required in NFD, will change NLSR above to nlsr
registerPrefix for:
/localhost/nlsr

set interest filter for:
/localhost/nlsr/lsdb/name
/localhost/nlsr/lsdb/coordinate
/localhost/nlsr/lsdb/adjacency
/localhost/nlsr/routing-table
/localhost/nlsr/prefix-update/advertise
/localhost/nlsr/prefix-update/withdraw
/localhost/nlsr/rib/register
/localhost/nlsr/rib/unregister

Need to update any affected wiki pages.

Actions #8

Updated by Ashlesh Gawande almost 6 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 0 to 100
Actions #9

Updated by Saurab Dulal almost 6 years ago

  • Target version changed from v0.5.0 to 0.4.3
Actions

Also available in: Atom PDF