[Mini-NDN] How to restart of ndn services in mini-ndn

[Ashlesh Gawande (agawande)]

Mini-NDN first starts NFD, then NLSR, and then runs the experiment pingall. In the pingall experiment you can start tcpdump before startPctPings:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/nlsr/pingall_experiment.py

(An example for ndndump startup is here: https://redmine.named-data.net/issues/4436#note-1)

If you want to start tcpdump before NFD is started then put the code in bin/minindn before NFD is started.

Also, once the experiment has finished you cannot invoke the convergence again from the command line. You can manually check whether they have converged similar to how it is done in https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py

Ashlesh

On 1/3/19 6:55 AM, knet solutions wrote:
Hi,

When i run the default-configuration,  its converged and pings fine.

"sudo minindn --experiment=pingall --nPings=50"

But I want to capture the network packets . so i stopped (killed the nfd and nlsr process on all nodes) and started the tcpdump capture on the nodes.

Again, i started the nfd and nlsr process as below on all nodes,

Example:
mini-ndn> a nfd --config /tmp/minindn/a/nfd.conf &
mini-ndn> a nlsr -f /tmp/minindn/a/nlsr.conf &

The process are running fine.

But Nodes are  not synchronizing/converging..

Am i missing some steps?

Note: I have not touched the configuration file.

Thanks
suresh








--
Regards,
Knet solutions.
Whatsapp/Mobile:  +919445042007
website:  http://knetsolutions.in/
Facebook Page :   https://www.facebook.com/sdntraining/
youtube channel:  https://www.youtube.com/channel/UCTD6X9_oDqIYs_xpE7moFnQ





_______________________________________________
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/mini-ndn/attachments/20190103/94ed48e3/attachment-0001.html>