From vslehman at memphis.edu  Tue Mar  1 07:58:40 2016
From: vslehman at memphis.edu (Vince Lehman (vslehman))
Date: Tue, 1 Mar 2016 15:58:40 +0000
Subject: [Mini-NDN] {Disarmed} Re: Consumer is not receiving the data
 (MiniNdn)
In-Reply-To: <CAOP2KvziEwk0WyBjc0o758UAUbSzkZiRzaDE2=GScbY77v7Msg@mail.gmail.com>
References: <CAOP2Kvx8a8e45vBuT6W5AmAAeMm_oSCkZjK3CoTVvSuLSx+ZLA@mail.gmail.com>
	<CAN32gn0bA_=j5A+b5Ag5mCSZGDGjaQYBQRQF5aZV0c_hQrUfgg@mail.gmail.com>
	<CAOP2KvziEwk0WyBjc0o758UAUbSzkZiRzaDE2=GScbY77v7Msg@mail.gmail.com>
Message-ID: <8E46BA03-C4F7-48B9-B653-454E92023914@memphis.edu>

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 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 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/20160301/8e567b7c/attachment.html>

From agawande at memphis.edu  Tue Mar  1 08:45:19 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Tue, 1 Mar 2016 16:45:19 +0000
Subject: [Mini-NDN] {Disarmed} Re: Consumer is not receiving the data
 (MiniNdn)
In-Reply-To: <8E46BA03-C4F7-48B9-B653-454E92023914@memphis.edu>
References: <CAOP2Kvx8a8e45vBuT6W5AmAAeMm_oSCkZjK3CoTVvSuLSx+ZLA@mail.gmail.com>
	<CAN32gn0bA_=j5A+b5Ag5mCSZGDGjaQYBQRQF5aZV0c_hQrUfgg@mail.gmail.com>
	<CAOP2KvziEwk0WyBjc0o758UAUbSzkZiRzaDE2=GScbY77v7Msg@mail.gmail.com>,
	<8E46BA03-C4F7-48B9-B653-454E92023914@memphis.edu>
Message-ID: <BY1PR0401MB1610466101FD02918BD84969D9BB0@BY1PR0401MB1610.namprd04.prod.outlook.com>

Just wanted to mention, even with using IP static routes might not work as there is no routing protocol on IP level (However, each node should be able to reach its neighbor using IP and the correct interface and there should be no problem in registering routes towards neighbor in NFD).


One needs to first install routes for IP (using the route command) and then install routes for NFD.

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Vince Lehman (vslehman) <vslehman at memphis.edu>
Sent: Tuesday, March 1, 2016 9:58 AM
To: Percy Perez Aruni
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] {Disarmed} Re: Consumer is not receiving the data (MiniNdn)

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 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 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/20160301/1b144316/attachment.html>

From pdpa at st-andrews.ac.uk  Tue Mar  1 16:56:37 2016
From: pdpa at st-andrews.ac.uk (Percy Perez Aruni)
Date: Wed, 2 Mar 2016 00:56:37 +0000
Subject: [Mini-NDN] {Disarmed} Re: {Disarmed} Re: Consumer is not
 receiving the data (MiniNdn)
In-Reply-To: <8E46BA03-C4F7-48B9-B653-454E92023914@memphis.edu>
References: <CAOP2Kvx8a8e45vBuT6W5AmAAeMm_oSCkZjK3CoTVvSuLSx+ZLA@mail.gmail.com>
	<CAN32gn0bA_=j5A+b5Ag5mCSZGDGjaQYBQRQF5aZV0c_hQrUfgg@mail.gmail.com>
	<CAOP2KvziEwk0WyBjc0o758UAUbSzkZiRzaDE2=GScbY77v7Msg@mail.gmail.com>
	<8E46BA03-C4F7-48B9-B653-454E92023914@memphis.edu>
