Clarify README and correct the usage message from NLSR
Updated by Syed Amin almost 7 years ago
On linux, if you are not building protobuf from sources then installing "libprotobuf-dev" doesn't install protoc compiler. Therefore I suggested to change the following line in INSTALL.md:
sudo apt-get install libprotobuf-dev
sudo apt-get install libprotobuf-dev protobuf-compiler
Updated by A K M Mahmudul Hoque almost 7 years ago
- Status changed from New to Code review
- % Done changed from 0 to 90
Here is the conversation of email to start this issue
On Tue, 2014-08-05 at 11:45 -0500, Syed Obaid Amin wrote:
Here is a brief history that maybe of interest to you. nlsr for ccnx
can be controlled by CLI or remotely. It does so by listening on a
port on which it accepts commands and process them. The '-p ' switch was introduced to change the default port on which it
listens for this.
thank you a lot for pointing this out, I will keep it in mind if I need
nlsr for nfd doesn't support this feature. The consensus was to use
Interest/Data model for the communication between nfd and routing
protocols(like nlsr). Plus, this functionality should be provided to
all routing protocols (not just nlsr).
That's on track and I'm agree with it.
As a result, we added two new commands, advertise and withdraw in
the RibManager, which will allow to specify the routing protocol for
disseminating the name prefixes. However, these commands are not
I hope that they will grow out soon. Thank you a lot for the history.
On Tue, Aug 5, 2014 at 9:43 AM, Salvatore Signorello
Thank you both,I'm looking at the following documentation to get know the RIB management http://redmine.named-data.net/projects/nfd/wiki/Management , if you want to point me more resources, I would be glad. If I grep the NFD main directory looking for 'advertise', I find no trace of this command, where should it be? Best, Salvo On Tue, 2014-08-05 at 06:55 -0700, Junxiao Shi wrote: > Hi Hoque > > Instead of opening an "API client port", I suggest NLSR to use an > Interest-Data based protocol. > > NFD RIB Management protocol contains "advertise" and "unadvertise" > commands that are probably related to this purpose. > > Yours, Junxiao > > On Aug 5, 2014 6:51 AM, "A K M Mahmudul Hoque (ahoque1)" > <firstname.lastname@example.org> wrote: > > - as option for launching the nlsr daemon they provide '-p' to > specify > > > the "port where api client will connect" (nlsr's usage output). I > looked > > > at the code, but I'm not able to find out if they've already > > > implemented/used this functionality. Could you please provide me > any > > > hint about its aim/meaning? > > > > > > --- It will be implemented in future. The aim of this one to tell > NLSR to advertise prefix, > > --- or even adding neighbors without taking down NLSR. Not only that > this API can be > > --- used to remove old prefixes link that are no longer valid. The > objective is to do those > > --- things without taking shutting down NLSR > _______________________________________________ Ndn-interest mailing list Ndnemail@example.com http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest