[Nfd-dev] Interests not forwarded

[Navdeep Uniyal]

Hi Junxiao,

Thank you for the reply, I have attached NFD Logs(Best-Route) and NDN Traffic Generator logs.
The nodes are connected via UDP faces. On analyzing the logs, I could see that after a certain point of time the interests are not forwarded. As visible from the NDN Traffic Server logs, till a certain point the interests are reaching the server and are being answered. As many interests are not reaching server, I doubt the forwarder is dropping most of them.

I am not very sure if the issue is with forwarder or NDN Traffic generator as logs does not show what exactly is happening with the interests which are not being forwarded. But the number of interests reaching the server is generally constant which is quite surprising for me.

Also, please suggest what minimum value should I keep for CS Store(Currently it is 1) so that most of the interests reaches server(For the sake of experiments).


Best Regards,
Navdeep Uniyal

From: Junxiao Shi [mailto:shijunxiao at email.arizona.edu]
Sent: Dienstag, 10. November 2015 19:07
To: Navdeep Uniyal; nfd-dev at lists.cs.ucla.edu
Subject: RE: [Nfd-dev] Interests not forwarded


Hi Navdeep



Can you attach the complete configuration files for NFD, traffic generator client, and traffic generator server, so others can attempt to reproduce the bug?

Are you running client and server on the same node? If not, how are the two nodes connected (Ethernet, or UDP, or TCP)?

How did you conclude the forwarder has stopped forwarding Interests after 800, instead of the producer has stopped responding Data, or the Data is being dropped? Did you reach this conclusion by ndndump or NFD logs?



Also,

1. “broadcast” strategy is deprecated and will be removed in next release. Use “multicast” strategy instead. See http://www.lists.cs.ucla.edu/pipermail/nfd-dev/2015-August/001281.html announcement.

2. Disabling ContentStore is not a supported scenario. It will break management until #2182 is implemented.



Yours, Junxiao



From: Navdeep Uniyal
Sent: Tuesday, November 10, 2015 06:41
To: nfd-dev at lists.cs.ucla.edu<mailto:nfd-dev at lists.cs.ucla.edu>
Subject: [Nfd-dev] Interests not forwarded


Hello everyone,

I am facing some issue on interest forwarding using NDN Traffic Generator. The forwarder in the client is only forwarding only initial 800(approx.) interests. I tried using broadcast as well as best-route strategies. In both the cases, after forwarding 800 odd interests, the forwarder is not sending out other interests to any of the face. I have increased the capacity of the links in order to verify the cause to be congestion but there is no improvement.

For my experiment, I am switching off CS Store( MAX_PACKETS = 1). The interest generation interval is 10 ms, NonceDuplicationPercentage = 0 and MustBeFresh Flag is set True. Even on varying the values and number of generated interests the forwarded interests number is observed to be the same. I could not find any error in the log. Please, any pointers could be helpful.



Best Regards,
Navdeep Uniyal



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20151111/a231bb01/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Best-Route.log
Type: application/octet-stream
Size: 7015668 bytes
Desc: Best-Route.log
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20151111/a231bb01/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NdnTrafficClient_BestFace.log
Type: application/octet-stream
Size: 448043 bytes
Desc: NdnTrafficClient_BestFace.log
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20151111/a231bb01/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NdnTrafficServer_BestFace.log
Type: application/octet-stream
Size: 92752 bytes
Desc: NdnTrafficServer_BestFace.log
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20151111/a231bb01/attachment-0002.obj>