Message-ID: <CAOP2Kvw0SwPzuuPPDmiYMjSF-LnWom8s4LCBU8NXRK0PgbC5Gg@mail.gmail.com>

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>
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 instead of IP addresses?
>       for example:
>                      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[?p?], ?/ndn/edu/store1?, dstNode)
>
> --
> Vince Lehman
>
> On Feb 29, 2016, at 6:25 PM, Percy Perez Aruni <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 instead of IP addresses?
>       for example:
>                      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>
> 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 == "p":
>>
>>
>>
>>  9                host.cmd("echo test1 | ndnpoke /ndn/edu/producer &")
>>
>>
>>
>> 10
>>
>>
>>
>> 11        for host in self.net.hosts:
>>
>>
>>
>> 12            if 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
>> > 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 == "p":
>>>               host.cmd("echo test1 | ndnpoke /ndn/edu/p &")
>>>         if 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
>>> 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/7a61e2a7/attachment.html>

From Navdeep.Uniyal at neclab.eu  Wed Mar  2 02:42:09 2016
From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal)
Date: Wed, 2 Mar 2016 10:42:09 +0000
Subject: [Mini-NDN] NLSR Error
In-Reply-To: <C9AD32D7-BF59-412B-B2D3-7DB74609E3DD@memphis.edu>
References: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd>
	<C9AD32D7-BF59-412B-B2D3-7DB74609E3DD@memphis.edu>
Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384DAFE@Hydra.office.hd>

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/mini-ndn/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/mini-ndn/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/mini-ndn/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/mini-ndn/attachments/20160302/91b13f6c/attachment-0002.obj>

From vslehman at memphis.edu  Wed Mar  2 07:01:05 2016
From: vslehman at memphis.edu (Vince Lehman (vslehman))
Date: Wed, 2 Mar 2016 15:01:05 +0000
Subject: [Mini-NDN] NLSR Error
In-Reply-To: <15421E67B274CD4AB5F6AEA46A684C370384DAFE@Hydra.office.hd>
References: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd>
	<C9AD32D7-BF59-412B-B2D3-7DB74609E3DD@memphis.edu>
	<15421E67B274CD4AB5F6AEA46A684C370384DAFE@Hydra.office.hd>
Message-ID: <455D46E2-5E72-4E6D-9BA7-335B1D37FEFF@memphis.edu>

Hi Navdeep,

Could you also attach the corresponding NLSR log file? Thanks.

--
Vince Lehman

On Mar 2, 2016, at 4:42 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>> wrote:

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<mailto:ndn-interest at lists.cs.ucla.edu>; mini-ndn at lists.cs.ucla.edu<mailto: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

<ga.log><ndn-traffic-server.conf><ndn-traffic-client.conf>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160302/d205e404/attachment.html>

From vslehman at memphis.edu  Wed Mar  2 07:06:13 2016
From: vslehman at memphis.edu (Vince Lehman (vslehman))
Date: Wed, 2 Mar 2016 15:06:13 +0000
Subject: [Mini-NDN] {Disarmed} Re: {Disarmed} Re: Consumer is not
 receiving the data (MiniNdn)
In-Reply-To: <CAOP2Kvw0SwPzuuPPDmiYMjSF-LnWom8s4LCBU8NXRK0PgbC5Gg@mail.gmail.com>
References: <CAOP2Kvx8a8e45vBuT6W5AmAAeMm_oSCkZjK3CoTVvSuLSx+ZLA@mail.gmail.com>
	<CAN32gn0bA_=j5A+b5Ag5mCSZGDGjaQYBQRQF5aZV0c_hQrUfgg@mail.gmail.com>
	<CAOP2KvziEwk0WyBjc0o758UAUbSzkZiRzaDE2=GScbY77v7Msg@mail.gmail.com>
	<8E46BA03-C4F7-48B9-B653-454E92023914@memphis.edu>
	<CAOP2Kvw0SwPzuuPPDmiYMjSF-LnWom8s4LCBU8NXRK0PgbC5Gg@mail.gmail.com>
Message-ID: <49913FF4-FEFE-43D7-9EF9-48C6A093334B@memphis.edu>

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>

