<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div id="appendonsend" style="font-family: Calibri, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> André D. Carneiro <adcarneiro@inf.ufrgs.br><br>
<b>Sent:</b> Sunday, September 20, 2020 6:30 PM<br>
<b>To:</b> Saurab Dulal (sdulal) <sdulal@memphis.edu><br>
<b>Subject:</b> Re: [Mini-NDN] Issues installing MiniNDN</font>
<div> </div>
</div>
<div>
<p style="margin-top: 0px; margin-bottom: 0px;">Thanks very much for your help, indeed my installation was fine. I was not advertising the producer's prefix, I was just using the producer and consumer from the examples folder, slightly modified to capture transmission
times and set interest filters from the command line so I could use them from within the python script (ex. `<tt>host.cmd('producer /a')</tt>`).</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">Running a few tests now I noticed that when I advertise the producer's prefix, run a producer and a consumer with that same interest filter, then the data is cached. So that the next time the same consumer runs,
the data is received with a much lower delay. However, if I advertise that same prefix (say `<tt>a nlsrc advertise /a</tt>`) and run a consumer with an interest filter such as `<tt>/a/data0</tt>`, the data is transmitted and received but not cached, as can
be seen by the delay which stays at around the same value, about 20ms.</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<div style="margin-top: 0px; margin-bottom: 0px;"><span style="color: rgb(0, 0, 0); font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, system-ui, Roboto, "Helvetica Neue", sans-serif; font-size: 15px; background-color: rgb(255, 255, 255); display: inline !important">-
I don't know if I understand this fully. AFAIK the data should be cached even if your interest filter is on "/a/data0". I did some testing and saw the data cached in both the cases. I assume you are only setting interest filters at the producer's node and
not on the consumer? Regarding the caching, and the intermediate node will cache a copy of the data packet for a certain period based on the caching policy. </span><br>
</div>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">Does this mean that every interest filter used by a consumer must be advertised using `<tt>nlsrc advertise</tt>` by the producer so it can be cached by other hosts/routers in the topology?<br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<div style="margin-top: 0px; margin-bottom: 0px;"><span style="color: rgb(0, 0, 0); font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, system-ui, Roboto, "Helvetica Neue", sans-serif; font-size: 15px; background-color: rgb(255, 255, 255); display: inline !important">- </span><span style="margin: 0px; font-size: 14px; font-family: monospace; color: black; background-color: white">nlsrc
advertise<span> </span></span><span style="margin: 0px; font-size: 12pt; font-family: "Segoe UI", "Segoe UI Web (West European)", "Segoe UI", -apple-system, system-ui, Roboto, "Helvetica Neue", sans-serif; background-color: white">means every other node in
the network will create routes towards that prefix. If the prefix (say /a) is not advertised (or the routes are not established by any other means), none of the interest sent under that name (e.g. interest: /a) will reach the producer or will be forwarded
(consumer will receive NoRoute Nack). Regarding the caching, if data comes back, by any means, it will be cached in the intermediate nodes regardless of interest filter unless it's unsolicited. </span><br>
</div>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"></p>
<div>- Saurab </div>
<p></p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;">Regards,</p>
<p style="margin-top: 0px; margin-bottom: 0px;">André Dexheimer Carneiro<br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<p style="margin-top: 0px; margin-bottom: 0px;"><br>
</p>
<div class="x_moz-cite-prefix">On 20/09/2020 15:57, Saurab Dulal (sdulal) wrote:<br>
</div>
<blockquote type="cite">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Mini-NDN
<a class="x_moz-txt-link-rfc2396E" href="mailto:mini-ndn-bounces@lists.cs.ucla.edu">
<mini-ndn-bounces@lists.cs.ucla.edu></a> on behalf of Lan Wang (lanwang) <a class="x_moz-txt-link-rfc2396E" href="mailto:lanwang@memphis.edu">
<lanwang@memphis.edu></a><br>
<b>Sent:</b> Saturday, September 19, 2020 6:27 PM<br>
<b>To:</b> Ritu Bordoloi via Mini-NDN <a class="x_moz-txt-link-rfc2396E" href="mailto:mini-ndn@lists.cs.ucla.edu">
<mini-ndn@lists.cs.ucla.edu></a><br>
<b>Subject:</b> [Mini-NDN] Issues installing MiniNDN</font>
<div> </div>
</div>
<div class="" style="word-wrap:break-word; line-break:after-white-space"><br class="">
<div>
<blockquote type="cite" class="">
<div class="">
<div class="" style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span class="" style="color:rgba(127,127,127,1.0)"><b class="">From: </b></span><span class="" style="">André D. Carneiro <<a href="mailto:adcarneiro@inf.ufrgs.br" class="">adcarneiro@inf.ufrgs.br</a>><br class="">
</span></div>
<div class="" style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span class="" style="color:rgba(127,127,127,1.0)"><b class="">Subject: </b></span><span class="" style=""><b class="">Issues installing MiniNDN</b><br class="">
</span></div>
<div class="" style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span class="" style="color:rgba(127,127,127,1.0)"><b class="">Date: </b></span><span class="" style="">September 19, 2020 at 4:34:30 PM CDT<br class="">
</span></div>
<div class="" style="margin-top:0px; margin-right:0px; margin-bottom:0px; margin-left:0px">
<span class="" style="color:rgba(127,127,127,1.0)"><b class="">To: </b></span><span class="" style=""><a href="mailto:mini-ndn@lists.cs.ucla.edu" class="">mini-ndn@lists.cs.ucla.edu</a>.<br class="">
</span></div>
<br class="">
<br class="">
Hi all,<br class="">
<br class="">
I'm having trouble getting MiniNDN up and running. I figured the easiest way to install is by using the vagrantfile. So I cloned the repo for named-data/mini-ndn and ran `vagrant up` inside it, which created the virtual machine in VirtualBox. I then proceeded
to install miniNDN inside it via `sudo ./install.sh -a`, which downloaded and compiled everything successfully.<br class="">
<br class="">
The first thing I noticed is that it did not create a `minindn` symbolic link, which is not a real problem for me because running the python scripts inside the examples folder still starts minindn and lets me in to the mini-ndn> CLI. Just thought is was curious.<br class="">
</div>
</blockquote>
<div class="">Mini-NDN is not installed in the system anymore, so the minindn command doesn't exist. For more details please see the latest release notes: <a href="http://minindn.memphis.edu/release-notes.html#mini-ndn-version-0-5-0-major-changes-since-version-0-4-0" id="LPlnk570568">http://minindn.memphis.edu/release-notes.html#mini-ndn-version-0-5-0-major-changes-since-version-0-4-0</a></div>
<div class=""><br>
</div>
<blockquote type="cite" class="">
<div class="">Anyway, the real problem is that when I run `sudo python examples/mnndn.py`, everything starts and I get in to the CLI. But then, running pingall results in the following<br class="">
<br class="">
mini-ndn> pingall<br class="">
*** Ping: testing ping reachability<br class="">
a -> b c X<br class="">
b -> a X d<br class="">
c -> X X X<br class="">
d -> X X X<br class="">
</div>
<div class=""> *** Results: 66% dropped (4/12 received)</div>
</blockquote>
<div class="">This is completely fine, not a problem at all for ndn related stuff.</div>
<div class=""><br>
</div>
<div class="">Quote from the previous email (Custom experiments in MiniNDN, Sending data, Error: No default identity): </div>
<div class="">
<blockquote class="x_quotableTextTraining" style="border-left:3px solid rgb(200,200,200); border-top-color:rgb(200,200,200); border-right-color:rgb(200,200,200); border-bottom-color:rgb(200,200,200); padding-left:1ex; margin-left:0.8ex; color:rgb(102,102,102)">
<div dir="ltr" style="">
<div style="margin:0px">- For every link, minindn creates a veth pair, meaning a-c is different than c-a. So, if you have a-c link in the topology, you can do<span> </span><b>a ping c</b><span> </span>but not the other way around.<br>
</div>
<div style="margin:0px"><br>
</div>
</div>
<div dir="ltr" style=""><b>More important info: </b></div>
<div dir="ltr" style=""><a href="https://redmine.named-data.net/issues/3054" target="_blank" rel="noopener noreferrer" style="margin:0px">https://redmine.named-data.net/issues/3054</a></div>
<div dir="ltr" style=""><a href="https://redmine.named-data.net/issues/4069" target="_blank" rel="noopener noreferrer" style="margin:0px">https://redmine.named-data.net/issues/4069</a></div>
</blockquote>
<div dir="ltr" style="">This means for the given default topology; every node won't be able to ping every other node and that's why we observer 66% dropped. </div>
</div>
<blockquote type="cite" class="">
<div class="">And after I run `sudo python examples/nlsr/pingall.py`, exit the CLI and run `grep -c content /tmp/minindn/*/ping-data/*.txt`, as stated in the documentation, I get the following:<br class="">
</div>
<div class=""><br class="">
/tmp/minindn/a/ping-data/b.txt:300<br class="">
/tmp/minindn/a/ping-data/c.txt:300<br class="">
/tmp/minindn/a/ping-data/d.txt:300<br class="">
/tmp/minindn/b/ping-data/a.txt:300<br class="">
/tmp/minindn/b/ping-data/c.txt:300<br class="">
/tmp/minindn/b/ping-data/d.txt:300<br class="">
/tmp/minindn/c/ping-data/a.txt:300<br class="">
/tmp/minindn/c/ping-data/b.txt:300<br class="">
/tmp/minindn/c/ping-data/d.txt:300<br class="">
/tmp/minindn/d/ping-data/a.txt:300<br class="">
/tmp/minindn/d/ping-data/b.txt:300<br class="">
/tmp/minindn/d/ping-data/c.txt:300<br class="">
<br class="">
As oposed to the count of 50 that should be reported for each file.<br class="">
</div>
</blockquote>
<div class="">I don't understand why you expect 50. The default value for nPings (see nlsr_common.py) is 300, meaning each node will ping (ndnping) each other node 300 times and that's the number you are seeing it there. Unless you have different settings,
the above result looks good to me.</div>
<div class=""><br>
</div>
<blockquote type="cite" class="">
<div class="">Running `grep -c timeout /tmp/minindn/*/ping-data/*.txt` yields the apparently correct result of 0 for each file.<br class="">
<br class="">
Note that I have already tried this same process on two different linux machines here. Having the same results.<br class="">
<br class="">
I believe these problems are the cause for another error that I'm having in my experiments, where I get NACK for every consumer when trying to run a simple producer/consumer scenario.<br class="">
</div>
</blockquote>
<div class="">Can you please provide more detail on this? Are you getting no-route Nack? if so, have you advertised your producer's prefix using nlsrc advertise command? or have set up the routes to the producer's prefix in any other way? For example, if a
producer (say <b>"b"</b>) is serving data for '<b>/example' </b>prefix, you need to advertise it from node <b>"b"
</b>(b nlsrc advertise /example). After the advertisement, <span style="">with the help of NLSR, </span>every other node will be able to reach this prefix and so you won't observe any no-route nack. </div>
<div class=""><br>
</div>
<blockquote type="cite" class="">
<div class="">Also, the documentation I refer to is this one: <a href="http://minindn.memphis.edu/install.html#using-install-sh" class="">
http://minindn.memphis.edu/install.html#using-install-sh</a><br class="">
<br class="">
<br class="">
Best regards,<br class="">
André Dexheimer Carneiro<br class="">
</div>
</blockquote>
<div class=""><br>
</div>
</div>
<div class="">Lastly, your Mini-NDN installation looks good to me.</div>
<div class=""><br>
</div>
<div class="">Let us know if you are facing more issues.</div>
<div class=""><br>
</div>
<div class="">Regards,</div>
<div class="">Saurab Dulal</div>
<br class="">
</div>
<br>
<fieldset class="x_mimeAttachmentHeader"></fieldset>
<pre class="x_moz-quote-pre">_______________________________________________
Mini-NDN mailing list
<a class="x_moz-txt-link-abbreviated" href="mailto:Mini-NDN@lists.cs.ucla.edu">Mini-NDN@lists.cs.ucla.edu</a>
<a class="x_moz-txt-link-freetext" href="http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn">http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn</a>
</pre>
</blockquote>
</div>
</body>
</html>