[Ndn-interest] [Mini-NDN] NLSR Error

Navdeep Uniyal Navdeep.Uniyal at neclab.eu
Wed Mar 2 02:42:09 PST 2016


Hi Vince,

Thank you for your reply. I saw the NFD logs(attached) and could not find any point where NFD is failing. But surprisingly, I could see that there is less number of interests that are forwarded even in the case they are not satisfied with the cache. I am using NDN Traffic generator to create the traffic in the network. Any pointer would be helpful. I am using a simple topology:


Client1-->Client2-->Server (There are 3 paths from Client2 to server) Attached is the traffic generator client and server configuration. Please help.


Thanks and Regards,
Navdeep Uniyal

From: Vince Lehman (vslehman) [mailto:vslehman at memphis.edu]
Sent: Montag, 29. Februar 2016 16:48
To: Navdeep Uniyal
Cc: ndn-interest at lists.cs.ucla.edu; mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR Error

Hi Navdeep,

This error is usually caused by the NFD process on the node terminating; NLSR is unable to receive data from NFD’s Unix socket.

Can you check or share NFD’s log to see the reason for the process’ termination? It could be something wrong with the configuration or if you are using ctl^c to kill a process on the Mini-NDN command-line, this can sometimes kill NFD processes also.

--
Vince Lehman

On Feb 29, 2016, at 7:52 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>> wrote:

Hi everyone,

I am using minindn to run my experiments, I am finding few errors in the NLSR log. Due to which packet loss is occurring. Below is the snippet of the error and attached is the log file. Please if someone can help resolving the issue.

20160229054020045 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb
20160229054020045 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hb
20160229054020049 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hb
20160229054020533 DEBUG: [HelloProtocol] Interest Received for Name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc
20160229054020533 DEBUG: [HelloProtocol] Neighbor: /ndn/edu/%C1.Router/cs/hc
20160229054020535 DEBUG: [HelloProtocol] Sending out data for name: /ndn/edu/%C1.Router/cs/ga/NLSR/INFO/%07%1C%08%03ndn%08%03edu%08%08%C1.Router%08%02cs%08%02hc
20160229054111562 FATAL: [Main] ERROR: error while receiving data from socket (End of file)
20160229054111562 DEBUG: [Fib] Fib::clean called




Regards,
Navdeep Uniyal
<nlsr.log>_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160302/91b13f6c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ga.log
Type: application/octet-stream
Size: 1791955 bytes
Desc: ga.log
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160302/91b13f6c/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ndn-traffic-server.conf
Type: application/octet-stream
Size: 1570 bytes
Desc: ndn-traffic-server.conf
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160302/91b13f6c/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ndn-traffic-client.conf
Type: application/octet-stream
Size: 1710 bytes
Desc: ndn-traffic-client.conf
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20160302/91b13f6c/attachment-0002.obj>


More information about the Ndn-interest mailing list