From Navdeep.Uniyal at neclab.eu  Wed Mar  2 07:16:55 2016
From: Navdeep.Uniyal at neclab.eu (Navdeep Uniyal)
Date: Wed, 2 Mar 2016 15:16:55 +0000
Subject: [Mini-NDN] NLSR Error
In-Reply-To: <455D46E2-5E72-4E6D-9BA7-335B1D37FEFF@memphis.edu>
References: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd>
	<C9AD32D7-BF59-412B-B2D3-7DB74609E3DD@memphis.edu>
	<15421E67B274CD4AB5F6AEA46A684C370384DAFE@Hydra.office.hd>
	<455D46E2-5E72-4E6D-9BA7-335B1D37FEFF@memphis.edu>
Message-ID: <15421E67B274CD4AB5F6AEA46A684C370384FDD9@PALLENE.office.hd>

Hi Vince,

PFA the NLSR log file.

Regards,
Navdeep Uniyal

From: Vince Lehman (vslehman) [mailto:vslehman at memphis.edu]
Sent: Mittwoch, 2. M?rz 2016 16:01
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,

Could you also attach the corresponding NLSR log file? Thanks.

--
Vince Lehman

On Mar 2, 2016, at 4:42 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>> wrote:

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<mailto:ndn-interest at lists.cs.ucla.edu>; mini-ndn at lists.cs.ucla.edu<mailto: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

<ga.log><ndn-traffic-server.conf><ndn-traffic-client.conf>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160302/396fa039/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nlsr.log
Type: application/octet-stream
Size: 924612 bytes
Desc: nlsr.log
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160302/396fa039/attachment.obj>

From vslehman at memphis.edu  Wed Mar  2 07:29:38 2016
From: vslehman at memphis.edu (Vince Lehman (vslehman))
Date: Wed, 2 Mar 2016 15:29:38 +0000
Subject: [Mini-NDN] NLSR Error
In-Reply-To: <15421E67B274CD4AB5F6AEA46A684C370384FDD9@PALLENE.office.hd>
References: <15421E67B274CD4AB5F6AEA46A684C370384D9B1@Hydra.office.hd>
	<C9AD32D7-BF59-412B-B2D3-7DB74609E3DD@memphis.edu>
	<15421E67B274CD4AB5F6AEA46A684C370384DAFE@Hydra.office.hd>
	<455D46E2-5E72-4E6D-9BA7-335B1D37FEFF@memphis.edu>
	<15421E67B274CD4AB5F6AEA46A684C370384FDD9@PALLENE.office.hd>
Message-ID: <44E4BF3F-45B0-4059-ABC0-BB6AE0419927@memphis.edu>

Hi Navdeep,

It looks like the NFD log file was recorded on March 2, but all of the NLSR log messages in the attached file are from February 29. Do you have the NLSR log file for the same time period as the NFD log file?
--
Vince Lehman

On Mar 2, 2016, at 9:16 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>> wrote:

Hi Vince,

PFA the NLSR log file.

Regards,
Navdeep Uniyal

From: Vince Lehman (vslehman) [mailto:vslehman at memphis.edu]
Sent: Mittwoch, 2. M?rz 2016 16:01
To: Navdeep Uniyal
Cc: ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>; mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR Error

Hi Navdeep,

Could you also attach the corresponding NLSR log file? Thanks.

--
Vince Lehman

On Mar 2, 2016, at 4:42 AM, Navdeep Uniyal <Navdeep.Uniyal at neclab.eu<mailto:Navdeep.Uniyal at neclab.eu>> wrote:

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<mailto:ndn-interest at lists.cs.ucla.edu>; mini-ndn at lists.cs.ucla.edu<mailto: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

<ga.log><ndn-traffic-server.conf><ndn-traffic-client.conf>

<nlsr.log>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160302/97dee1b7/attachment.html>

From pdpa at st-andrews.ac.uk  Mon Mar  7 06:30:10 2016
From: pdpa at st-andrews.ac.uk (Percy Perez Aruni)
Date: Mon, 7 Mar 2016 14:30:10 +0000
Subject: [Mini-NDN] Set a strategy in MiniNdn
Message-ID: <CAOP2KvxDBB03wet8v8N7FYSqwZFRr+NV4snAsZaCfKapmtC83A@mail.gmail.com>

