https://redmine.named-data.net/https://redmine.named-data.net/favicon.ico?14759811232014-08-06T09:38:22ZNDN project issue tracking systemNLSR - Task #1827: Clarify README and correct the usage message from NLSRhttps://redmine.named-data.net/issues/1827?journal_id=42232014-08-06T09:38:22ZSyed Amin
<ul></ul><p>Don't forget to add protoc-compiler in the steps of installing protoc. </p>
NLSR - Task #1827: Clarify README and correct the usage message from NLSRhttps://redmine.named-data.net/issues/1827?journal_id=42252014-08-06T09:55:12ZA K M Mahmudul Hoqueahoque1@memphis.edu
<ul></ul><p>Obaid,</p>
<p>Can you tell us how did you do in your machine? I mean install protoc</p>
NLSR - Task #1827: Clarify README and correct the usage message from NLSRhttps://redmine.named-data.net/issues/1827?journal_id=42272014-08-06T10:05:27ZSyed Amin
<ul></ul><p>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:</p>
<pre><code>sudo apt-get install libprotobuf-dev
</code></pre>
<p>to:</p>
<pre><code>sudo apt-get install libprotobuf-dev protobuf-compiler
</code></pre> NLSR - Task #1827: Clarify README and correct the usage message from NLSRhttps://redmine.named-data.net/issues/1827?journal_id=42282014-08-06T10:06:53ZA K M Mahmudul Hoqueahoque1@memphis.edu
<ul></ul><p>Okay thats great </p>
NLSR - Task #1827: Clarify README and correct the usage message from NLSRhttps://redmine.named-data.net/issues/1827?journal_id=42742014-08-10T07:01:19ZA K M Mahmudul Hoqueahoque1@memphis.edu
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Code review</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>90</i></li></ul><p>Here is the conversation of email to start this issue</p>
<blockquote>
<p>Hi Obaid,<br>
On Tue, 2014-08-05 at 11:45 -0500, Syed Obaid Amin wrote:<br>
Hi Salvatore,</p>
<p>Here is a brief history that maybe of interest to you. nlsr for ccnx<br>
can be controlled by CLI or remotely. It does so by listening on a<br>
port on which it accepts commands and process them. The '-p ' switch was introduced to change the default port on which it<br>
listens for this.<br><br>
thank you a lot for pointing this out, I will keep it in mind if I need<br>
this functionality.<br>
nlsr for nfd doesn't support this feature. The consensus was to use<br>
Interest/Data model for the communication between nfd and routing<br>
protocols(like nlsr). Plus, this functionality should be provided to<br>
all routing protocols (not just nlsr).<br>
That's on track and I'm agree with it.<br>
As a result, we added two new commands, advertise and withdraw in<br>
the RibManager, which will allow to specify the routing protocol for<br>
disseminating the name prefixes. However, these commands are not<br>
supported yet.</p>
<p>I hope that they will grow out soon. Thank you a lot for the history.<br>
Best,<br>
Salvo </p>
<p>Regards,<br>
Obaid</p>
<p>On Tue, Aug 5, 2014 at 9:43 AM, Salvatore Signorello<br>
<a href="mailto:unict.signorello@gmail.com">unict.signorello@gmail.com</a> wrote:<br>
Thank you both,</p>
<pre><code> 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)"
> <ahoque1@memphis.edu> 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
Ndn-interest@lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
</code></pre></blockquote>
NLSR - Task #1827: Clarify README and correct the usage message from NLSRhttps://redmine.named-data.net/issues/1827?journal_id=42872014-08-11T09:45:05ZA K M Mahmudul Hoqueahoque1@memphis.edu
<ul><li><strong>Status</strong> changed from <i>Code review</i> to <i>Closed</i></li></ul>