[Mini-NDN] {Disarmed} Re: {Disarmed} Re: Consumer is not receiving the data (MiniNdn)
Vince Lehman (vslehman)
vslehman at memphis.edu
Wed Mar 2 07:06:13 PST 2016
Is there some available parser for these logs in MiniNdn ? (for example for NFD and/or NLSR logs).
Or
How would you recommend to read them ?.
There are no tools included with Mini-NDN to help parse the log files, but if you want to know when a face receives an Interest or Data packet, the NFD log files can be searched for the keywords onIncomingInterest or onIncomingData. The log line will include the timestamp, the receiving face, and the Interest/Data name.
e.g.)
1456913149.237331 DEBUG: [Forwarder] onIncomingInterest face=257 interest=/localhost/nfd/faces/events/%FE%06
1456913134.562870 DEBUG: [Forwarder] onIncomingData face=1 data=/localhost/nfd/faces/events/%FE%00
--
Vince Lehman
On Mar 1, 2016, at 6:56 PM, Percy Perez Aruni <pdpa at st-andrews.ac.uk<mailto:pdpa at st-andrews.ac.uk>> wrote:
Hi Vince
Thank you so much for the details.
>>>a: _ nfd-log-level=DEBUG
>>>The log will be written to the node’s home folder (by default, /tmp/$NODE_NAME).
Is there some available parser for these logs in MiniNdn ? (for example for NFD and/or NLSR logs).
Or
How would you recommend to read them ?.
Regards
Percy
On 1 March 2016 at 15:58, Vince Lehman (vslehman) <vslehman at memphis.edu<mailto:vslehman at memphis.edu>> wrote:
1.- How can I use MiniNdn to collect data traffic for each and between nodes?
For example, I would like to collect data traffic for the forwarder, like which face has received the interest or data and when?
If you would like to log forwarder information on a node, you can add an additional parameter to its definition in the topology configuration file:
[nodes]
a: _ nfd-log-level=DEBUG
...
The log will be written to the node’s home folder (by default, /tmp/$NODE_NAME).
2.- To register static routes from a ExperimentClass, could MiniNdn use the host.name<http://host.name/> instead of IP addresses?
for example:
self.net<http://self.net/>['p'].cmd("nfdc register /ndn/edu/store1 tcp://MailScanner has detected a possible fraud attempt from "1.0.0.3:6363" claiming to be MailScanner warning: numerical links are often malicious: 1.0.0.3:6363<http://1.0.0.3:6363/> &")
In the current version of Mini-NDN, using the IP address is the standard way to achieve static routes. In the future, we would like to provide a static routing helper that would allow a user to call something like:
Nfdc.register(self.net<http://self.net/>[‘p’], “/ndn/edu/store1”, dstNode)
--
Vince Lehman
On Feb 29, 2016, at 6:25 PM, Percy Perez Aruni <pdpa at st-andrews.ac.uk<mailto:pdpa at st-andrews.ac.uk>> wrote:
Hi dear Shuo and Vince
Thank you both for replying my last email.
I just re-installed minindn (./install.sh -mrfti) and the script is working now. Unfortunately I can not explain why this was necessary.
Regarding your comments:
>>> Is the script you included your entire experiment script? If not, could you please attach the full code?
Yes, it is the entire script.
If you do not mind, could I ask the following please:
1.- How can I use MiniNdn to collect data traffic for each and between nodes?
For example, I would like to collect data traffic for the forwarder, like which face has received the interest or data and when?
2.- To register static routes from a ExperimentClass, could MiniNdn use the host.name<http://host.name/> instead of IP addresses?
for example:
self.net<http://self.net/>['p'].cmd("nfdc register /ndn/edu/store1 tcp://MailScanner has detected a possible fraud attempt from "1.0.0.3:6363" claiming to be MailScanner warning: numerical links are often malicious: 1.0.0.3:6363<http://1.0.0.3:6363/> &")
Thank you again for your comments.
Regards
Percy
On 29 February 2016 at 04:46, Shuo Yang <shuoyang at email.arizona.edu<mailto:shuoyang at email.arizona.edu>> wrote:
Hi Percy,
It seems that you should write the script in this way:
1from ndn.experiments.experiment import Experiment
2
3class Experiment1(Experiment):
4 def __init__(self,args):
5 Experiment.__init__(self, args)
6 def run(self):
7 for host in self.net.hosts:
8 if host.name<http://host.name/> == "p":
9 host.cmd("echo test1 | ndnpoke /ndn/edu/producer &")
10
11 for host in self.net.hosts:
12 if host.name<http://host.name/> == "c":
13 print host.cmd("ndnpeek -p /ndn/edu/producer")
14
15Experiment.register("peek-poke", Experiment1)
At least yours is working on my side. I'm using Mini-ndn 0.1.1
Best luck!
Shuo
On Sun, Feb 28, 2016 at 5:09 PM, Percy Perez Aruni <pdpa at st-andrews.ac.uk<mailto:pdpa at st-andrews.ac.uk>> wrote:
Hi dear MiniNdn team
I am interested in using MiniNdn for an initial basic experiment between three nodes: a consumer , a forwarder and a producer. It is highly possible that I am missing something, but the consumer is not receiving the data from the producer.
Could I ask for some advice of how this could be achieved by using MiniNdn?
Some details below:
1.- Topology: c <-> f <-> p
where c = consumer, f = forwarder, p =producer
2.- ExperimentClass:
from ndn.experiments.experiment import Experiment
class Experiment1(Experiment):
def __init__(self,args):
Experiment.__init__(self, args)
def run(self):
if host.name<http://host.name/> == "p":
host.cmd("echo test1 | ndnpoke /ndn/edu/p &")
if host.name<http://host.name/> == "c":
print host.cmd("ndnpeek -p /ndn/edu/p")
Experiment.register("peek-poke", Experiment1)
3.- Running as root:
#./install.sh -i; minindn --experiment=peek-poke --ctime=20 ndn_utils/topologies/three-nodes.conf
4.- "NLSR has successfully converged"
Thank you in advance for your time and help
Regards
Percy
_______________________________________________
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/20160302/a01f6bfb/attachment.html>
More information about the Mini-NDN
mailing list