Hi dear MiniNdn team

Sorry for this email but would you mind to confirm if the proper way to set
a strategy in Minindn is by changing the  "strategy" argument  in
"mini-ndn/bin/minindn" (line ~375)?  and if MiniNdn supports all below
strategies?


.....
>      experimentArgs = {
>             "net": net,
>             "nodes": nodes,
>             "ctime": options.ctime,
>             "nPings": options.nPings,
>             "strategy": "client-control",
> #            "strategy": "multicast",
> #            "strategy": "ncc",
> #            "strategy": "broadcast",

#            "strategy": "access",
> #            "strategy": Nfd.STRATEGY_BEST_ROUTE_V3,
>             "pctTraffic": options.pctTraffic
>      } .....
>


Thank you in advance for your reply and comments.

Regards
Percy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160307/c3f580f1/attachment.html>

From vslehman at memphis.edu  Mon Mar  7 09:52:15 2016
From: vslehman at memphis.edu (Vince Lehman (vslehman))
Date: Mon, 7 Mar 2016 17:52:15 +0000
Subject: [Mini-NDN] Set a strategy in MiniNdn
In-Reply-To: <CAOP2KvxDBB03wet8v8N7FYSqwZFRr+NV4snAsZaCfKapmtC83A@mail.gmail.com>
References: <CAOP2KvxDBB03wet8v8N7FYSqwZFRr+NV4snAsZaCfKapmtC83A@mail.gmail.com>
Message-ID: <B884B4BE-6FCF-4C19-99A3-7866F5041709@memphis.edu>

Hi Percy,

Currently, the best way to set the strategy for a namespace in Mini-NDN is to use the setStrategy method in the Nfd class.

For example:

host.nfd.setStrategy(?/name/prefix?, ?strategy-name?)

where ?strategy-name? is one of the strategy strings you listed: (e.g., ?client-control?, ?multicast?, ?ncc?, etc.); and yes, all of the strategies supported by NFD are supported by Mini-NDN.

Changing the strategy option in experimentArgs will only set the specified strategy for the prefix ?/ndn/edu? when you run an experiment. If you want to set the strategy for any other prefix or while not running an experiment, you should use the setStrategy method.

--
Vince Lehman

On Mar 7, 2016, at 8:30 AM, Percy Perez Aruni <pdpa at st-andrews.ac.uk<mailto:pdpa at st-andrews.ac.uk>> wrote:

Hi dear MiniNdn team

Sorry for this email but would you mind to confirm if the proper way to set a strategy in Minindn is by changing the  "strategy" argument  in "mini-ndn/bin/minindn" (line ~375)?  and if MiniNdn supports all below strategies?


.....
     experimentArgs = {
            "net": net,
            "nodes": nodes,
            "ctime": options.ctime,
            "nPings": options.nPings,
            "strategy": "client-control",
#            "strategy": "multicast",
#            "strategy": "ncc",
#            "strategy": "broadcast",
#            "strategy": "access",
#            "strategy": Nfd.STRATEGY_BEST_ROUTE_V3,
            "pctTraffic": options.pctTraffic
     } .....


Thank you in advance for your reply and comments.

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/20160307/5b5c38ef/attachment.html>

From vslehman at memphis.edu  Mon Mar  7 12:20:55 2016
From: vslehman at memphis.edu (Vince Lehman (vslehman))
Date: Mon, 7 Mar 2016 20:20:55 +0000
Subject: [Mini-NDN] access to localhost
References: <mailman.52.1457377061.10425.mini-ndn@lists.cs.ucla.edu>
Message-ID: <0240158C-53B1-43BC-B96F-81F888350D61@memphis.edu>

Hi,

Do you mean you are unable to connect from the virtual network to the host machine that is running Mini-NDN? If so, you can follow the steps in https://github.com/named-data/mini-ndn/blob/master/docs/CONNECT-TO-OUTSIDE.md to set up a connection from a Mini-NDN node to the host machine.

