[Mini-NDN] Not getting HIT scenario on CS for multiple interests with same name.

[Ashlesh Gawande (agawande)]

You need to set the data freshness and interest lifetime in your code.

For ndnpingserver you can set freshness using -x (see ndnpingserver -h).

For ndnping set the timeout for interest lifetime (ndnping -h).


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Aman Maldar <amanmaldar at gmail.com>
Sent: Friday, November 24, 2017 5:09:27 PM
To: Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Not getting HIT scenario on CS for multiple interests with same name.

Thanks you Junxiao,
That is correct. Though  I have a really silly question regarding the correct syntax.
I am trying to override default value for freshness. I spent good amount of time figuring this out, but no luck.
I am getting search results for ndnSim, but not for mini-ndn.
I made changes in /usr/local/etc/ndn/nfd.conf file

Is this the way I write it? Additionally , how do I set interestLifetime as well?


; The tables section configures the CS, PIT, FIB, Strategy Choice, and Measurements tables
{
  ; ContentStore size limit in number of packets
  ; default is 65536, about 500MB with 8KB packet size
  cs_max_packets 65000
  //FreshnessPeriod 10000mS     //WHAT is correct syntax?
  //FreshnessPeriod=11000mS

I am new to mini-ndn. I appreciate your time and help.


On Fri, Nov 24, 2017 at 9:35 AM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:
Hi Aman

I am trying to see if I request 2 interest packets with the same name back to back, the second interest should be satisfied at the requesting node itself.
Yes, but only if the cached Data satisfies the Interest selectors.

Steps followed :
> sudo minindn
mini-ndn> d ndnpingserver /ndn/d-site/d &
mini-ndn> a ndnping /ndn/d-site/d -c1 -n 55555
ndnpingserver is invoked with default settings: FreshnessPeriod of the Data packet is 1000ms.

host A get the contents back . with RTT 45ms apprx.
cs::Insert() adds the content to the CS.
According to screenshot, this occurs at 1511480463.948688.


Now I immediately execute the same request again, keeping sequence number same.
 mini-ndn> a ndnpin /ndn/d-site/d -c1 -n 55555
 ndnping is invoked with default settings: Interest carries MustBeFresh selector.

Now I see in Content store log, the cs::Find() does not finds entry in CS. (I believe it should be already there)
The cached Data has become stale at 1511480464.948688. When processing the Interest at 1511480467.711965, the Data does not satisfy the Interest because it violates MustBeFresh selector. Hence, the CS rightfully returns "no-match".

The packet goes all the way to host D, and again when data packet is returned to host A, cs::insert() is called on host A.

Expected outcome.
second interest should be satisfied by cs::Find() at host A itself with very small RTT.

Attaching log screenshot.

[Inline image 1]
Next time paste the log as text, not screenshot or attachment.


Any idea if I am doing something wrong? Thank you in advance.


Yours, Junxiao



--
Regards,
Mr. Maldar Aman M.
University of Massachusetts, Lowell
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20171127/7af448a9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 215305 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20171127/7af448a9/attachment-0001.png>