[Mini-NDN] max packets satisfied by consumer?

[Ashlesh Gawande (agawande)]

I don't think it has to do with the ndnpingserver code (https://github.com/named-data/ndn-tools/tree/master/tools/ping) or NFD forwarder code.

It most probably has to do with mininet pseudo shell (cmd).


Ashlesh

________________________________
From: Aman Maldar <amanmaldar at gmail.com>
Sent: Thursday, December 21, 2017 7:29:13 PM
To: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] max packets satisfied by consumer?

Ashlesh,
Thanks for the response.

It works your way,but not sure why it is not working without redirecting logs for ndnpingserver.
I am trying dig into function which handles incoming interest and responds to data.

Where can I find following scenario implementation for ndnpingserver in codebase (same scenario as asked in previous mail)? I checked mini-ndn/NFD/daemons/fw/forwarder.cpp

content from /ndn/b-site/b: seq=700 time=22.2604 ms
content from /ndn/b-site/b: seq=701 time=21.6291 ms
content from /ndn/b-site/b: seq=702 time=22.3644 ms
content from /ndn/b-site/b: seq=703 time=21.6401 ms
timeout from /ndn/b-site/b: seq=704
timeout from /ndn/b-site/b: seq=705
timeout from /ndn/b-site/b: seq=706
timeout from /ndn/b-site/b: seq=707

Thanks.


On Thu, Dec 21, 2017 at 3:36 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Okay so I tried your first two commands and got timeout after seq 1654.

I restarted mini-ndn and tried to diagnose it by redirecting ping server logs:

mini-ndn> b ndnpingserver /ndn/b-site/b -x 1000000 &> ping-server &


After which I did not get the problem. Can you try this and check?


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Aman Maldar <amanmaldar at gmail.com<mailto:amanmaldar at gmail.com>>
Sent: Thursday, December 21, 2017 1:19:10 PM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] max packets satisfied by consumer?

Greetings Everyone,

I am doing following in mini-ndn

sudo minindn
mini-ndn> b ndnpingserver /ndn/b-site/b -x 1000000 &
mini-ndn> a ndnping /ndn/b-site/b -i 100 -c 1000 -n 1001

I am trying to send 1000 interest packets. The freshness is about 6 minutes for data packets.
So I all replied data packets will be cashed at Content store A for long time.

Once all the interests are satisfied, I will execute following again.
mini-ndn> a ndnping /ndn/b-site/b -i 100 -c 1000 -n 1001

I should see all the packets getting satisfied at CS-A. It works for limited number of packets.

The problem is,

The above experiment works well for n=600 packets.
After 680 packets I am getting error as

timeout from /ndn/b-site/b: seq=681
timeout from /ndn/b-site/b: seq=682
timeout from /ndn/b-site/b: seq=683
...
and so on.


I tried changing cs_max_packets to large values like 300000 in nfd.conf file. Makes very less difference to extra packets getting satisfied.
ndndump shows node B is receiving packets but , not replying to interests. - this is  main problem.
As I missing something? Any memory issues or max requests?

Thanks in advance.

--
Regards,
Mr. Maldar Aman M.
University of Massachusetts, Lowell



--
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/20171222/16fe702a/attachment-0001.html>