--
Vince Lehman

Begin forwarded message:

From: <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>>
Subject: Auto-discard notification
Date: March 7, 2016 at 12:57:41 PM CST
To: <mini-ndn-owner at lists.cs.ucla.edu<mailto:mini-ndn-owner at lists.cs.ucla.edu>>

The attached message has been automatically discarded.
From: "El Mimouni, Omar Ilias (IntlAssoc)" <omarilias.elmimouni at nist.gov<mailto:omarilias.elmimouni at nist.gov>>
Subject: access to localhost
Date: March 7, 2016 at 12:57:31 PM CST
To: "mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>" <mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>>


Hi all,
I can?t access to the localhost from a mini-ndn host.
I am running mini-ndn in Ubuntu from a VirtualBox machine.

By the way, I am using xampp as a web server.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160307/91f6dc03/attachment.html>

From pdpa at st-andrews.ac.uk  Thu Mar 10 15:41:17 2016
From: pdpa at st-andrews.ac.uk (Percy Perez Aruni)
Date: Thu, 10 Mar 2016 23:41:17 +0000
Subject: [Mini-NDN] How to read/decode Minindn logs
Message-ID: <CAOP2Kvx0oXvDZ_i3H6=9o1wEvBAY0Yo=1=gg48CR-rjC08ADpQ@mail.gmail.com>

Hi MiniNdn team

Would you mind pointing me to some documentation/API/tool  that could help
me to decode/read  the hexadecimal logs that are generated by experiments
in MiniNdn ?
I am referring to the "hostname".log for NFD  and the log/nlsr.log for NLSR
(below two samples for your reference)

Thank you in advance for your advice.

Regards
Percy

PS  Here two examples for your reference :

For NFD
1457640049.463597 DEBUG: [Forwarder] onOutgoingInterest face=256
interest=/localhost/nfd/rib/register/h
%16%07%11%08%09localhost%08%04nlsrl%01%01/%00%00%01Sb%1E%0B%02/%88%82%7B%E3%EB%91_%E5/%16%3C%1B%01%01%1C7%075%08%0Ctmp-identity%08%04%12%B1%60%5C%08%03KEY%08%11ksk-1457640036842%08%07ID-CERT/%17%FD%01%00%7F%00%A8%FCG%E2%17%04%23%DEf%3D%0B%96%0C0%9B%1E%8B%F1%1D%C3%D1l%7D%40%8E%02eP%DA%14%5C%04b%A6%20%5CN%CE%0BI%EA%F1%96%B6%EB%C4%A1%CE%06I%B3qZ%C1%18%5E%0F%FA%9E%F0%B5-%DA%FC%BA%ABZ_%ECP%BF%BA9%CC%26%98%8B%C4%B7%CA%81%89S%A6%D9qh%07%0Au%96%19%21%14%A0%7D%BBZ%D9%3Fy%03%F7%8B%E0%26%21_%87%10%D4%12s%D6aw%02%F9%80%23%DB%1E.%0A%BB%EF%14%83g%F2%03%CB%2C%D1Q%B3%AF%8C%90%BBl%1E%9E%27%92%81%2A%A6C%D1%E9%22%40u%A6%AB%C5%2A%8B%CEK%BE%8C%BC%82%E1m%C6%A0%83%A70o%F8%C54%9Dl%CB%24%1F%2FU%18%F5B%BA%7C%EDBf%23%B5%D6%C1H%8D%CB3%03%1A%F4%FE%3C%ADQ%8B%F6g%E8%CC%A6%B4%01%22nJ%8E%DE%0E%98r%1C%C2r%D0Q%F2%12%A1%0A%DF%E4Dj%BA%E9g%1AN%94%F1b%F7C%13%EC%9A%05%C9A%7D%FD%0B

For NLSR
20160310200105241 DEBUG: [SyncLogic] sendSyncInterest: /ndn/NLSR/sync/
d8589e0f69552d1a1e42dbc55d648b8893c53818ec0406ef6d0bb958e9f9858c
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160310/7337c31e/attachment.html>