From rajendrj at tcd.ie  Mon Jun  6 09:09:25 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Mon, 6 Jun 2016 17:09:25 +0100
Subject: [Mini-NDN] Controller implementation in mini-ndn : Request for
 advice
Message-ID: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>

Hi All,

Greetings!

This is Jeeva Rajendran from Trinity College Dublin, Ireland. I am pursuing
my master degree in computer science.

As part of my research, I am trying to use 'Mini-ndn' to execute and
evaluate my network experiments.

>From Mini-ndn GitHub repository, I learned that Mini-ndn is based on
'Mini-ccnx' and forked from 'Mininet'. When I was going through the code of
mininet, mini-ccnx and mini-ndn, I noticed that the coding related to
'Controller' is removed in mini-ndn (I could see controller implementation
in mini-ccnx in conf_parser, miniccnxedit, miniccnx script and other files)

Is there a specific reason why controller implementation is not a part of
mini-ndn and is there a future plan to include it in mini-ndn?

Please help with the information.

Thanks in advance

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

From agawande at memphis.edu  Mon Jun  6 09:46:51 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 6 Jun 2016 16:46:51 +0000
Subject: [Mini-NDN] Controller implementation in mini-ndn : Request for
 advice
In-Reply-To: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>
References: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>
Message-ID: <BN3PR04MB21966598BE28C8FC5D9968B3D95C0@BN3PR04MB2196.namprd04.prod.outlook.com>

I cannot remember any particular reason as to why we removed it. I guess we just didn't have any use for it and might have skipped it.

There are no plans to include it any time soon. But if you have need for it and would like to contribute and include it (I think it is not a big change) we would be happy to accept it.

You can file an issue here:

http://redmine.named-data.net/projects/mini-ndn/issues


And when you are ready you can push your changes to gerrit.named-data.net

Some information on gerrit and git is given here:

http://redmine.named-data.net/projects/nfd/wiki#development-process


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Monday, June 6, 2016 11:09:25 AM
To: mini-ndn at lists.cs.ucla.edu; Ashlesh Gawande (agawande)
Subject: Controller implementation in mini-ndn : Request for advice

Hi All,

Greetings!

This is Jeeva Rajendran from Trinity College Dublin, Ireland. I am pursuing my master degree in computer science.

As part of my research, I am trying to use 'Mini-ndn' to execute and evaluate my network experiments.

>From Mini-ndn GitHub repository, I learned that Mini-ndn is based on 'Mini-ccnx' and forked from 'Mininet'. When I was going through the code of mininet, mini-ccnx and mini-ndn, I noticed that the coding related to 'Controller' is removed in mini-ndn (I could see controller implementation in mini-ccnx in conf_parser, miniccnxedit, miniccnx script and other files)

Is there a specific reason why controller implementation is not a part of mini-ndn and is there a future plan to include it in mini-ndn?

Please help with the information.

Thanks in advance

~Jeeva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160606/571c299d/attachment.html>

From shijunxiao at email.arizona.edu  Mon Jun  6 11:18:04 2016
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Mon, 6 Jun 2016 11:18:04 -0700
Subject: [Mini-NDN] Controller implementation in mini-ndn : Request for
 advice
In-Reply-To: <CAOFH+ObJEbO-m0VG7SWtpYonaL=597vL7+bXKscaaeY5bakx2w@mail.gmail.com>
References: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>
	<CAOFH+ObETs3rnk2CUpcrJJT2U=6q0mjUKm5441P_Ha73WSNxzQ@mail.gmail.com>
	<CAOFH+ObJEbO-m0VG7SWtpYonaL=597vL7+bXKscaaeY5bakx2w@mail.gmail.com>
Message-ID: <CAOFH+OarD-O6mJGZzgF2+-gWwDVyOyVpHt96vHfSARrFJOqkrw@mail.gmail.com>

Dear folks

In Mininet, a Controller is a centralized component that makes forwarding
decisions for Ethernet Switches.
I believe that Controller is still available for use in Mini-NDN, because
Mini-NDN is now an add-on of Mininet and not a fork.

However, I wonder what's the semantics of a Controller in Mini-NDN?
Last time I looked, Mini-NDN uses only Hosts. Each Host has an NFD and an
NLSR instance. They make forwarding decisions in a distributed manner.
Since there is no Switch involved, what's a use case for Controller?

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160606/c62720fd/attachment.html>

From agawande at memphis.edu  Mon Jun  6 11:29:44 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 6 Jun 2016 18:29:44 +0000
Subject: [Mini-NDN] Controller implementation in mini-ndn : Request for
 advice
In-Reply-To: <CAOFH+OarD-O6mJGZzgF2+-gWwDVyOyVpHt96vHfSARrFJOqkrw@mail.gmail.com>
References: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>
	<CAOFH+ObETs3rnk2CUpcrJJT2U=6q0mjUKm5441P_Ha73WSNxzQ@mail.gmail.com>
	<CAOFH+ObJEbO-m0VG7SWtpYonaL=597vL7+bXKscaaeY5bakx2w@mail.gmail.com>,
	<CAOFH+OarD-O6mJGZzgF2+-gWwDVyOyVpHt96vHfSARrFJOqkrw@mail.gmail.com>
Message-ID: <BN3PR04MB21963EC2B82EFA2E79ED34C2D95C0@BN3PR04MB2196.namprd04.prod.outlook.com>

Yes the controller should still be available via Mininet but it is no longer in the conf_parser for Mini-NDN.



Mini-NDN does have a provision to add switches but I do not know the use case (I think they were added back to support NFD tests at one point).

https://github.com/named-data/mini-ndn/blob/master/ndn/conf_parser.py


And yes Mini-NDN still just uses hosts.


Maybe Jeeva can elaborate why he needs a controller.


Ashlesh

________________________________
From: Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Monday, June 6, 2016 1:18:04 PM
To: Rajendran Jeeva; Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Controller implementation in mini-ndn : Request for advice


Dear folks

In Mininet, a Controller is a centralized component that makes forwarding decisions for Ethernet Switches.
I believe that Controller is still available for use in Mini-NDN, because Mini-NDN is now an add-on of Mininet and not a fork.

However, I wonder what's the semantics of a Controller in Mini-NDN?
Last time I looked, Mini-NDN uses only Hosts. Each Host has an NFD and an NLSR instance. They make forwarding decisions in a distributed manner.
Since there is no Switch involved, what's a use case for Controller?

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160606/e1215f0a/attachment.html>

From rajendrj at tcd.ie  Mon Jun  6 11:54:26 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Mon, 6 Jun 2016 19:54:26 +0100
Subject: [Mini-NDN] Controller implementation in mini-ndn : Request for
 advice
In-Reply-To: <BN3PR04MB21963EC2B82EFA2E79ED34C2D95C0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>
	<CAOFH+ObETs3rnk2CUpcrJJT2U=6q0mjUKm5441P_Ha73WSNxzQ@mail.gmail.com>
	<CAOFH+ObJEbO-m0VG7SWtpYonaL=597vL7+bXKscaaeY5bakx2w@mail.gmail.com>
	<CAOFH+OarD-O6mJGZzgF2+-gWwDVyOyVpHt96vHfSARrFJOqkrw@mail.gmail.com>
	<BN3PR04MB21963EC2B82EFA2E79ED34C2D95C0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAMGewCT+7FHjcdv5BDBLu0TyQ5PYKmAMQK46XnHWrUpb6DEi5A@mail.gmail.com>

Hi All,

Thanks for the response.

I just started with my research on this area and I may not be entirely
correct in what I am saying. Sorry if I go wrong somewhere. But, this is
what I am trying to do:

I am trying to experiment with a network that has both NDN nodes and
switches/routers and a controller to control FIB entries in those
switches/routers. Just to replicate the behaviour of OpenFlow controller
but in NDN world. Basically to study what an OpenFlow controller should
know in order to control a NDN network.

Eventhough Mininet has a controller, Mini-ccnx has customized it for the
CCN experiments (in bin/miniccnx, sources/conf_parser, bin/miniccnxedit: in
GUI). I was looking for such implementation in mini-ndn when I found it was
not implemented in mini-ndn and dropped a mail to ask for the motive behind
that.

thanks,
Jeeva


On 6 June 2016 at 19:29, Ashlesh Gawande (agawande) <agawande at memphis.edu>
wrote:

> Yes the controller should still be available via Mininet but it is no
> longer in the conf_parser for Mini-NDN.
>
>
>
> Mini-NDN does have a provision to add switches but I do not know the use
> case (I think they were added back to support NFD tests at one point).
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/conf_parser.py
>
> And yes Mini-NDN still just uses hosts.
>
>
> Maybe Jeeva can elaborate why he needs a controller.
>
>
> Ashlesh
> ------------------------------
> *From:* Junxiao Shi <shijunxiao at email.arizona.edu>
> *Sent:* Monday, June 6, 2016 1:18:04 PM
> *To:* Rajendran Jeeva; Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] Controller implementation in mini-ndn : Request
> for advice
>
>
> Dear folks
>
> In Mininet, a Controller is a centralized component that makes forwarding
> decisions for Ethernet Switches.
> I believe that Controller is still available for use in Mini-NDN, because
> Mini-NDN is now an add-on of Mininet and not a fork.
>
> However, I wonder what's the semantics of a Controller in Mini-NDN?
> Last time I looked, Mini-NDN uses only Hosts. Each Host has an NFD and an
> NLSR instance. They make forwarding decisions in a distributed manner.
> Since there is no Switch involved, what's a use case for Controller?
>
> Yours, Junxiao
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160606/7da1b025/attachment.html>

From shijunxiao at email.arizona.edu  Mon Jun  6 12:01:08 2016
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Mon, 6 Jun 2016 12:01:08 -0700
Subject: [Mini-NDN] Controller implementation in mini-ndn : Request
 foradvice
In-Reply-To: <CAMGewCT+7FHjcdv5BDBLu0TyQ5PYKmAMQK46XnHWrUpb6DEi5A@mail.gmail.com>
References: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>
	<CAOFH+ObETs3rnk2CUpcrJJT2U=6q0mjUKm5441P_Ha73WSNxzQ@mail.gmail.com>
	<CAOFH+ObJEbO-m0VG7SWtpYonaL=597vL7+bXKscaaeY5bakx2w@mail.gmail.com>
	<CAOFH+OarD-O6mJGZzgF2+-gWwDVyOyVpHt96vHfSARrFJOqkrw@mail.gmail.com>
	<BN3PR04MB21963EC2B82EFA2E79ED34C2D95C0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCT+7FHjcdv5BDBLu0TyQ5PYKmAMQK46XnHWrUpb6DEi5A@mail.gmail.com>
Message-ID: <5755c875.8f4a620a.58926.3f72@mx.google.com>

Hi Jeeva

Mini-NDN uses NFD for NDN forwarding.
NFD?s FIB is controlled by NFD-RIB; the RIB is controlled by NFD-RIB management protocol.

If you are looking at centralized control of RIB entries, the control messages should be delivered over NDN protocol. This would be possible once #3142 is approved and implemented.
The ?controller? for this purpose is just an NDN application, and it?s unrelated to OpenFlow.

Yours, Junxiao

From: Rajendran Jeeva
Sent: Monday, June 6, 2016 11:54
To: Ashlesh Gawande (agawande)
Cc: Junxiao Shi; mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Controller implementation in mini-ndn : Request foradvice

Hi All,

Thanks for the response.

I just started with my research on this area and I may not be entirely correct in what I am saying. Sorry if I go wrong somewhere. But, this is what I am trying to do:

I am trying to experiment with a network that has both NDN nodes and switches/routers and a controller to control FIB entries in those switches/routers. Just to replicate the behaviour of OpenFlow controller but in NDN world. Basically to study what an OpenFlow controller should know in order to control a NDN network.

Eventhough Mininet has a controller, Mini-ccnx has customized it for the CCN experiments (in bin/miniccnx, sources/conf_parser, bin/miniccnxedit: in GUI). I was looking for such implementation in mini-ndn when I found it was not implemented in mini-ndn and dropped a mail to ask for the motive behind that. ?

thanks,
Jeeva
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160606/0bdbe9a1/attachment.html>

From rajendrj at tcd.ie  Tue Jun  7 13:31:35 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Tue, 7 Jun 2016 21:31:35 +0100
Subject: [Mini-NDN] Controller implementation in mini-ndn : Request
 foradvice
In-Reply-To: <5755c875.8f4a620a.58926.3f72@mx.google.com>
References: <CAMGewCQ6xKpuJsZYoHmqiG0_FspnNvKMKpj0G19R6Ao5kegKdQ@mail.gmail.com>
	<CAOFH+ObETs3rnk2CUpcrJJT2U=6q0mjUKm5441P_Ha73WSNxzQ@mail.gmail.com>
	<CAOFH+ObJEbO-m0VG7SWtpYonaL=597vL7+bXKscaaeY5bakx2w@mail.gmail.com>
	<CAOFH+OarD-O6mJGZzgF2+-gWwDVyOyVpHt96vHfSARrFJOqkrw@mail.gmail.com>
	<BN3PR04MB21963EC2B82EFA2E79ED34C2D95C0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCT+7FHjcdv5BDBLu0TyQ5PYKmAMQK46XnHWrUpb6DEi5A@mail.gmail.com>
	<5755c875.8f4a620a.58926.3f72@mx.google.com>
Message-ID: <CAMGewCRbsu2KLQhFc-Z9=YOKuKFhBZH31_rmgyeSgj8jmY75qg@mail.gmail.com>

Thanks for the clarification Junxiao!

~Jeeva

On 6 June 2016 at 20:01, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:

> Hi Jeeva
>
>
>
> Mini-NDN uses NFD for NDN forwarding.
>
> NFD?s FIB is controlled by NFD-RIB; the RIB is controlled by NFD-RIB
> management protocol
> <http://redmine.named-data.net/projects/nfd/wiki/RibMgmt>.
>
>
>
> If you are looking at centralized control of RIB entries, the control
> messages should be delivered over NDN protocol. This would be possible once
> #3142 <http://redmine.named-data.net/issues/3142> is approved and
> implemented.
>
> The ?controller? for this purpose is just an NDN application, and it?s
> unrelated to OpenFlow.
>
>
>
> Yours, Junxiao
>
>
>
> *From: *Rajendran Jeeva <rajendrj at tcd.ie>
> *Sent: *Monday, June 6, 2016 11:54
> *To: *Ashlesh Gawande (agawande) <agawande at memphis.edu>
> *Cc: *Junxiao Shi <shijunxiao at email.arizona.edu>;
> mini-ndn at lists.cs.ucla.edu
> *Subject: *Re: [Mini-NDN] Controller implementation in mini-ndn : Request
> foradvice
>
>
>
> Hi All,
>
>
>
> Thanks for the response.
>
>
>
> I just started with my research on this area and I may not be entirely
> correct in what I am saying. Sorry if I go wrong somewhere. But, this is
> what I am trying to do:
>
>
>
> I am trying to experiment with a network that has both NDN nodes and
> switches/routers and a controller to control FIB entries in those
> switches/routers. Just to replicate the behaviour of OpenFlow controller
> but in NDN world. Basically to study what an OpenFlow controller should
> know in order to control a NDN network.
>
>
>
> Eventhough Mininet has a controller, Mini-ccnx has customized it for the
> CCN experiments (in bin/miniccnx, sources/conf_parser, bin/miniccnxedit: in
> GUI). I was looking for such implementation in mini-ndn when I found it was
> not implemented in mini-ndn and dropped a mail to ask for the motive behind
> that.
>
>
>
> thanks,
>
> Jeeva
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160607/a5b0baf7/attachment.html>

From rajendrj at tcd.ie  Sun Jun 12 08:33:05 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Sun, 12 Jun 2016 16:33:05 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
Message-ID: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall
experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the
working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c)
(10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
*Waiting 60 seconds for convergence...*
...done
*NLSR has not converged. Exiting...*
rajendrj at Jeeva:~$

As shown in the last line, the execution exited with 'NLSR has not converged'

' message

Am I missing something here ? Is this because 'mininet' is running
from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?

Please advise and help me here

Thanks in advance,

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

From agawande at memphis.edu  Mon Jun 13 08:56:04 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 13 Jun 2016 15:56:04 +0000
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
Message-ID: <BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>

Try to run just:

sudo minindn


And when the command line comes up, wait for some time and check the FIB of each node:


a nfd-status -b

b nfd-status -b

c nfd-status -b

d nfd-status -b


They should all have each other prefixes (i.e. /ndn/edu/<node>) and routers (/ndn/edu/%C1.Router/<node>).

If not you will get the error you got - NLSR could not converge (only if an experiment was run).


If they do have each other's prefixes then you can try to increase the convergence time:

sudo minindn --experiment=pingall --ctime 100


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Sunday, June 12, 2016 10:33:05 AM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
Waiting 60 seconds for convergence...
...done
NLSR has not converged. Exiting...
rajendrj at Jeeva:~$


As shown in the last line, the execution exited with 'NLSR has not converged'

' message


Am I missing something here ? Is this because 'mininet' is running from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?


Please advise and help me here


Thanks in advance,

~Jeeva




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

From rajendrj at tcd.ie  Tue Jun 14 07:32:55 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Tue, 14 Jun 2016 15:32:55 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>

Hi Ashlesh,

Thanks for the response.

I tried running the command 'a nfd-status -b' for node 'a' and for other
nodes as well. It is not displaying anything .

1. NFD status:

mininet> a nfd-status -b
mininet>


NLSR status is displaying as follow

2. NLSR status:

mininet> a nlsrc status
NLSR Status
LSDB:
  OriginRouter: /ndn/edu/%C1.Router/cs/a

    Coordinate LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber:
90, ExpirationPeriod: 3591936 milliseconds)
      angle=0
      radius=0

    Name LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber:
90, ExpirationPeriod: 3591932 milliseconds)
      name=/ndn/edu/a

  OriginRouter: /ndn/edu/%C1.Router/cs/b

3. I just tried running 'nfd' command for a node and it displayed 'Failed
to read configuration file: /usr/local/etc/ndn/nfd.conf'

mininet> a nfd
1465913606.293515 FATAL: [NFD] Failed to read configuration file:
/usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void
nfd::ConfigFile::parse(const string&, bool)]
mininet>

I ensured again that NFD is installed when mini-ndn is installed and the
configuration is run.

Not sure whether the convergence is not happening because the conf file is
missing.

Any help would be appreciated

Thanks in advance

~Jeeva


On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu>
wrote:

> Try to run just:
>
> sudo minindn
>
>
> And when the command line comes up, wait for some time and check the FIB
> of each node:
>
>
> a nfd-status -b
>
> b nfd-status -b
>
> c nfd-status -b
>
> d nfd-status -b
>
>
> They should all have each other prefixes (i.e. /ndn/edu/<node>) and
> routers (/ndn/edu/%C1.Router/<node>).
>
> If not you will get the error you got - NLSR could not converge (only if
> an experiment was run).
>
>
> If they do have each other's prefixes then you can try to increase the
> convergence time:
>
> sudo minindn --experiment=pingall --ctime 100
>
>
> Ashlesh
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
> Rajendran Jeeva <rajendrj at tcd.ie>
> *Sent:* Sunday, June 12, 2016 10:33:05 AM
> *To:* mini-ndn at lists.cs.ucla.edu
> *Subject:* [Mini-NDN] NLSR has not converged - Issue while running minindn
>
> Hi All,
>
> I have installed mini-ndn as follows:
>
> 1. Cloned 'mini-ndn' from github
> 2. $ cd mini-ndn
> 3. Installed it using the command
>
> sudo ./install.sh -mrfti
>
> 4. When the above command got executed , NFD, NLSR, ndn, and
> mininet got installed in the 'mini-ndn' directory(not in the home directory
>
> as I ran install.sh from inside mini-ndn directory )
>
> 5. Once the installation is completed I tried running the --Pingall experiment with
>
> default topology
>
> 6. There was an error stating 'mininet.topo module not found'(Rectified this
>
> problem by installing 'mininet' in the home directory)
>
> 7. When I ran the minindn command again, I got the following output
>
> rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
> No results folder specified; experiment results will remain in the working directory
> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
> *** Creating network
> *** Adding controller
> *** Adding hosts:
> a b c d
> *** Adding switches:
>
> *** Adding links:
> (10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
> *** Configuring hosts
> a b c d
> Setup time: 8
> *** Starting controller
> c0
> *** Starting 0 switches
>
> Loading experiment: pingall
> Using 1.000000 traffic
> *Waiting 60 seconds for convergence...*
> ...done
> *NLSR has not converged. Exiting...*
> rajendrj at Jeeva:~$
>
> As shown in the last line, the execution exited with 'NLSR has not converged'
>
> ' message
>
> Am I missing something here ? Is this because 'mininet' is running from home directory
>
> but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see
>
> the error output?
>
> Please advise and help me here
>
> Thanks in advance,
>
> ~Jeeva
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160614/335b85e3/attachment.html>

From agawande at memphis.edu  Tue Jun 14 09:29:50 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Tue, 14 Jun 2016 16:29:50 +0000
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
Message-ID: <BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>

Can you check whether nfd-status works outside of mini-ndn?

Just do nfd-start and then do nfd-status.


Convergence depends on nfd-status as mini-ndn checks whether prefixes and routers have been installed.


> a nfd does not work because we use the a.conf file, if you do" a nfd -f a.conf &" it should work.

But the problem seems to be that nfd-status is not working (even outside of mini-ndn).


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Tuesday, June 14, 2016 9:32:55 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried running the command 'a nfd-status -b' for node 'a' and for other nodes as well. It is not displaying anything .

1. NFD status:

mininet> a nfd-status -b
mininet>


NLSR status is displaying as follow

2. NLSR status:

mininet> a nlsrc status
NLSR Status
LSDB:
  OriginRouter: /ndn/edu/%C1.Router/cs/a

    Coordinate LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
      angle=0
      radius=0

    Name LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
      name=/ndn/edu/a

  OriginRouter: /ndn/edu/%C1.Router/cs/b

3. I just tried running 'nfd' command for a node and it displayed 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'

mininet> a nfd
1465913606.293515 FATAL: [NFD] Failed to read configuration file: /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
mininet>

I ensured again that NFD is installed when mini-ndn is installed and the configuration is run.

Not sure whether the convergence is not happening because the conf file is missing.

Any help would be appreciated

Thanks in advance

~Jeeva


On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Try to run just:

sudo minindn


And when the command line comes up, wait for some time and check the FIB of each node:


a nfd-status -b

b nfd-status -b

c nfd-status -b

d nfd-status -b


They should all have each other prefixes (i.e. /ndn/edu/<node>) and routers (/ndn/edu/%C1.Router/<node>).

If not you will get the error you got - NLSR could not converge (only if an experiment was run).


If they do have each other's prefixes then you can try to increase the convergence time:

sudo minindn --experiment=pingall --ctime 100


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Sunday, June 12, 2016 10:33:05 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
Waiting 60 seconds for convergence...
...done
NLSR has not converged. Exiting...
rajendrj at Jeeva:~$


As shown in the last line, the execution exited with 'NLSR has not converged'

' message


Am I missing something here ? Is this because 'mininet' is running from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?


Please advise and help me here


Thanks in advance,

~Jeeva





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

From agawande at memphis.edu  Tue Jun 14 11:42:44 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Tue, 14 Jun 2016 18:42:44 +0000
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>,
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>

Hi


Some new information may have come to light, if nfd-status is not working outside Mini-NDN can you try the following patch:

https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0


To do so go to your NFD folder and do

git checkout ace83ac9384da037a36695888e829d7337ce36b0

./waf distclean

./waf configure --without-websocket

./waf

sudo ./waf install


Then try to run Mini-NDN experiment again.


And is your OS, Ubuntu 14.04?


Thanks

Ashlesh


________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu>
Sent: Tuesday, June 14, 2016 11:29:50 AM
To: Rajendran Jeeva
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn


Can you check whether nfd-status works outside of mini-ndn?

Just do nfd-start and then do nfd-status.


Convergence depends on nfd-status as mini-ndn checks whether prefixes and routers have been installed.


> a nfd does not work because we use the a.conf file, if you do" a nfd -f a.conf &" it should work.

But the problem seems to be that nfd-status is not working (even outside of mini-ndn).


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Tuesday, June 14, 2016 9:32:55 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried running the command 'a nfd-status -b' for node 'a' and for other nodes as well. It is not displaying anything .

1. NFD status:

mininet> a nfd-status -b
mininet>


NLSR status is displaying as follow

2. NLSR status:

mininet> a nlsrc status
NLSR Status
LSDB:
  OriginRouter: /ndn/edu/%C1.Router/cs/a

    Coordinate LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
      angle=0
      radius=0

    Name LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
      name=/ndn/edu/a

  OriginRouter: /ndn/edu/%C1.Router/cs/b

3. I just tried running 'nfd' command for a node and it displayed 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'

mininet> a nfd
1465913606.293515 FATAL: [NFD] Failed to read configuration file: /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
mininet>

I ensured again that NFD is installed when mini-ndn is installed and the configuration is run.

Not sure whether the convergence is not happening because the conf file is missing.

Any help would be appreciated

Thanks in advance

~Jeeva


On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Try to run just:

sudo minindn


And when the command line comes up, wait for some time and check the FIB of each node:


a nfd-status -b

b nfd-status -b

c nfd-status -b

d nfd-status -b


They should all have each other prefixes (i.e. /ndn/edu/<node>) and routers (/ndn/edu/%C1.Router/<node>).

If not you will get the error you got - NLSR could not converge (only if an experiment was run).


If they do have each other's prefixes then you can try to increase the convergence time:

sudo minindn --experiment=pingall --ctime 100


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Sunday, June 12, 2016 10:33:05 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
Waiting 60 seconds for convergence...
...done
NLSR has not converged. Exiting...
rajendrj at Jeeva:~$


As shown in the last line, the execution exited with 'NLSR has not converged'

' message


Am I missing something here ? Is this because 'mininet' is running from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?


Please advise and help me here


Thanks in advance,

~Jeeva





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

From rajendrj at tcd.ie  Tue Jun 14 12:48:39 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Tue, 14 Jun 2016 20:48:39 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>

Hi Ashlesh,

Thank you for sorting out the problem.

I am using Ubuntu 14.04 LTS.

Yeah. 'nfd-status' was not working even outside the mini-ndn folder  (seems
like nfd-start and stop were working, I even got 'NFD already running'
message when i triggered nfd-start multiple times)

When i tried checking out the above patch in NFD folder there was 'fatal:
reference not in tree' issue. So, i removed '--depth 1' part from git clone
of NFD in install.sh of mini-ndn and reinstalled it

I checked out the above patch as well and ran waf configuration and
installation

Then i executed both 'nfd-status' and pingall experiment and both got
executed successfully with the convergence time of 120 instead of 60. Thank
you so much for the help.

I just have one more query. When I executed the command 'sudo minindn
--experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it
showed count for only few files . Is this expected ?

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:243
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:242
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:241
/tmp/d/ping-data/c.txt:0

Please advise.

Thanks,
~Jeeva



On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <agawande at memphis.edu>
wrote:

> Hi
>
>
> Some new information may have come to light, if nfd-status is not working
> outside Mini-NDN can you try the following patch:
>
>
> https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0
>
>
> To do so go to your NFD folder and do
>
> git checkout ace83ac9384da037a36695888e829d7337ce36b0
>
> ./waf distclean
>
> ./waf configure --without-websocket
>
> ./waf
>
> sudo ./waf install
>
>
> Then try to run Mini-NDN experiment again.
>
>
> And is your OS, Ubuntu 14.04?
>
>
> Thanks
>
> Ashlesh
>
>
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
> Ashlesh Gawande (agawande) <agawande at memphis.edu>
> *Sent:* Tuesday, June 14, 2016 11:29:50 AM
> *To:* Rajendran Jeeva
>
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
> minindn
>
>
> Can you check whether nfd-status works outside of mini-ndn?
>
> Just do nfd-start and then do nfd-status.
>
>
> Convergence depends on nfd-status as mini-ndn checks whether prefixes and
> routers have been installed.
>
>
> > a nfd does not work because we use the a.conf file, if you do" a nfd -f
> a.conf &" it should work.
>
> But the problem seems to be that nfd-status is not working (even outside
> of mini-ndn).
>
>
> Ashlesh
> ------------------------------
> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
> *Sent:* Tuesday, June 14, 2016 9:32:55 AM
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
> minindn
>
> Hi Ashlesh,
>
> Thanks for the response.
>
> I tried running the command 'a nfd-status -b' for node 'a' and for other
> nodes as well. It is not displaying anything .
>
> 1. NFD status:
>
> mininet> a nfd-status -b
> mininet>
>
>
> NLSR status is displaying as follow
>
> 2. NLSR status:
>
> mininet> a nlsrc status
> NLSR Status
> LSDB:
>   OriginRouter: /ndn/edu/%C1.Router/cs/a
>
>     Coordinate LSA:
>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber:
> 90, ExpirationPeriod: 3591936 milliseconds)
>       angle=0
>       radius=0
>
>     Name LSA:
>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber:
> 90, ExpirationPeriod: 3591932 milliseconds)
>       name=/ndn/edu/a
>
>   OriginRouter: /ndn/edu/%C1.Router/cs/b
>
> 3. I just tried running 'nfd' command for a node and it displayed 'Failed
> to read configuration file: /usr/local/etc/ndn/nfd.conf'
>
> mininet> a nfd
> 1465913606.293515 FATAL: [NFD] Failed to read configuration file:
> /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void
> nfd::ConfigFile::parse(const string&, bool)]
> mininet>
>
> I ensured again that NFD is installed when mini-ndn is installed and the
> configuration is run.
>
> Not sure whether the convergence is not happening because the conf file is
> missing.
>
> Any help would be appreciated
>
> Thanks in advance
>
> ~Jeeva
>
>
> On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu
> > wrote:
>
>> Try to run just:
>>
>> sudo minindn
>>
>>
>> And when the command line comes up, wait for some time and check the FIB
>> of each node:
>>
>>
>> a nfd-status -b
>>
>> b nfd-status -b
>>
>> c nfd-status -b
>>
>> d nfd-status -b
>>
>>
>> They should all have each other prefixes (i.e. /ndn/edu/<node>) and
>> routers (/ndn/edu/%C1.Router/<node>).
>>
>> If not you will get the error you got - NLSR could not converge (only if
>> an experiment was run).
>>
>>
>> If they do have each other's prefixes then you can try to increase the
>> convergence time:
>>
>> sudo minindn --experiment=pingall --ctime 100
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>> Rajendran Jeeva <rajendrj at tcd.ie>
>> *Sent:* Sunday, June 12, 2016 10:33:05 AM
>> *To:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* [Mini-NDN] NLSR has not converged - Issue while running
>> minindn
>>
>> Hi All,
>>
>> I have installed mini-ndn as follows:
>>
>> 1. Cloned 'mini-ndn' from github
>> 2. $ cd mini-ndn
>> 3. Installed it using the command
>>
>> sudo ./install.sh -mrfti
>>
>> 4. When the above command got executed , NFD, NLSR, ndn, and
>> mininet got installed in the 'mini-ndn' directory(not in the home directory
>>
>> as I ran install.sh from inside mini-ndn directory )
>>
>> 5. Once the installation is completed I tried running the --Pingall experiment with
>>
>> default topology
>>
>> 6. There was an error stating 'mininet.topo module not found'(Rectified this
>>
>> problem by installing 'mininet' in the home directory)
>>
>> 7. When I ran the minindn command again, I got the following output
>>
>> rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
>> No results folder specified; experiment results will remain in the working directory
>> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
>> *** Creating network
>> *** Adding controller
>> *** Adding hosts:
>> a b c d
>> *** Adding switches:
>>
>> *** Adding links:
>> (10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
>> *** Configuring hosts
>> a b c d
>> Setup time: 8
>> *** Starting controller
>> c0
>> *** Starting 0 switches
>>
>> Loading experiment: pingall
>> Using 1.000000 traffic
>> *Waiting 60 seconds for convergence...*
>> ...done
>> *NLSR has not converged. Exiting...*
>> rajendrj at Jeeva:~$
>>
>> As shown in the last line, the execution exited with 'NLSR has not converged'
>>
>> ' message
>>
>> Am I missing something here ? Is this because 'mininet' is running from home directory
>>
>> but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see
>>
>> the error output?
>>
>> Please advise and help me here
>>
>> Thanks in advance,
>>
>> ~Jeeva
>>
>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160614/28444c0b/attachment.html>

From agawande at memphis.edu  Tue Jun 14 13:08:51 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Tue, 14 Jun 2016 20:08:51 +0000
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
Message-ID: <BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>

It is not expected, I think you have timeouts in those, search:

grep -c timeout /tmp/*/ping-data/*.txt


ndnping is timing out for some reason - either NFD went down during the experiment in another terminal

(you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went down on any of the node.


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Tuesday, June 14, 2016 2:48:39 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thank you for sorting out the problem.

I am using Ubuntu 14.04 LTS.

Yeah. 'nfd-status' was not working even outside the mini-ndn folder  (seems like nfd-start and stop were working, I even got 'NFD already running' message when i triggered nfd-start multiple times)

When i tried checking out the above patch in NFD folder there was 'fatal: reference not in tree' issue. So, i removed '--depth 1' part from git clone of NFD in install.sh of mini-ndn and reinstalled it

I checked out the above patch as well and ran waf configuration and installation

Then i executed both 'nfd-status' and pingall experiment and both got executed successfully with the convergence time of 120 instead of 60. Thank you so much for the help.

I just have one more query. When I executed the command 'sudo minindn --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it showed count for only few files . Is this expected ?

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:243
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:242
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:241
/tmp/d/ping-data/c.txt:0

Please advise.

Thanks,
~Jeeva



On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Hi


Some new information may have come to light, if nfd-status is not working outside Mini-NDN can you try the following patch:

https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0


To do so go to your NFD folder and do

git checkout ace83ac9384da037a36695888e829d7337ce36b0

./waf distclean

./waf configure --without-websocket

./waf

sudo ./waf install


Then try to run Mini-NDN experiment again.


And is your OS, Ubuntu 14.04?


Thanks

Ashlesh


________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>>
Sent: Tuesday, June 14, 2016 11:29:50 AM
To: Rajendran Jeeva

Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn


Can you check whether nfd-status works outside of mini-ndn?

Just do nfd-start and then do nfd-status.


Convergence depends on nfd-status as mini-ndn checks whether prefixes and routers have been installed.


> a nfd does not work because we use the a.conf file, if you do" a nfd -f a.conf &" it should work.

But the problem seems to be that nfd-status is not working (even outside of mini-ndn).


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Tuesday, June 14, 2016 9:32:55 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried running the command 'a nfd-status -b' for node 'a' and for other nodes as well. It is not displaying anything .

1. NFD status:

mininet> a nfd-status -b
mininet>


NLSR status is displaying as follow

2. NLSR status:

mininet> a nlsrc status
NLSR Status
LSDB:
  OriginRouter: /ndn/edu/%C1.Router/cs/a

    Coordinate LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
      angle=0
      radius=0

    Name LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
      name=/ndn/edu/a

  OriginRouter: /ndn/edu/%C1.Router/cs/b

3. I just tried running 'nfd' command for a node and it displayed 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'

mininet> a nfd
1465913606.293515 FATAL: [NFD] Failed to read configuration file: /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
mininet>

I ensured again that NFD is installed when mini-ndn is installed and the configuration is run.

Not sure whether the convergence is not happening because the conf file is missing.

Any help would be appreciated

Thanks in advance

~Jeeva


On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Try to run just:

sudo minindn


And when the command line comes up, wait for some time and check the FIB of each node:


a nfd-status -b

b nfd-status -b

c nfd-status -b

d nfd-status -b


They should all have each other prefixes (i.e. /ndn/edu/<node>) and routers (/ndn/edu/%C1.Router/<node>).

If not you will get the error you got - NLSR could not converge (only if an experiment was run).


If they do have each other's prefixes then you can try to increase the convergence time:

sudo minindn --experiment=pingall --ctime 100


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Sunday, June 12, 2016 10:33:05 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
Waiting 60 seconds for convergence...
...done
NLSR has not converged. Exiting...
rajendrj at Jeeva:~$


As shown in the last line, the execution exited with 'NLSR has not converged'

' message


Am I missing something here ? Is this because 'mininet' is running from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?


Please advise and help me here


Thanks in advance,

~Jeeva






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

From rajendrj at tcd.ie  Wed Jun 15 09:41:34 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Wed, 15 Jun 2016 17:41:34 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>

Thanks Ashlesh!

When I tried pingAll experiment today all the pings were getting timed out
(no content entries in the text file; only timeout entries)

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:0
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:0
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:0
/tmp/d/ping-data/c.txt:0
rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:10
/tmp/a/ping-data/c.txt:10
/tmp/a/ping-data/d.txt:10
/tmp/b/ping-data/a.txt:10
/tmp/b/ping-data/c.txt:10
/tmp/b/ping-data/d.txt:10
/tmp/c/ping-data/a.txt:10
/tmp/c/ping-data/b.txt:10
/tmp/c/ping-data/d.txt:10
/tmp/d/ping-data/a.txt:10
/tmp/d/ping-data/b.txt:10
/tmp/d/ping-data/c.txt:10

I was running the command from only one terminal (no other terminals are
open). NFD and NLSR status are getting displayed for all the nodes

I also tried manually 'ndnping' from the node 'a' to the prefix
'/ndn/edu/b' , but it got timed out as well

Is there a way to track the reason behind these timeouts ?

Please advise

thanks,
Jeeva


On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <agawande at memphis.edu>
wrote:

> It is not expected, I think you have timeouts in those, search:
>
> grep -c timeout /tmp/*/ping-data/*.txt
>
>
> ndnping is timing out for some reason - either NFD went down during the
> experiment in another terminal
>
> (you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went
> down on any of the node.
>
>
> Ashlesh
> ------------------------------
> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
> *Sent:* Tuesday, June 14, 2016 2:48:39 PM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
> minindn
>
> Hi Ashlesh,
>
> Thank you for sorting out the problem.
>
> I am using Ubuntu 14.04 LTS.
>
> Yeah. 'nfd-status' was not working even outside the mini-ndn folder
> (seems like nfd-start and stop were working, I even got 'NFD already
> running' message when i triggered nfd-start multiple times)
>
> When i tried checking out the above patch in NFD folder there was 'fatal:
> reference not in tree' issue. So, i removed '--depth 1' part from git clone
> of NFD in install.sh of mini-ndn and reinstalled it
>
> I checked out the above patch as well and ran waf configuration and
> installation
>
> Then i executed both 'nfd-status' and pingall experiment and both got
> executed successfully with the convergence time of 120 instead of 60. Thank
> you so much for the help.
>
> I just have one more query. When I executed the command 'sudo minindn
> --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it
> showed count for only few files . Is this expected ?
>
> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
> /tmp/a/ping-data/b.txt:243
> /tmp/a/ping-data/c.txt:0
> /tmp/a/ping-data/d.txt:0
> /tmp/b/ping-data/a.txt:0
> /tmp/b/ping-data/c.txt:0
> /tmp/b/ping-data/d.txt:0
> /tmp/c/ping-data/a.txt:0
> /tmp/c/ping-data/b.txt:242
> /tmp/c/ping-data/d.txt:0
> /tmp/d/ping-data/a.txt:0
> /tmp/d/ping-data/b.txt:241
> /tmp/d/ping-data/c.txt:0
>
> Please advise.
>
> Thanks,
> ~Jeeva
>
>
>
> On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <agawande at memphis.edu
> > wrote:
>
>> Hi
>>
>>
>> Some new information may have come to light, if nfd-status is not working
>> outside Mini-NDN can you try the following patch:
>>
>>
>> https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0
>>
>>
>> To do so go to your NFD folder and do
>>
>> git checkout ace83ac9384da037a36695888e829d7337ce36b0
>>
>> ./waf distclean
>>
>> ./waf configure --without-websocket
>>
>> ./waf
>>
>> sudo ./waf install
>>
>>
>> Then try to run Mini-NDN experiment again.
>>
>>
>> And is your OS, Ubuntu 14.04?
>>
>>
>> Thanks
>>
>> Ashlesh
>>
>>
>> ------------------------------
>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>> Ashlesh Gawande (agawande) <agawande at memphis.edu>
>> *Sent:* Tuesday, June 14, 2016 11:29:50 AM
>> *To:* Rajendran Jeeva
>>
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>> minindn
>>
>>
>> Can you check whether nfd-status works outside of mini-ndn?
>>
>> Just do nfd-start and then do nfd-status.
>>
>>
>> Convergence depends on nfd-status as mini-ndn checks whether prefixes and
>> routers have been installed.
>>
>>
>> > a nfd does not work because we use the a.conf file, if you do" a nfd -f
>> a.conf &" it should work.
>>
>> But the problem seems to be that nfd-status is not working (even outside
>> of mini-ndn).
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>> *Sent:* Tuesday, June 14, 2016 9:32:55 AM
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>> minindn
>>
>> Hi Ashlesh,
>>
>> Thanks for the response.
>>
>> I tried running the command 'a nfd-status -b' for node 'a' and for other
>> nodes as well. It is not displaying anything .
>>
>> 1. NFD status:
>>
>> mininet> a nfd-status -b
>> mininet>
>>
>>
>> NLSR status is displaying as follow
>>
>> 2. NLSR status:
>>
>> mininet> a nlsrc status
>> NLSR Status
>> LSDB:
>>   OriginRouter: /ndn/edu/%C1.Router/cs/a
>>
>>     Coordinate LSA:
>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>> SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
>>       angle=0
>>       radius=0
>>
>>     Name LSA:
>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>> SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
>>       name=/ndn/edu/a
>>
>>   OriginRouter: /ndn/edu/%C1.Router/cs/b
>>
>> 3. I just tried running 'nfd' command for a node and it displayed 'Failed
>> to read configuration file: /usr/local/etc/ndn/nfd.conf'
>>
>> mininet> a nfd
>> 1465913606.293515 FATAL: [NFD] Failed to read configuration file:
>> /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void
>> nfd::ConfigFile::parse(const string&, bool)]
>> mininet>
>>
>> I ensured again that NFD is installed when mini-ndn is installed and the
>> configuration is run.
>>
>> Not sure whether the convergence is not happening because the conf file
>> is missing.
>>
>> Any help would be appreciated
>>
>> Thanks in advance
>>
>> ~Jeeva
>>
>>
>> On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> Try to run just:
>>>
>>> sudo minindn
>>>
>>>
>>> And when the command line comes up, wait for some time and check the FIB
>>> of each node:
>>>
>>>
>>> a nfd-status -b
>>>
>>> b nfd-status -b
>>>
>>> c nfd-status -b
>>>
>>> d nfd-status -b
>>>
>>>
>>> They should all have each other prefixes (i.e. /ndn/edu/<node>) and
>>> routers (/ndn/edu/%C1.Router/<node>).
>>>
>>> If not you will get the error you got - NLSR could not converge (only if
>>> an experiment was run).
>>>
>>>
>>> If they do have each other's prefixes then you can try to increase the
>>> convergence time:
>>>
>>> sudo minindn --experiment=pingall --ctime 100
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>> Rajendran Jeeva <rajendrj at tcd.ie>
>>> *Sent:* Sunday, June 12, 2016 10:33:05 AM
>>> *To:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* [Mini-NDN] NLSR has not converged - Issue while running
>>> minindn
>>>
>>> Hi All,
>>>
>>> I have installed mini-ndn as follows:
>>>
>>> 1. Cloned 'mini-ndn' from github
>>> 2. $ cd mini-ndn
>>> 3. Installed it using the command
>>>
>>> sudo ./install.sh -mrfti
>>>
>>> 4. When the above command got executed , NFD, NLSR, ndn, and
>>> mininet got installed in the 'mini-ndn' directory(not in the home directory
>>>
>>> as I ran install.sh from inside mini-ndn directory )
>>>
>>> 5. Once the installation is completed I tried running the --Pingall experiment with
>>>
>>> default topology
>>>
>>> 6. There was an error stating 'mininet.topo module not found'(Rectified this
>>>
>>> problem by installing 'mininet' in the home directory)
>>>
>>> 7. When I ran the minindn command again, I got the following output
>>>
>>> rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
>>> No results folder specified; experiment results will remain in the working directory
>>> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
>>> *** Creating network
>>> *** Adding controller
>>> *** Adding hosts:
>>> a b c d
>>> *** Adding switches:
>>>
>>> *** Adding links:
>>> (10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
>>> *** Configuring hosts
>>> a b c d
>>> Setup time: 8
>>> *** Starting controller
>>> c0
>>> *** Starting 0 switches
>>>
>>> Loading experiment: pingall
>>> Using 1.000000 traffic
>>> *Waiting 60 seconds for convergence...*
>>> ...done
>>> *NLSR has not converged. Exiting...*
>>> rajendrj at Jeeva:~$
>>>
>>> As shown in the last line, the execution exited with 'NLSR has not converged'
>>>
>>> ' message
>>>
>>> Am I missing something here ? Is this because 'mininet' is running from home directory
>>>
>>> but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see
>>>
>>> the error output?
>>>
>>> Please advise and help me here
>>>
>>> Thanks in advance,
>>>
>>> ~Jeeva
>>>
>>>
>>>
>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160615/b8b50dcf/attachment.html>

From rajendrj at tcd.ie  Wed Jun 15 09:48:36 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Wed, 15 Jun 2016 17:48:36 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>
Message-ID: <CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>

I tried running 'NFD' in one terminal (using sudo nfd-start) and meanwhile
checked for the nfd-status in another terminal(using sudo nfd-status), and
I saw the following messages in the terminal where NFD was running:

1466016269.157386 INFO: [UnixStreamTransport]
[id=0,local=unix:///run/nfd.sock,remote=fd://28] Creating transport
1466016269.157470 INFO: [FaceTable] Added face id=261 remote=fd://28
local=unix:///run/nfd.sock
1466016269.202716 INFO: [Transport]
[id=261,local=unix:///run/nfd.sock,remote=fd://28] setState UP -> FAILED
1466016269.202831 INFO: [Transport]
[id=261,local=unix:///run/nfd.sock,remote=fd://28] setState FAILED -> CLOSED
1466016269.207058 INFO: [FaceTable] Removed face id=261 remote=fd://28
local=unix:///run/nfd.sock


Jeeva

On 15 June 2016 at 17:41, Rajendran Jeeva <rajendrj at tcd.ie> wrote:

> Thanks Ashlesh!
>
> When I tried pingAll experiment today all the pings were getting timed out
> (no content entries in the text file; only timeout entries)
>
> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
> /tmp/a/ping-data/b.txt:0
> /tmp/a/ping-data/c.txt:0
> /tmp/a/ping-data/d.txt:0
> /tmp/b/ping-data/a.txt:0
> /tmp/b/ping-data/c.txt:0
> /tmp/b/ping-data/d.txt:0
> /tmp/c/ping-data/a.txt:0
> /tmp/c/ping-data/b.txt:0
> /tmp/c/ping-data/d.txt:0
> /tmp/d/ping-data/a.txt:0
> /tmp/d/ping-data/b.txt:0
> /tmp/d/ping-data/c.txt:0
> rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
> /tmp/a/ping-data/b.txt:10
> /tmp/a/ping-data/c.txt:10
> /tmp/a/ping-data/d.txt:10
> /tmp/b/ping-data/a.txt:10
> /tmp/b/ping-data/c.txt:10
> /tmp/b/ping-data/d.txt:10
> /tmp/c/ping-data/a.txt:10
> /tmp/c/ping-data/b.txt:10
> /tmp/c/ping-data/d.txt:10
> /tmp/d/ping-data/a.txt:10
> /tmp/d/ping-data/b.txt:10
> /tmp/d/ping-data/c.txt:10
>
> I was running the command from only one terminal (no other terminals are
> open). NFD and NLSR status are getting displayed for all the nodes
>
> I also tried manually 'ndnping' from the node 'a' to the prefix
> '/ndn/edu/b' , but it got timed out as well
>
> Is there a way to track the reason behind these timeouts ?
>
> Please advise
>
> thanks,
> Jeeva
>
>
> On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <agawande at memphis.edu
> > wrote:
>
>> It is not expected, I think you have timeouts in those, search:
>>
>> grep -c timeout /tmp/*/ping-data/*.txt
>>
>>
>> ndnping is timing out for some reason - either NFD went down during the
>> experiment in another terminal
>>
>> (you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went
>> down on any of the node.
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>> *Sent:* Tuesday, June 14, 2016 2:48:39 PM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>> minindn
>>
>> Hi Ashlesh,
>>
>> Thank you for sorting out the problem.
>>
>> I am using Ubuntu 14.04 LTS.
>>
>> Yeah. 'nfd-status' was not working even outside the mini-ndn folder
>> (seems like nfd-start and stop were working, I even got 'NFD already
>> running' message when i triggered nfd-start multiple times)
>>
>> When i tried checking out the above patch in NFD folder there was 'fatal:
>> reference not in tree' issue. So, i removed '--depth 1' part from git clone
>> of NFD in install.sh of mini-ndn and reinstalled it
>>
>> I checked out the above patch as well and ran waf configuration and
>> installation
>>
>> Then i executed both 'nfd-status' and pingall experiment and both got
>> executed successfully with the convergence time of 120 instead of 60. Thank
>> you so much for the help.
>>
>> I just have one more query. When I executed the command 'sudo minindn
>> --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it
>> showed count for only few files . Is this expected ?
>>
>> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
>> /tmp/a/ping-data/b.txt:243
>> /tmp/a/ping-data/c.txt:0
>> /tmp/a/ping-data/d.txt:0
>> /tmp/b/ping-data/a.txt:0
>> /tmp/b/ping-data/c.txt:0
>> /tmp/b/ping-data/d.txt:0
>> /tmp/c/ping-data/a.txt:0
>> /tmp/c/ping-data/b.txt:242
>> /tmp/c/ping-data/d.txt:0
>> /tmp/d/ping-data/a.txt:0
>> /tmp/d/ping-data/b.txt:241
>> /tmp/d/ping-data/c.txt:0
>>
>> Please advise.
>>
>> Thanks,
>> ~Jeeva
>>
>>
>>
>> On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> Hi
>>>
>>>
>>> Some new information may have come to light, if nfd-status is not
>>> working outside Mini-NDN can you try the following patch:
>>>
>>>
>>> https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0
>>>
>>>
>>> To do so go to your NFD folder and do
>>>
>>> git checkout ace83ac9384da037a36695888e829d7337ce36b0
>>>
>>> ./waf distclean
>>>
>>> ./waf configure --without-websocket
>>>
>>> ./waf
>>>
>>> sudo ./waf install
>>>
>>>
>>> Then try to run Mini-NDN experiment again.
>>>
>>>
>>> And is your OS, Ubuntu 14.04?
>>>
>>>
>>> Thanks
>>>
>>> Ashlesh
>>>
>>>
>>> ------------------------------
>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>> Ashlesh Gawande (agawande) <agawande at memphis.edu>
>>> *Sent:* Tuesday, June 14, 2016 11:29:50 AM
>>> *To:* Rajendran Jeeva
>>>
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>>> minindn
>>>
>>>
>>> Can you check whether nfd-status works outside of mini-ndn?
>>>
>>> Just do nfd-start and then do nfd-status.
>>>
>>>
>>> Convergence depends on nfd-status as mini-ndn checks whether prefixes
>>> and routers have been installed.
>>>
>>>
>>> > a nfd does not work because we use the a.conf file, if you do" a nfd
>>> -f a.conf &" it should work.
>>>
>>> But the problem seems to be that nfd-status is not working (even outside
>>> of mini-ndn).
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>> *Sent:* Tuesday, June 14, 2016 9:32:55 AM
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>>> minindn
>>>
>>> Hi Ashlesh,
>>>
>>> Thanks for the response.
>>>
>>> I tried running the command 'a nfd-status -b' for node 'a' and for other
>>> nodes as well. It is not displaying anything .
>>>
>>> 1. NFD status:
>>>
>>> mininet> a nfd-status -b
>>> mininet>
>>>
>>>
>>> NLSR status is displaying as follow
>>>
>>> 2. NLSR status:
>>>
>>> mininet> a nlsrc status
>>> NLSR Status
>>> LSDB:
>>>   OriginRouter: /ndn/edu/%C1.Router/cs/a
>>>
>>>     Coordinate LSA:
>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>> SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
>>>       angle=0
>>>       radius=0
>>>
>>>     Name LSA:
>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>> SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
>>>       name=/ndn/edu/a
>>>
>>>   OriginRouter: /ndn/edu/%C1.Router/cs/b
>>>
>>> 3. I just tried running 'nfd' command for a node and it displayed
>>> 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'
>>>
>>> mininet> a nfd
>>> 1465913606.293515 FATAL: [NFD] Failed to read configuration file:
>>> /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void
>>> nfd::ConfigFile::parse(const string&, bool)]
>>> mininet>
>>>
>>> I ensured again that NFD is installed when mini-ndn is installed and the
>>> configuration is run.
>>>
>>> Not sure whether the convergence is not happening because the conf file
>>> is missing.
>>>
>>> Any help would be appreciated
>>>
>>> Thanks in advance
>>>
>>> ~Jeeva
>>>
>>>
>>> On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> Try to run just:
>>>>
>>>> sudo minindn
>>>>
>>>>
>>>> And when the command line comes up, wait for some time and check the
>>>> FIB of each node:
>>>>
>>>>
>>>> a nfd-status -b
>>>>
>>>> b nfd-status -b
>>>>
>>>> c nfd-status -b
>>>>
>>>> d nfd-status -b
>>>>
>>>>
>>>> They should all have each other prefixes (i.e. /ndn/edu/<node>) and
>>>> routers (/ndn/edu/%C1.Router/<node>).
>>>>
>>>> If not you will get the error you got - NLSR could not converge (only
>>>> if an experiment was run).
>>>>
>>>>
>>>> If they do have each other's prefixes then you can try to increase the
>>>> convergence time:
>>>>
>>>> sudo minindn --experiment=pingall --ctime 100
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>> Rajendran Jeeva <rajendrj at tcd.ie>
>>>> *Sent:* Sunday, June 12, 2016 10:33:05 AM
>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* [Mini-NDN] NLSR has not converged - Issue while running
>>>> minindn
>>>>
>>>> Hi All,
>>>>
>>>> I have installed mini-ndn as follows:
>>>>
>>>> 1. Cloned 'mini-ndn' from github
>>>> 2. $ cd mini-ndn
>>>> 3. Installed it using the command
>>>>
>>>> sudo ./install.sh -mrfti
>>>>
>>>> 4. When the above command got executed , NFD, NLSR, ndn, and
>>>> mininet got installed in the 'mini-ndn' directory(not in the home directory
>>>>
>>>> as I ran install.sh from inside mini-ndn directory )
>>>>
>>>> 5. Once the installation is completed I tried running the --Pingall experiment with
>>>>
>>>> default topology
>>>>
>>>> 6. There was an error stating 'mininet.topo module not found'(Rectified this
>>>>
>>>> problem by installing 'mininet' in the home directory)
>>>>
>>>> 7. When I ran the minindn command again, I got the following output
>>>>
>>>> rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
>>>> No results folder specified; experiment results will remain in the working directory
>>>> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
>>>> *** Creating network
>>>> *** Adding controller
>>>> *** Adding hosts:
>>>> a b c d
>>>> *** Adding switches:
>>>>
>>>> *** Adding links:
>>>> (10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
>>>> *** Configuring hosts
>>>> a b c d
>>>> Setup time: 8
>>>> *** Starting controller
>>>> c0
>>>> *** Starting 0 switches
>>>>
>>>> Loading experiment: pingall
>>>> Using 1.000000 traffic
>>>> *Waiting 60 seconds for convergence...*
>>>> ...done
>>>> *NLSR has not converged. Exiting...*
>>>> rajendrj at Jeeva:~$
>>>>
>>>> As shown in the last line, the execution exited with 'NLSR has not converged'
>>>>
>>>> ' message
>>>>
>>>> Am I missing something here ? Is this because 'mininet' is running from home directory
>>>>
>>>> but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see
>>>>
>>>> the error output?
>>>>
>>>> Please advise and help me here
>>>>
>>>> Thanks in advance,
>>>>
>>>> ~Jeeva
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160615/caf12b28/attachment.html>

From agawande at memphis.edu  Wed Jun 15 10:17:09 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Wed, 15 Jun 2016 17:17:09 +0000
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>,
	<CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>
Message-ID: <BN3PR04MB219609EE2CC48D06ECA86BC4D9550@BN3PR04MB2196.namprd04.prod.outlook.com>

So in Mini-NDN did you follow these steps to check whether ndnping works:


mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &

mininet> b ndnping -c5 /ndn/edu/a


If this does not work can you check if ndnpingserver output anything to /tmp/a/ndnpingserver or whether it is running (ps aux | grep ndndpingserver).

If it is running can you try:

mininet> a ndnping -c5 /ndn/edua


I am not sure about the NFD error, are you running NFD while you are running Mini-NDN?


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Wednesday, June 15, 2016 11:48:36 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

I tried running 'NFD' in one terminal (using sudo nfd-start) and meanwhile checked for the nfd-status in another terminal(using sudo nfd-status), and I saw the following messages in the terminal where NFD was running:

1466016269.157386 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://28] Creating transport
1466016269.157470 INFO: [FaceTable] Added face id=261 remote=fd://28 local=unix:///run/nfd.sock
1466016269.202716 INFO: [Transport] [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState UP -> FAILED
1466016269.202831 INFO: [Transport] [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState FAILED -> CLOSED
1466016269.207058 INFO: [FaceTable] Removed face id=261 remote=fd://28 local=unix:///run/nfd.sock


Jeeva

On 15 June 2016 at 17:41, Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>> wrote:
Thanks Ashlesh!

When I tried pingAll experiment today all the pings were getting timed out (no content entries in the text file; only timeout entries)

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:0
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:0
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:0
/tmp/d/ping-data/c.txt:0
rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:10
/tmp/a/ping-data/c.txt:10
/tmp/a/ping-data/d.txt:10
/tmp/b/ping-data/a.txt:10
/tmp/b/ping-data/c.txt:10
/tmp/b/ping-data/d.txt:10
/tmp/c/ping-data/a.txt:10
/tmp/c/ping-data/b.txt:10
/tmp/c/ping-data/d.txt:10
/tmp/d/ping-data/a.txt:10
/tmp/d/ping-data/b.txt:10
/tmp/d/ping-data/c.txt:10

I was running the command from only one terminal (no other terminals are open). NFD and NLSR status are getting displayed for all the nodes

I also tried manually 'ndnping' from the node 'a' to the prefix '/ndn/edu/b' , but it got timed out as well

Is there a way to track the reason behind these timeouts ?

Please advise

thanks,
Jeeva


On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

It is not expected, I think you have timeouts in those, search:

grep -c timeout /tmp/*/ping-data/*.txt


ndnping is timing out for some reason - either NFD went down during the experiment in another terminal

(you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went down on any of the node.


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Tuesday, June 14, 2016 2:48:39 PM

To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thank you for sorting out the problem.

I am using Ubuntu 14.04 LTS.

Yeah. 'nfd-status' was not working even outside the mini-ndn folder  (seems like nfd-start and stop were working, I even got 'NFD already running' message when i triggered nfd-start multiple times)

When i tried checking out the above patch in NFD folder there was 'fatal: reference not in tree' issue. So, i removed '--depth 1' part from git clone of NFD in install.sh of mini-ndn and reinstalled it

I checked out the above patch as well and ran waf configuration and installation

Then i executed both 'nfd-status' and pingall experiment and both got executed successfully with the convergence time of 120 instead of 60. Thank you so much for the help.

I just have one more query. When I executed the command 'sudo minindn --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it showed count for only few files . Is this expected ?

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:243
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:242
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:241
/tmp/d/ping-data/c.txt:0

Please advise.

Thanks,
~Jeeva



On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Hi


Some new information may have come to light, if nfd-status is not working outside Mini-NDN can you try the following patch:

https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0


To do so go to your NFD folder and do

git checkout ace83ac9384da037a36695888e829d7337ce36b0

./waf distclean

./waf configure --without-websocket

./waf

sudo ./waf install


Then try to run Mini-NDN experiment again.


And is your OS, Ubuntu 14.04?


Thanks

Ashlesh


________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>>
Sent: Tuesday, June 14, 2016 11:29:50 AM
To: Rajendran Jeeva

Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn


Can you check whether nfd-status works outside of mini-ndn?

Just do nfd-start and then do nfd-status.


Convergence depends on nfd-status as mini-ndn checks whether prefixes and routers have been installed.


> a nfd does not work because we use the a.conf file, if you do" a nfd -f a.conf &" it should work.

But the problem seems to be that nfd-status is not working (even outside of mini-ndn).


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Tuesday, June 14, 2016 9:32:55 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried running the command 'a nfd-status -b' for node 'a' and for other nodes as well. It is not displaying anything .

1. NFD status:

mininet> a nfd-status -b
mininet>


NLSR status is displaying as follow

2. NLSR status:

mininet> a nlsrc status
NLSR Status
LSDB:
  OriginRouter: /ndn/edu/%C1.Router/cs/a

    Coordinate LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
      angle=0
      radius=0

    Name LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
      name=/ndn/edu/a

  OriginRouter: /ndn/edu/%C1.Router/cs/b

3. I just tried running 'nfd' command for a node and it displayed 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'

mininet> a nfd
1465913606.293515 FATAL: [NFD] Failed to read configuration file: /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
mininet>

I ensured again that NFD is installed when mini-ndn is installed and the configuration is run.

Not sure whether the convergence is not happening because the conf file is missing.

Any help would be appreciated

Thanks in advance

~Jeeva


On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Try to run just:

sudo minindn


And when the command line comes up, wait for some time and check the FIB of each node:


a nfd-status -b

b nfd-status -b

c nfd-status -b

d nfd-status -b


They should all have each other prefixes (i.e. /ndn/edu/<node>) and routers (/ndn/edu/%C1.Router/<node>).

If not you will get the error you got - NLSR could not converge (only if an experiment was run).


If they do have each other's prefixes then you can try to increase the convergence time:

sudo minindn --experiment=pingall --ctime 100


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Sunday, June 12, 2016 10:33:05 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
Waiting 60 seconds for convergence...
...done
NLSR has not converged. Exiting...
rajendrj at Jeeva:~$


As shown in the last line, the execution exited with 'NLSR has not converged'

' message


Am I missing something here ? Is this because 'mininet' is running from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?


Please advise and help me here


Thanks in advance,

~Jeeva








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

From rajendrj at tcd.ie  Thu Jun 16 09:44:56 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Thu, 16 Jun 2016 17:44:56 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <BN3PR04MB219609EE2CC48D06ECA86BC4D9550@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>
	<CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>
	<BN3PR04MB219609EE2CC48D06ECA86BC4D9550@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAMGewCTqeHmhuL5zetSxWC3z8tmmTmGRhWevy9oqOed3d3WSfQ@mail.gmail.com>

Hi Ashlesh,

Thanks for the response.

I tried the following (sorry for the long mail)

#1 - Manual try

When I tried invoking 'ndnpingserver' followed by 'ndnping' manually for a
host as follows, ndnping received the contents and meanwhile ndnpingserver
file showed the interests that are received

//

mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &

mininet> b ndnping -c 5 /ndn/edu/a

//

Above commands worked for all the hosts

#2. - from minindn script - They seem to be not working while running from
minindn script

I replicated the above manual scenario in the code in experiment.py file ,
by replacing this line 'host.cmd("ndnpingserver /ndn/edu/" + str(host) + "
> ping-server &")' from setup module to ping module as follows:

// ndn/experiments/experiment.py

def setup(self):

........

#host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")

.......

 def ping(self, source, dest, nPings):

.......

*dest.cmd("ndnpingserver /ndn/edu/" + str(dest) + " > ping-server &")*
source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name + " >>
ping-data/" + dest.name + ".txt &")

//

as quoted in the code above I tried running ndnpingserver just before
calling ndnping client , reinstalled mini-ndn , executed pingall experiment
and the ping got content for the interests


But, executing ndnpingserver from setup module is not keeping ndnpingserver
listening (no change in ping-server file-no interests received expect for
the prefix entry)

// ndn/experiments/experiment.py

def setup(self):

........

*host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")*

.......

 def ping(self, source, dest, nPings):

.......

*#*dest.cmd("ndnpingserver /ndn/edu/" + str(dest)* + " > ping-server &")*
source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name + " >>
ping-data/" + dest.name + ".txt &")
//

when I tried with logging statements for both the scenarios, 'statusRouter'
printed our an error message for the last one (scenario where ndnpingserver
started from setup module and no content received). The error message is
shown below:


statusRouter
ERROR: Key does not exist:/tmp-identity/%16%1B%CA8/ksk-1466093584396
  /ndn/edu/%C1.Router/cs/d nexthops={faceid=261 (cost=30)}
  /ndn/edu/%C1.Router/cs/b nexthops={faceid=261 (cost=20)}
  /ndn/edu/%C1.Router/cs/c nexthops={faceid=258 (cost=0)}
  /ndn/edu/%C1.Router/cs/a nexthops={faceid=261 (cost=10)}
For the other case there is no error for statusRouter.

Please advise

Thank you!

~Jeeva


On 15 June 2016 at 18:17, Ashlesh Gawande (agawande) <agawande at memphis.edu>
wrote:

> So in Mini-NDN did you follow these steps to check whether ndnping works:
>
>
> mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &
>
> mininet> b ndnping -c5 /ndn/edu/a
>
>
> If this does not work can you check if ndnpingserver output anything to
> /tmp/a/ndnpingserver or whether it is running (ps aux | grep
> ndndpingserver).
>
> If it is running can you try:
>
> mininet> a ndnping -c5 /ndn/edua
>
> I am not sure about the NFD error, are you running NFD while you are
> running Mini-NDN?
>
>
> Ashlesh
> ------------------------------
> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
> *Sent:* Wednesday, June 15, 2016 11:48:36 AM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
> minindn
>
> I tried running 'NFD' in one terminal (using sudo nfd-start) and meanwhile
> checked for the nfd-status in another terminal(using sudo nfd-status), and
> I saw the following messages in the terminal where NFD was running:
>
> 1466016269.157386 INFO: [UnixStreamTransport]
> [id=0,local=unix:///run/nfd.sock,remote=fd://28] Creating transport
> 1466016269.157470 INFO: [FaceTable] Added face id=261 remote=fd://28
> local=unix:///run/nfd.sock
> 1466016269.202716 INFO: [Transport]
> [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState UP -> FAILED
> 1466016269.202831 INFO: [Transport]
> [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState FAILED -> CLOSED
> 1466016269.207058 INFO: [FaceTable] Removed face id=261 remote=fd://28
> local=unix:///run/nfd.sock
>
>
> Jeeva
>
> On 15 June 2016 at 17:41, Rajendran Jeeva <rajendrj at tcd.ie> wrote:
>
>> Thanks Ashlesh!
>>
>> When I tried pingAll experiment today all the pings were getting timed
>> out (no content entries in the text file; only timeout entries)
>>
>> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
>> /tmp/a/ping-data/b.txt:0
>> /tmp/a/ping-data/c.txt:0
>> /tmp/a/ping-data/d.txt:0
>> /tmp/b/ping-data/a.txt:0
>> /tmp/b/ping-data/c.txt:0
>> /tmp/b/ping-data/d.txt:0
>> /tmp/c/ping-data/a.txt:0
>> /tmp/c/ping-data/b.txt:0
>> /tmp/c/ping-data/d.txt:0
>> /tmp/d/ping-data/a.txt:0
>> /tmp/d/ping-data/b.txt:0
>> /tmp/d/ping-data/c.txt:0
>> rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
>> /tmp/a/ping-data/b.txt:10
>> /tmp/a/ping-data/c.txt:10
>> /tmp/a/ping-data/d.txt:10
>> /tmp/b/ping-data/a.txt:10
>> /tmp/b/ping-data/c.txt:10
>> /tmp/b/ping-data/d.txt:10
>> /tmp/c/ping-data/a.txt:10
>> /tmp/c/ping-data/b.txt:10
>> /tmp/c/ping-data/d.txt:10
>> /tmp/d/ping-data/a.txt:10
>> /tmp/d/ping-data/b.txt:10
>> /tmp/d/ping-data/c.txt:10
>>
>> I was running the command from only one terminal (no other terminals are
>> open). NFD and NLSR status are getting displayed for all the nodes
>>
>> I also tried manually 'ndnping' from the node 'a' to the prefix
>> '/ndn/edu/b' , but it got timed out as well
>>
>> Is there a way to track the reason behind these timeouts ?
>>
>> Please advise
>>
>> thanks,
>> Jeeva
>>
>>
>> On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> It is not expected, I think you have timeouts in those, search:
>>>
>>> grep -c timeout /tmp/*/ping-data/*.txt
>>>
>>>
>>> ndnping is timing out for some reason - either NFD went down during the
>>> experiment in another terminal
>>>
>>> (you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went
>>> down on any of the node.
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>> *Sent:* Tuesday, June 14, 2016 2:48:39 PM
>>>
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>>> minindn
>>>
>>> Hi Ashlesh,
>>>
>>> Thank you for sorting out the problem.
>>>
>>> I am using Ubuntu 14.04 LTS.
>>>
>>> Yeah. 'nfd-status' was not working even outside the mini-ndn folder
>>> (seems like nfd-start and stop were working, I even got 'NFD already
>>> running' message when i triggered nfd-start multiple times)
>>>
>>> When i tried checking out the above patch in NFD folder there was
>>> 'fatal: reference not in tree' issue. So, i removed '--depth 1' part from
>>> git clone of NFD in install.sh of mini-ndn and reinstalled it
>>>
>>> I checked out the above patch as well and ran waf configuration and
>>> installation
>>>
>>> Then i executed both 'nfd-status' and pingall experiment and both got
>>> executed successfully with the convergence time of 120 instead of 60. Thank
>>> you so much for the help.
>>>
>>> I just have one more query. When I executed the command 'sudo minindn
>>> --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it
>>> showed count for only few files . Is this expected ?
>>>
>>> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
>>> /tmp/a/ping-data/b.txt:243
>>> /tmp/a/ping-data/c.txt:0
>>> /tmp/a/ping-data/d.txt:0
>>> /tmp/b/ping-data/a.txt:0
>>> /tmp/b/ping-data/c.txt:0
>>> /tmp/b/ping-data/d.txt:0
>>> /tmp/c/ping-data/a.txt:0
>>> /tmp/c/ping-data/b.txt:242
>>> /tmp/c/ping-data/d.txt:0
>>> /tmp/d/ping-data/a.txt:0
>>> /tmp/d/ping-data/b.txt:241
>>> /tmp/d/ping-data/c.txt:0
>>>
>>> Please advise.
>>>
>>> Thanks,
>>> ~Jeeva
>>>
>>>
>>>
>>> On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> Hi
>>>>
>>>>
>>>> Some new information may have come to light, if nfd-status is not
>>>> working outside Mini-NDN can you try the following patch:
>>>>
>>>>
>>>> https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0
>>>>
>>>>
>>>> To do so go to your NFD folder and do
>>>>
>>>> git checkout ace83ac9384da037a36695888e829d7337ce36b0
>>>>
>>>> ./waf distclean
>>>>
>>>> ./waf configure --without-websocket
>>>>
>>>> ./waf
>>>>
>>>> sudo ./waf install
>>>>
>>>>
>>>> Then try to run Mini-NDN experiment again.
>>>>
>>>>
>>>> And is your OS, Ubuntu 14.04?
>>>>
>>>>
>>>> Thanks
>>>>
>>>> Ashlesh
>>>>
>>>>
>>>> ------------------------------
>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>> Ashlesh Gawande (agawande) <agawande at memphis.edu>
>>>> *Sent:* Tuesday, June 14, 2016 11:29:50 AM
>>>> *To:* Rajendran Jeeva
>>>>
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>>>> minindn
>>>>
>>>>
>>>> Can you check whether nfd-status works outside of mini-ndn?
>>>>
>>>> Just do nfd-start and then do nfd-status.
>>>>
>>>>
>>>> Convergence depends on nfd-status as mini-ndn checks whether prefixes
>>>> and routers have been installed.
>>>>
>>>>
>>>> > a nfd does not work because we use the a.conf file, if you do" a nfd
>>>> -f a.conf &" it should work.
>>>>
>>>> But the problem seems to be that nfd-status is not working (even
>>>> outside of mini-ndn).
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>>> *Sent:* Tuesday, June 14, 2016 9:32:55 AM
>>>> *To:* Ashlesh Gawande (agawande)
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>>>> minindn
>>>>
>>>> Hi Ashlesh,
>>>>
>>>> Thanks for the response.
>>>>
>>>> I tried running the command 'a nfd-status -b' for node 'a' and for
>>>> other nodes as well. It is not displaying anything .
>>>>
>>>> 1. NFD status:
>>>>
>>>> mininet> a nfd-status -b
>>>> mininet>
>>>>
>>>>
>>>> NLSR status is displaying as follow
>>>>
>>>> 2. NLSR status:
>>>>
>>>> mininet> a nlsrc status
>>>> NLSR Status
>>>> LSDB:
>>>>   OriginRouter: /ndn/edu/%C1.Router/cs/a
>>>>
>>>>     Coordinate LSA:
>>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>>> SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
>>>>       angle=0
>>>>       radius=0
>>>>
>>>>     Name LSA:
>>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>>> SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
>>>>       name=/ndn/edu/a
>>>>
>>>>   OriginRouter: /ndn/edu/%C1.Router/cs/b
>>>>
>>>> 3. I just tried running 'nfd' command for a node and it displayed
>>>> 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'
>>>>
>>>> mininet> a nfd
>>>> 1465913606.293515 FATAL: [NFD] Failed to read configuration file:
>>>> /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void
>>>> nfd::ConfigFile::parse(const string&, bool)]
>>>> mininet>
>>>>
>>>> I ensured again that NFD is installed when mini-ndn is installed and
>>>> the configuration is run.
>>>>
>>>> Not sure whether the convergence is not happening because the conf file
>>>> is missing.
>>>>
>>>> Any help would be appreciated
>>>>
>>>> Thanks in advance
>>>>
>>>> ~Jeeva
>>>>
>>>>
>>>> On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> Try to run just:
>>>>>
>>>>> sudo minindn
>>>>>
>>>>>
>>>>> And when the command line comes up, wait for some time and check the
>>>>> FIB of each node:
>>>>>
>>>>>
>>>>> a nfd-status -b
>>>>>
>>>>> b nfd-status -b
>>>>>
>>>>> c nfd-status -b
>>>>>
>>>>> d nfd-status -b
>>>>>
>>>>>
>>>>> They should all have each other prefixes (i.e. /ndn/edu/<node>) and
>>>>> routers (/ndn/edu/%C1.Router/<node>).
>>>>>
>>>>> If not you will get the error you got - NLSR could not converge (only
>>>>> if an experiment was run).
>>>>>
>>>>>
>>>>> If they do have each other's prefixes then you can try to increase the
>>>>> convergence time:
>>>>>
>>>>> sudo minindn --experiment=pingall --ctime 100
>>>>>
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>> Rajendran Jeeva <rajendrj at tcd.ie>
>>>>> *Sent:* Sunday, June 12, 2016 10:33:05 AM
>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* [Mini-NDN] NLSR has not converged - Issue while running
>>>>> minindn
>>>>>
>>>>> Hi All,
>>>>>
>>>>> I have installed mini-ndn as follows:
>>>>>
>>>>> 1. Cloned 'mini-ndn' from github
>>>>> 2. $ cd mini-ndn
>>>>> 3. Installed it using the command
>>>>>
>>>>> sudo ./install.sh -mrfti
>>>>>
>>>>> 4. When the above command got executed , NFD, NLSR, ndn, and
>>>>> mininet got installed in the 'mini-ndn' directory(not in the home directory
>>>>>
>>>>> as I ran install.sh from inside mini-ndn directory )
>>>>>
>>>>> 5. Once the installation is completed I tried running the --Pingall experiment with
>>>>>
>>>>> default topology
>>>>>
>>>>> 6. There was an error stating 'mininet.topo module not found'(Rectified this
>>>>>
>>>>> problem by installing 'mininet' in the home directory)
>>>>>
>>>>> 7. When I ran the minindn command again, I got the following output
>>>>>
>>>>> rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
>>>>> No results folder specified; experiment results will remain in the working directory
>>>>> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
>>>>> *** Creating network
>>>>> *** Adding controller
>>>>> *** Adding hosts:
>>>>> a b c d
>>>>> *** Adding switches:
>>>>>
>>>>> *** Adding links:
>>>>> (10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
>>>>> *** Configuring hosts
>>>>> a b c d
>>>>> Setup time: 8
>>>>> *** Starting controller
>>>>> c0
>>>>> *** Starting 0 switches
>>>>>
>>>>> Loading experiment: pingall
>>>>> Using 1.000000 traffic
>>>>> *Waiting 60 seconds for convergence...*
>>>>> ...done
>>>>> *NLSR has not converged. Exiting...*
>>>>> rajendrj at Jeeva:~$
>>>>>
>>>>> As shown in the last line, the execution exited with 'NLSR has not converged'
>>>>>
>>>>> ' message
>>>>>
>>>>> Am I missing something here ? Is this because 'mininet' is running from home directory
>>>>>
>>>>> but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see
>>>>>
>>>>> the error output?
>>>>>
>>>>> Please advise and help me here
>>>>>
>>>>> Thanks in advance,
>>>>>
>>>>> ~Jeeva
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160616/ca890781/attachment.html>

From agawande at memphis.edu  Fri Jun 17 09:57:41 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 17 Jun 2016 16:57:41 +0000
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <CAMGewCTqeHmhuL5zetSxWC3z8tmmTmGRhWevy9oqOed3d3WSfQ@mail.gmail.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>
	<CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>
	<BN3PR04MB219609EE2CC48D06ECA86BC4D9550@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAMGewCTqeHmhuL5zetSxWC3z8tmmTmGRhWevy9oqOed3d3WSfQ@mail.gmail.com>
Message-ID: <SN2PR04MB220561FA14E4E66C7F576FEAD9560@SN2PR04MB2205.namprd04.prod.outlook.com>

I am not sure why ndnpingserver won't work from setup.


Were the ndnpingservers running while the experiment ran or did they quit (ps aux | grep ndnpingserver) when you start them from setup?


Maybe in setup try:

           print(host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &"))


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Thursday, June 16, 2016 11:44:56 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried the following (sorry for the long mail)

#1 - Manual try

When I tried invoking 'ndnpingserver' followed by 'ndnping' manually for a host as follows, ndnping received the contents and meanwhile ndnpingserver file showed the interests that are received

//

mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &

mininet> b ndnping -c 5 /ndn/edu/a

//

Above commands worked for all the hosts

#2. - from minindn script - They seem to be not working while running from minindn script

I replicated the above manual scenario in the code in experiment.py file , by replacing this line 'host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")' from setup module to ping module as follows:

// ndn/experiments/experiment.py

def setup(self):

........

#host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")

.......

 def ping(self, source, dest, nPings):

.......

dest.cmd("ndnpingserver /ndn/edu/" + str(dest) + " > ping-server &")
source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name<http://dest.name> + " >> ping-data/" + dest.name<http://dest.name> + ".txt &")

//

as quoted in the code above I tried running ndnpingserver just before calling ndnping client , reinstalled mini-ndn , executed pingall experiment and the ping got content for the interests


But, executing ndnpingserver from setup module is not keeping ndnpingserver listening (no change in ping-server file-no interests received expect for the prefix entry)

// ndn/experiments/experiment.py

def setup(self):

........

host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")

.......

 def ping(self, source, dest, nPings):

.......

#dest.cmd("ndnpingserver /ndn/edu/" + str(dest) + " > ping-server &")
source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name<http://dest.name> + " >> ping-data/" + dest.name<http://dest.name> + ".txt &")

//

when I tried with logging statements for both the scenarios, 'statusRouter' printed our an error message for the last one (scenario where ndnpingserver started from setup module and no content received). The error message is shown below:


statusRouter
ERROR: Key does not exist:/tmp-identity/%16%1B%CA8/ksk-1466093584396
  /ndn/edu/%C1.Router/cs/d nexthops={faceid=261 (cost=30)}
  /ndn/edu/%C1.Router/cs/b nexthops={faceid=261 (cost=20)}
  /ndn/edu/%C1.Router/cs/c nexthops={faceid=258 (cost=0)}
  /ndn/edu/%C1.Router/cs/a nexthops={faceid=261 (cost=10)}

For the other case there is no error for statusRouter.

Please advise

Thank you!

~Jeeva


On 15 June 2016 at 18:17, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

So in Mini-NDN did you follow these steps to check whether ndnping works:


mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &

mininet> b ndnping -c5 /ndn/edu/a


If this does not work can you check if ndnpingserver output anything to /tmp/a/ndnpingserver or whether it is running (ps aux | grep ndndpingserver).

If it is running can you try:

mininet> a ndnping -c5 /ndn/edua


I am not sure about the NFD error, are you running NFD while you are running Mini-NDN?


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Wednesday, June 15, 2016 11:48:36 AM

To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

I tried running 'NFD' in one terminal (using sudo nfd-start) and meanwhile checked for the nfd-status in another terminal(using sudo nfd-status), and I saw the following messages in the terminal where NFD was running:

1466016269.157386 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://28] Creating transport
1466016269.157470 INFO: [FaceTable] Added face id=261 remote=fd://28 local=unix:///run/nfd.sock
1466016269.202716 INFO: [Transport] [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState UP -> FAILED
1466016269.202831 INFO: [Transport] [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState FAILED -> CLOSED
1466016269.207058 INFO: [FaceTable] Removed face id=261 remote=fd://28 local=unix:///run/nfd.sock


Jeeva

On 15 June 2016 at 17:41, Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>> wrote:
Thanks Ashlesh!

When I tried pingAll experiment today all the pings were getting timed out (no content entries in the text file; only timeout entries)

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:0
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:0
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:0
/tmp/d/ping-data/c.txt:0
rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:10
/tmp/a/ping-data/c.txt:10
/tmp/a/ping-data/d.txt:10
/tmp/b/ping-data/a.txt:10
/tmp/b/ping-data/c.txt:10
/tmp/b/ping-data/d.txt:10
/tmp/c/ping-data/a.txt:10
/tmp/c/ping-data/b.txt:10
/tmp/c/ping-data/d.txt:10
/tmp/d/ping-data/a.txt:10
/tmp/d/ping-data/b.txt:10
/tmp/d/ping-data/c.txt:10

I was running the command from only one terminal (no other terminals are open). NFD and NLSR status are getting displayed for all the nodes

I also tried manually 'ndnping' from the node 'a' to the prefix '/ndn/edu/b' , but it got timed out as well

Is there a way to track the reason behind these timeouts ?

Please advise

thanks,
Jeeva


On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

It is not expected, I think you have timeouts in those, search:

grep -c timeout /tmp/*/ping-data/*.txt


ndnping is timing out for some reason - either NFD went down during the experiment in another terminal

(you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went down on any of the node.


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Tuesday, June 14, 2016 2:48:39 PM

To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thank you for sorting out the problem.

I am using Ubuntu 14.04 LTS.

Yeah. 'nfd-status' was not working even outside the mini-ndn folder  (seems like nfd-start and stop were working, I even got 'NFD already running' message when i triggered nfd-start multiple times)

When i tried checking out the above patch in NFD folder there was 'fatal: reference not in tree' issue. So, i removed '--depth 1' part from git clone of NFD in install.sh of mini-ndn and reinstalled it

I checked out the above patch as well and ran waf configuration and installation

Then i executed both 'nfd-status' and pingall experiment and both got executed successfully with the convergence time of 120 instead of 60. Thank you so much for the help.

I just have one more query. When I executed the command 'sudo minindn --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it showed count for only few files . Is this expected ?

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:243
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:242
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:241
/tmp/d/ping-data/c.txt:0

Please advise.

Thanks,
~Jeeva



On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Hi


Some new information may have come to light, if nfd-status is not working outside Mini-NDN can you try the following patch:

https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0


To do so go to your NFD folder and do

git checkout ace83ac9384da037a36695888e829d7337ce36b0

./waf distclean

./waf configure --without-websocket

./waf

sudo ./waf install


Then try to run Mini-NDN experiment again.


And is your OS, Ubuntu 14.04?


Thanks

Ashlesh


________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>>
Sent: Tuesday, June 14, 2016 11:29:50 AM
To: Rajendran Jeeva

Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn


Can you check whether nfd-status works outside of mini-ndn?

Just do nfd-start and then do nfd-status.


Convergence depends on nfd-status as mini-ndn checks whether prefixes and routers have been installed.


> a nfd does not work because we use the a.conf file, if you do" a nfd -f a.conf &" it should work.

But the problem seems to be that nfd-status is not working (even outside of mini-ndn).


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Tuesday, June 14, 2016 9:32:55 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried running the command 'a nfd-status -b' for node 'a' and for other nodes as well. It is not displaying anything .

1. NFD status:

mininet> a nfd-status -b
mininet>


NLSR status is displaying as follow

2. NLSR status:

mininet> a nlsrc status
NLSR Status
LSDB:
  OriginRouter: /ndn/edu/%C1.Router/cs/a

    Coordinate LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
      angle=0
      radius=0

    Name LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
      name=/ndn/edu/a

  OriginRouter: /ndn/edu/%C1.Router/cs/b

3. I just tried running 'nfd' command for a node and it displayed 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'

mininet> a nfd
1465913606.293515 FATAL: [NFD] Failed to read configuration file: /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
mininet>

I ensured again that NFD is installed when mini-ndn is installed and the configuration is run.

Not sure whether the convergence is not happening because the conf file is missing.

Any help would be appreciated

Thanks in advance

~Jeeva


On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Try to run just:

sudo minindn


And when the command line comes up, wait for some time and check the FIB of each node:


a nfd-status -b

b nfd-status -b

c nfd-status -b

d nfd-status -b


They should all have each other prefixes (i.e. /ndn/edu/<node>) and routers (/ndn/edu/%C1.Router/<node>).

If not you will get the error you got - NLSR could not converge (only if an experiment was run).


If they do have each other's prefixes then you can try to increase the convergence time:

sudo minindn --experiment=pingall --ctime 100


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Sunday, June 12, 2016 10:33:05 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
Waiting 60 seconds for convergence...
...done
NLSR has not converged. Exiting...
rajendrj at Jeeva:~$


As shown in the last line, the execution exited with 'NLSR has not converged'

' message


Am I missing something here ? Is this because 'mininet' is running from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?


Please advise and help me here


Thanks in advance,

~Jeeva









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

From agawande at memphis.edu  Thu Jun 23 09:41:32 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 23 Jun 2016 16:41:32 +0000
Subject: [Mini-NDN] NLSR
In-Reply-To: <CAOeyPyTcmuHO_1e8PnhSPha7S2NJmgZF0+DucugKfObinUPRhA@mail.gmail.com>
References: <CAOeyPySKEvTqKoodMR6+bCJ2ZB9DUCdji97H6m1dnGsuUTYkuw@mail.gmail.com>
	<BN3PR04MB21963EC21967B1C49C901839D9550@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAOeyPyTMGy9C+nJfnkCJGnsc6z839S6V5QiHr6Kd4GVR5GaZ_Q@mail.gmail.com>
	<BN3PR04MB2196212CE19452C66A02E5D5D92B0@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAOeyPyTcmuHO_1e8PnhSPha7S2NJmgZF0+DucugKfObinUPRhA@mail.gmail.com>
Message-ID: <BN3PR04MB21962E60D0B70AA6EFF6AA36D92D0@BN3PR04MB2196.namprd04.prod.outlook.com>

It should show the FIB. Can you make sure that NFD is running?

In a new terminal do:

ps aux | grep "sudo nfd"


If NFD is running then try to run NFD without Mini-NDN and see if nfd-status works.


If NFD status is not working you might be affected by this bug in NFD:

http://redmine.named-data.net/issues/3650 (the site seems down right now, but should be up soon).

So update your NFD by doing a git pull (since there's been a recent fix) and then compile and install it again (./waf, sudo ./waf install).


Try to run Mini-NDN and do nfd-status again.


Yes you need ndn-tools installed if you want to run the verification (https://github.com/named-data/mini-ndn/blob/master/INSTALL.md).


Security patch can be found at:

http://gerrit.named-data.net/#/c/2873/


You can install it by clicking on downloads and then selecting any one of the git commands you favor.


And then install it using sudo ./install.sh -i

Then do sudo minndn --help to see the security option and run using that.


You can see how to setup up any topology in Mini-NDN here:

https://github.com/named-data/mini-ndn/blob/master/docs/CONFIG.md


Mini-NDN uses the version of NFD and NLSR installed in the system.

So you can change the code in NLSR itself, compile and install it and then run Mini-NDN.


NLSR uses nsync for LSDB synchronization - which is basically chronosync.

So you should start by reading on Chronosync (http://named-data.net/publications/chronosync/)

https://github.com/named-data/ChronoSync


https://github.com/named-data/NLSR/tree/master/nsync


Ashlesh


________________________________
From: Tanusree Chatterjee <tnsr.chatterjee at gmail.com>
Sent: Thursday, June 23, 2016 4:06:59 AM
To: Ashlesh Gawande (agawande)
Subject: Re: NLSR

Hi,

There is a security patch here which sets NLSR security in mini-ndn which sets up the NLSR security automatically? What I need to configure here after installing mini-ndn?

I have installed the mini-ndn. What about the ndn-tools? I have to install the ndn tools also? I have seen the video you shared. I have tried to run mini-ndn. It shows the following.

sudo minindn
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 9
*** Starting controller
c0
*** Starting 0 switches

*** Starting CLI:

While run

mininet> a nfd-status -b

It shows nothing. Just

mininet>

It should show the FIB?

If I want to run a simple experiment where 5 hosts connecting together and exchanges interest and data to update some change in LSDB, can I do it here? Where I should write/edit the code?

I had surveyed the LSDB synchronization part of NLSR. I want to suggest some modification there to reduce the message exchange overhead and also to enhance the security in LSDB. Can you suggest me where should I start from in theory and in coding section? Which section of code I should visit thoroghly to check the LSDB syncronization process.

On Tue, Jun 21, 2016 at 8:55 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No it won't be  a problem.


You can simply install mininet first by:

git clone --depth 1 https://github.com/mininet/mininet

cd mininet

sudo ./util/install.sh -fnv


Then you can install mini-ndn

git clone --depth 1 https://github.com/named-data/mini-ndn


cd mini-ndn

sudo ./install.sh -i


Further information on mininet and mini-ndn:

https://www.youtube.com/watch?v=UxHPqaUwefg&feature=youtu.be


Ashlesh

________________________________
From: Tanusree Chatterjee <tnsr.chatterjee at gmail.com<mailto:tnsr.chatterjee at gmail.com>>
Sent: Tuesday, June 21, 2016 12:04:40 AM
To: Ashlesh Gawande (agawande)
Subject: Re: NLSR

Ashlesh,

I have installed NLSR already in my machine earlier and so NFD is also installed. Will it be any problem to install Mini-NDN now in Ubuntu 14.04?

On Wed, Jun 15, 2016 at 8:12 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Those are NLSRs neighbors. You need to configure other nodes running NLSR and make them neighbors.


But a better way would be to use Mini-NDN

https://github.com/named-data/mini-ndn
You should be able to find all the documentation in docs.

There is also a security patch here which sets NLSR security for you: http://gerrit.named-data.net/#/c/2873/

on Mini-NDN.


It does the setup for you and runs multiple NLSR on a single machine so you don't need multiple nodes.


NDNSim NLSR is still being prepared and might take a while.


Mini-NDN is an emulator - i.e. it runs actual instances of NFD, NLSR etc. so it does not scale as good. Scaling also depends on CPU rather than RAM. (~100 nodes max scaling on 32 core machine).

NDNSim is a simulator - i.e. it simulates NFD etc and scaling is much better. Scaling depends on RAM.


So if you need scaling in your experiment use NDNSim.

(Very high number of nodes can be simulated.)


I would suggest you read the following papers:

http://named-data.net/publications/nlsr-final/


http://named-data.net/publications/techreports/ndn-0037-1-nlsr/


<http://named-data.net/publications/techreports/ndn-0037-1-nlsr/>You will have to thoroughly understand security in NDN (NLSR) before implementing but you can look at the Mini-NDN patch as to how the security is actually done.

Also you can look at this:

http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html


Ashlesh

________________________________
From: Tanusree Chatterjee <tnsr.chatterjee at gmail.com<mailto:tnsr.chatterjee at gmail.com>>
Sent: Wednesday, June 15, 2016 1:34:03 AM
To: Ashlesh Gawande (agawande)
Subject: NLSR

Hi Ashlesh,

After I run the nlsr now, it is not showing anything in the terminal and crearing a log file which contents the following.

20160615113331480 WARN: [FaceController] Could not convert udp://mira.cs.memphis.edu<http://mira.cs.memphis.edu> to canonical form: Hostname resolution timed out

Can you tell me what is the significance of the above number in the file? And what for the warning is coming? You have commented few lines to disable the security. What if I want to keep the security enable? How and hat I need to configure then?

Which part in NDN you are currently working on? I am new to NDN and currrently I am doing my research to understand the NLSR where I want to propose some changes to enhance its security and also to reduce the overheads of the protocol in few area. Can you suggest me in which sections of the codes I need to concentrate and start working to do the same in future? What research is going on currently on NDNsim? How the simulator can be used in my work? Do I need to built up an app for it? I guess Anil is working to port NLSR in NDNsim. May be in future NLSR will not be needed to install separately.

However, thanks a lot for all your help till now.

-- Regards,
Tanusree Chatterjee




--
Tanusree Chatterjee




--
Tanusree Chatterjee
M:9836337175
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160623/28f8bd4c/attachment.html>

From rajendrj at tcd.ie  Thu Jun 23 15:17:18 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Thu, 23 Jun 2016 23:17:18 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <SN2PR04MB220561FA14E4E66C7F576FEAD9560@SN2PR04MB2205.namprd04.prod.outlook.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>
	<CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>
	<BN3PR04MB219609EE2CC48D06ECA86BC4D9550@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCTqeHmhuL5zetSxWC3z8tmmTmGRhWevy9oqOed3d3WSfQ@mail.gmail.com>
	<SN2PR04MB220561FA14E4E66C7F576FEAD9560@SN2PR04MB2205.namprd04.prod.outlook.com>
Message-ID: <CAMGewCS_yiYHU4xf0V3eByzmu-9TLRbJSGDJa3NEJzh2J+BDsw@mail.gmail.com>

Hi Ashlesh,

The above scenario is being intermittent now. Sometimes ndnpingserver
process from setup is running without being killed and in other cases the
process is getting killed. I noticed the above by doing 'grep' for
ndnpingserver.

Upon printing ndnpinserver command using 'print(host.cmd.....' , a process
ID is being printed and this ID is sometimes getting listed in 'ps aux'
(where the ndnpingserver keeps running) and sometimes not getting listed
(where the server is killed)

I am still looking into it.

Just by putting the ndnpingserver in ping module, I started working on
mini-ndn for my project. I like the way mini-ndn is framed.

Meanwhile, Is there is a packet dissector like Wireshark that works for
minindn ? (I am in need of looking into the packets that get generated out
of communication between NDN nodes in mini-ndn. Is it possible?)

Please advise

thanks,
Jeeva

On 17 June 2016 at 17:57, Ashlesh Gawande (agawande) <agawande at memphis.edu>
wrote:

> I am not sure why ndnpingserver won't work from setup.
>
>
> Were the ndnpingservers running while the experiment ran or did they quit
> (ps aux | grep ndnpingserver) when you start them from setup?
>
>
> Maybe in setup try:
>
>            print(host.cmd("ndnpingserver /ndn/edu/" + str(host) + " >
> ping-server &"))
>
>
> Ashlesh
> ------------------------------
> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
> *Sent:* Thursday, June 16, 2016 11:44:56 AM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
> minindn
>
> Hi Ashlesh,
>
> Thanks for the response.
>
> I tried the following (sorry for the long mail)
>
> #1 - Manual try
>
> When I tried invoking 'ndnpingserver' followed by 'ndnping' manually for a
> host as follows, ndnping received the contents and meanwhile ndnpingserver
> file showed the interests that are received
>
> //
>
> mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &
>
> mininet> b ndnping -c 5 /ndn/edu/a
>
> //
>
> Above commands worked for all the hosts
>
> #2. - from minindn script - They seem to be not working while running from
> minindn script
>
> I replicated the above manual scenario in the code in experiment.py file ,
> by replacing this line 'host.cmd("ndnpingserver /ndn/edu/" + str(host) + "
> > ping-server &")' from setup module to ping module as follows:
>
> // ndn/experiments/experiment.py
>
> def setup(self):
>
> ........
>
> #host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")
>
> .......
>
>  def ping(self, source, dest, nPings):
>
> .......
>
> *dest.cmd("ndnpingserver /ndn/edu/" + str(dest) + " > ping-server &")*
> source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name + "
> >> ping-data/" + dest.name + ".txt &")
>
> //
>
> as quoted in the code above I tried running ndnpingserver just before
> calling ndnping client , reinstalled mini-ndn , executed pingall experiment
> and the ping got content for the interests
>
>
> But, executing ndnpingserver from setup module is not keeping
> ndnpingserver listening (no change in ping-server file-no interests
> received expect for the prefix entry)
>
> // ndn/experiments/experiment.py
>
> def setup(self):
>
> ........
>
> *host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")*
>
> .......
>
>  def ping(self, source, dest, nPings):
>
> .......
>
> *#*dest.cmd("ndnpingserver /ndn/edu/" + str(dest)* + " > ping-server &")*
> source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name + "
> >> ping-data/" + dest.name + ".txt &")
> //
>
> when I tried with logging statements for both the scenarios,
> 'statusRouter' printed our an error message for the last one (scenario
> where ndnpingserver started from setup module and no content received). The
> error message is shown below:
>
>
> statusRouter
> ERROR: Key does not exist:/tmp-identity/%16%1B%CA8/ksk-1466093584396
>   /ndn/edu/%C1.Router/cs/d nexthops={faceid=261 (cost=30)}
>   /ndn/edu/%C1.Router/cs/b nexthops={faceid=261 (cost=20)}
>   /ndn/edu/%C1.Router/cs/c nexthops={faceid=258 (cost=0)}
>   /ndn/edu/%C1.Router/cs/a nexthops={faceid=261 (cost=10)}
> For the other case there is no error for statusRouter.
>
> Please advise
>
> Thank you!
>
> ~Jeeva
>
>
> On 15 June 2016 at 18:17, Ashlesh Gawande (agawande) <agawande at memphis.edu
> > wrote:
>
>> So in Mini-NDN did you follow these steps to check whether ndnping works:
>>
>>
>> mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &
>>
>> mininet> b ndnping -c5 /ndn/edu/a
>>
>>
>> If this does not work can you check if ndnpingserver output anything to
>> /tmp/a/ndnpingserver or whether it is running (ps aux | grep
>> ndndpingserver).
>>
>> If it is running can you try:
>>
>> mininet> a ndnping -c5 /ndn/edua
>>
>> I am not sure about the NFD error, are you running NFD while you are
>> running Mini-NDN?
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>> *Sent:* Wednesday, June 15, 2016 11:48:36 AM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>> minindn
>>
>> I tried running 'NFD' in one terminal (using sudo nfd-start) and
>> meanwhile checked for the nfd-status in another terminal(using sudo
>> nfd-status), and I saw the following messages in the terminal where NFD was
>> running:
>>
>> 1466016269.157386 INFO: [UnixStreamTransport]
>> [id=0,local=unix:///run/nfd.sock,remote=fd://28] Creating transport
>> 1466016269.157470 INFO: [FaceTable] Added face id=261 remote=fd://28
>> local=unix:///run/nfd.sock
>> 1466016269.202716 INFO: [Transport]
>> [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState UP -> FAILED
>> 1466016269.202831 INFO: [Transport]
>> [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState FAILED -> CLOSED
>> 1466016269.207058 INFO: [FaceTable] Removed face id=261 remote=fd://28
>> local=unix:///run/nfd.sock
>>
>>
>> Jeeva
>>
>> On 15 June 2016 at 17:41, Rajendran Jeeva <rajendrj at tcd.ie> wrote:
>>
>>> Thanks Ashlesh!
>>>
>>> When I tried pingAll experiment today all the pings were getting timed
>>> out (no content entries in the text file; only timeout entries)
>>>
>>> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
>>> /tmp/a/ping-data/b.txt:0
>>> /tmp/a/ping-data/c.txt:0
>>> /tmp/a/ping-data/d.txt:0
>>> /tmp/b/ping-data/a.txt:0
>>> /tmp/b/ping-data/c.txt:0
>>> /tmp/b/ping-data/d.txt:0
>>> /tmp/c/ping-data/a.txt:0
>>> /tmp/c/ping-data/b.txt:0
>>> /tmp/c/ping-data/d.txt:0
>>> /tmp/d/ping-data/a.txt:0
>>> /tmp/d/ping-data/b.txt:0
>>> /tmp/d/ping-data/c.txt:0
>>> rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
>>> /tmp/a/ping-data/b.txt:10
>>> /tmp/a/ping-data/c.txt:10
>>> /tmp/a/ping-data/d.txt:10
>>> /tmp/b/ping-data/a.txt:10
>>> /tmp/b/ping-data/c.txt:10
>>> /tmp/b/ping-data/d.txt:10
>>> /tmp/c/ping-data/a.txt:10
>>> /tmp/c/ping-data/b.txt:10
>>> /tmp/c/ping-data/d.txt:10
>>> /tmp/d/ping-data/a.txt:10
>>> /tmp/d/ping-data/b.txt:10
>>> /tmp/d/ping-data/c.txt:10
>>>
>>> I was running the command from only one terminal (no other terminals are
>>> open). NFD and NLSR status are getting displayed for all the nodes
>>>
>>> I also tried manually 'ndnping' from the node 'a' to the prefix
>>> '/ndn/edu/b' , but it got timed out as well
>>>
>>> Is there a way to track the reason behind these timeouts ?
>>>
>>> Please advise
>>>
>>> thanks,
>>> Jeeva
>>>
>>>
>>> On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> It is not expected, I think you have timeouts in those, search:
>>>>
>>>> grep -c timeout /tmp/*/ping-data/*.txt
>>>>
>>>>
>>>> ndnping is timing out for some reason - either NFD went down during the
>>>> experiment in another terminal
>>>>
>>>> (you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went
>>>> down on any of the node.
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>>> *Sent:* Tuesday, June 14, 2016 2:48:39 PM
>>>>
>>>> *To:* Ashlesh Gawande (agawande)
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>>>> minindn
>>>>
>>>> Hi Ashlesh,
>>>>
>>>> Thank you for sorting out the problem.
>>>>
>>>> I am using Ubuntu 14.04 LTS.
>>>>
>>>> Yeah. 'nfd-status' was not working even outside the mini-ndn folder
>>>> (seems like nfd-start and stop were working, I even got 'NFD already
>>>> running' message when i triggered nfd-start multiple times)
>>>>
>>>> When i tried checking out the above patch in NFD folder there was
>>>> 'fatal: reference not in tree' issue. So, i removed '--depth 1' part from
>>>> git clone of NFD in install.sh of mini-ndn and reinstalled it
>>>>
>>>> I checked out the above patch as well and ran waf configuration and
>>>> installation
>>>>
>>>> Then i executed both 'nfd-status' and pingall experiment and both got
>>>> executed successfully with the convergence time of 120 instead of 60. Thank
>>>> you so much for the help.
>>>>
>>>> I just have one more query. When I executed the command 'sudo minindn
>>>> --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it
>>>> showed count for only few files . Is this expected ?
>>>>
>>>> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
>>>> /tmp/a/ping-data/b.txt:243
>>>> /tmp/a/ping-data/c.txt:0
>>>> /tmp/a/ping-data/d.txt:0
>>>> /tmp/b/ping-data/a.txt:0
>>>> /tmp/b/ping-data/c.txt:0
>>>> /tmp/b/ping-data/d.txt:0
>>>> /tmp/c/ping-data/a.txt:0
>>>> /tmp/c/ping-data/b.txt:242
>>>> /tmp/c/ping-data/d.txt:0
>>>> /tmp/d/ping-data/a.txt:0
>>>> /tmp/d/ping-data/b.txt:241
>>>> /tmp/d/ping-data/c.txt:0
>>>>
>>>> Please advise.
>>>>
>>>> Thanks,
>>>> ~Jeeva
>>>>
>>>>
>>>>
>>>> On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> Hi
>>>>>
>>>>>
>>>>> Some new information may have come to light, if nfd-status is not
>>>>> working outside Mini-NDN can you try the following patch:
>>>>>
>>>>>
>>>>> https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0
>>>>>
>>>>>
>>>>> To do so go to your NFD folder and do
>>>>>
>>>>> git checkout ace83ac9384da037a36695888e829d7337ce36b0
>>>>>
>>>>> ./waf distclean
>>>>>
>>>>> ./waf configure --without-websocket
>>>>>
>>>>> ./waf
>>>>>
>>>>> sudo ./waf install
>>>>>
>>>>>
>>>>> Then try to run Mini-NDN experiment again.
>>>>>
>>>>>
>>>>> And is your OS, Ubuntu 14.04?
>>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> Ashlesh
>>>>>
>>>>>
>>>>> ------------------------------
>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>> Ashlesh Gawande (agawande) <agawande at memphis.edu>
>>>>> *Sent:* Tuesday, June 14, 2016 11:29:50 AM
>>>>> *To:* Rajendran Jeeva
>>>>>
>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while
>>>>> running minindn
>>>>>
>>>>>
>>>>> Can you check whether nfd-status works outside of mini-ndn?
>>>>>
>>>>> Just do nfd-start and then do nfd-status.
>>>>>
>>>>>
>>>>> Convergence depends on nfd-status as mini-ndn checks whether prefixes
>>>>> and routers have been installed.
>>>>>
>>>>>
>>>>> > a nfd does not work because we use the a.conf file, if you do" a nfd
>>>>> -f a.conf &" it should work.
>>>>>
>>>>> But the problem seems to be that nfd-status is not working (even
>>>>> outside of mini-ndn).
>>>>>
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>>>> *Sent:* Tuesday, June 14, 2016 9:32:55 AM
>>>>> *To:* Ashlesh Gawande (agawande)
>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while
>>>>> running minindn
>>>>>
>>>>> Hi Ashlesh,
>>>>>
>>>>> Thanks for the response.
>>>>>
>>>>> I tried running the command 'a nfd-status -b' for node 'a' and for
>>>>> other nodes as well. It is not displaying anything .
>>>>>
>>>>> 1. NFD status:
>>>>>
>>>>> mininet> a nfd-status -b
>>>>> mininet>
>>>>>
>>>>>
>>>>> NLSR status is displaying as follow
>>>>>
>>>>> 2. NLSR status:
>>>>>
>>>>> mininet> a nlsrc status
>>>>> NLSR Status
>>>>> LSDB:
>>>>>   OriginRouter: /ndn/edu/%C1.Router/cs/a
>>>>>
>>>>>     Coordinate LSA:
>>>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>>>> SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
>>>>>       angle=0
>>>>>       radius=0
>>>>>
>>>>>     Name LSA:
>>>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>>>> SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
>>>>>       name=/ndn/edu/a
>>>>>
>>>>>   OriginRouter: /ndn/edu/%C1.Router/cs/b
>>>>>
>>>>> 3. I just tried running 'nfd' command for a node and it displayed
>>>>> 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'
>>>>>
>>>>> mininet> a nfd
>>>>> 1465913606.293515 FATAL: [NFD] Failed to read configuration file:
>>>>> /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void
>>>>> nfd::ConfigFile::parse(const string&, bool)]
>>>>> mininet>
>>>>>
>>>>> I ensured again that NFD is installed when mini-ndn is installed and
>>>>> the configuration is run.
>>>>>
>>>>> Not sure whether the convergence is not happening because the conf
>>>>> file is missing.
>>>>>
>>>>> Any help would be appreciated
>>>>>
>>>>> Thanks in advance
>>>>>
>>>>> ~Jeeva
>>>>>
>>>>>
>>>>> On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <
>>>>> agawande at memphis.edu> wrote:
>>>>>
>>>>>> Try to run just:
>>>>>>
>>>>>> sudo minindn
>>>>>>
>>>>>>
>>>>>> And when the command line comes up, wait for some time and check the
>>>>>> FIB of each node:
>>>>>>
>>>>>>
>>>>>> a nfd-status -b
>>>>>>
>>>>>> b nfd-status -b
>>>>>>
>>>>>> c nfd-status -b
>>>>>>
>>>>>> d nfd-status -b
>>>>>>
>>>>>>
>>>>>> They should all have each other prefixes (i.e. /ndn/edu/<node>) and
>>>>>> routers (/ndn/edu/%C1.Router/<node>).
>>>>>>
>>>>>> If not you will get the error you got - NLSR could not converge (only
>>>>>> if an experiment was run).
>>>>>>
>>>>>>
>>>>>> If they do have each other's prefixes then you can try to increase
>>>>>> the convergence time:
>>>>>>
>>>>>> sudo minindn --experiment=pingall --ctime 100
>>>>>>
>>>>>>
>>>>>> Ashlesh
>>>>>> ------------------------------
>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>>> Rajendran Jeeva <rajendrj at tcd.ie>
>>>>>> *Sent:* Sunday, June 12, 2016 10:33:05 AM
>>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>>> *Subject:* [Mini-NDN] NLSR has not converged - Issue while running
>>>>>> minindn
>>>>>>
>>>>>> Hi All,
>>>>>>
>>>>>> I have installed mini-ndn as follows:
>>>>>>
>>>>>> 1. Cloned 'mini-ndn' from github
>>>>>> 2. $ cd mini-ndn
>>>>>> 3. Installed it using the command
>>>>>>
>>>>>> sudo ./install.sh -mrfti
>>>>>>
>>>>>> 4. When the above command got executed , NFD, NLSR, ndn, and
>>>>>> mininet got installed in the 'mini-ndn' directory(not in the home directory
>>>>>>
>>>>>> as I ran install.sh from inside mini-ndn directory )
>>>>>>
>>>>>> 5. Once the installation is completed I tried running the --Pingall experiment with
>>>>>>
>>>>>> default topology
>>>>>>
>>>>>> 6. There was an error stating 'mininet.topo module not found'(Rectified this
>>>>>>
>>>>>> problem by installing 'mininet' in the home directory)
>>>>>>
>>>>>> 7. When I ran the minindn command again, I got the following output
>>>>>>
>>>>>> rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
>>>>>> No results folder specified; experiment results will remain in the working directory
>>>>>> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
>>>>>> *** Creating network
>>>>>> *** Adding controller
>>>>>> *** Adding hosts:
>>>>>> a b c d
>>>>>> *** Adding switches:
>>>>>>
>>>>>> *** Adding links:
>>>>>> (10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
>>>>>> *** Configuring hosts
>>>>>> a b c d
>>>>>> Setup time: 8
>>>>>> *** Starting controller
>>>>>> c0
>>>>>> *** Starting 0 switches
>>>>>>
>>>>>> Loading experiment: pingall
>>>>>> Using 1.000000 traffic
>>>>>> *Waiting 60 seconds for convergence...*
>>>>>> ...done
>>>>>> *NLSR has not converged. Exiting...*
>>>>>> rajendrj at Jeeva:~$
>>>>>>
>>>>>> As shown in the last line, the execution exited with 'NLSR has not converged'
>>>>>>
>>>>>> ' message
>>>>>>
>>>>>> Am I missing something here ? Is this because 'mininet' is running from home directory
>>>>>>
>>>>>> but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see
>>>>>>
>>>>>> the error output?
>>>>>>
>>>>>> Please advise and help me here
>>>>>>
>>>>>> Thanks in advance,
>>>>>>
>>>>>> ~Jeeva
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160623/9b9eca2b/attachment.html>

From agawande at memphis.edu  Thu Jun 23 15:31:45 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 23 Jun 2016 22:31:45 +0000
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <CAMGewCS_yiYHU4xf0V3eByzmu-9TLRbJSGDJa3NEJzh2J+BDsw@mail.gmail.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>
	<CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>
	<BN3PR04MB219609EE2CC48D06ECA86BC4D9550@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCTqeHmhuL5zetSxWC3z8tmmTmGRhWevy9oqOed3d3WSfQ@mail.gmail.com>
	<SN2PR04MB220561FA14E4E66C7F576FEAD9560@SN2PR04MB2205.namprd04.prod.outlook.com>,
	<CAMGewCS_yiYHU4xf0V3eByzmu-9TLRbJSGDJa3NEJzh2J+BDsw@mail.gmail.com>
Message-ID: <BN3PR04MB2196083DCDA4ABE24CC1892CD92D0@BN3PR04MB2196.namprd04.prod.outlook.com>

If you have installed ndn-tools, it has ndndump in it which can be started on every node on every interface:


for host in self.net.hosts:

         for intf in host.intfNames():
                ndnDumpOutputFile = "dump.%s_%s" % (intf, str(host.intf(intf).IP()))
                host.cmd("sudo ndndump  -i %s > %s &" % (intf, ndnDumpOutputFile))

Then dump files would be available in /tmp/<node-name>/dump_intf*

Else there is this unofficial version of NDN wireshark:
https://github.com/relue2718/ndn-wireshark-dissector

Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie>
Sent: Thursday, June 23, 2016 5:17:18 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

The above scenario is being intermittent now. Sometimes ndnpingserver process from setup is running without being killed and in other cases the process is getting killed. I noticed the above by doing 'grep' for ndnpingserver.

Upon printing ndnpinserver command using 'print(host.cmd.....' , a process ID is being printed and this ID is sometimes getting listed in 'ps aux' (where the ndnpingserver keeps running) and sometimes not getting listed (where the server is killed)

I am still looking into it.

Just by putting the ndnpingserver in ping module, I started working on mini-ndn for my project. I like the way mini-ndn is framed.

Meanwhile, Is there is a packet dissector like Wireshark that works for minindn ? (I am in need of looking into the packets that get generated out of communication between NDN nodes in mini-ndn. Is it possible?)

Please advise

thanks,
Jeeva

On 17 June 2016 at 17:57, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

I am not sure why ndnpingserver won't work from setup.


Were the ndnpingservers running while the experiment ran or did they quit (ps aux | grep ndnpingserver) when you start them from setup?


Maybe in setup try:

           print(host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &"))


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Thursday, June 16, 2016 11:44:56 AM

To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried the following (sorry for the long mail)

#1 - Manual try

When I tried invoking 'ndnpingserver' followed by 'ndnping' manually for a host as follows, ndnping received the contents and meanwhile ndnpingserver file showed the interests that are received

//

mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &

mininet> b ndnping -c 5 /ndn/edu/a

//

Above commands worked for all the hosts

#2. - from minindn script - They seem to be not working while running from minindn script

I replicated the above manual scenario in the code in experiment.py file , by replacing this line 'host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")' from setup module to ping module as follows:

// ndn/experiments/experiment.py

def setup(self):

........

#host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")

.......

 def ping(self, source, dest, nPings):

.......

dest.cmd("ndnpingserver /ndn/edu/" + str(dest) + " > ping-server &")
source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name<http://dest.name> + " >> ping-data/" + dest.name<http://dest.name> + ".txt &")

//

as quoted in the code above I tried running ndnpingserver just before calling ndnping client , reinstalled mini-ndn , executed pingall experiment and the ping got content for the interests


But, executing ndnpingserver from setup module is not keeping ndnpingserver listening (no change in ping-server file-no interests received expect for the prefix entry)

// ndn/experiments/experiment.py

def setup(self):

........

host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")

.......

 def ping(self, source, dest, nPings):

.......

#dest.cmd("ndnpingserver /ndn/edu/" + str(dest) + " > ping-server &")
source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name<http://dest.name> + " >> ping-data/" + dest.name<http://dest.name> + ".txt &")

//

when I tried with logging statements for both the scenarios, 'statusRouter' printed our an error message for the last one (scenario where ndnpingserver started from setup module and no content received). The error message is shown below:


statusRouter
ERROR: Key does not exist:/tmp-identity/%16%1B%CA8/ksk-1466093584396
  /ndn/edu/%C1.Router/cs/d nexthops={faceid=261 (cost=30)}
  /ndn/edu/%C1.Router/cs/b nexthops={faceid=261 (cost=20)}
  /ndn/edu/%C1.Router/cs/c nexthops={faceid=258 (cost=0)}
  /ndn/edu/%C1.Router/cs/a nexthops={faceid=261 (cost=10)}

For the other case there is no error for statusRouter.

Please advise

Thank you!

~Jeeva


On 15 June 2016 at 18:17, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

So in Mini-NDN did you follow these steps to check whether ndnping works:


mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &

mininet> b ndnping -c5 /ndn/edu/a


If this does not work can you check if ndnpingserver output anything to /tmp/a/ndnpingserver or whether it is running (ps aux | grep ndndpingserver).

If it is running can you try:

mininet> a ndnping -c5 /ndn/edua


I am not sure about the NFD error, are you running NFD while you are running Mini-NDN?


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Wednesday, June 15, 2016 11:48:36 AM

To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

I tried running 'NFD' in one terminal (using sudo nfd-start) and meanwhile checked for the nfd-status in another terminal(using sudo nfd-status), and I saw the following messages in the terminal where NFD was running:

1466016269.157386 INFO: [UnixStreamTransport] [id=0,local=unix:///run/nfd.sock,remote=fd://28] Creating transport
1466016269.157470 INFO: [FaceTable] Added face id=261 remote=fd://28 local=unix:///run/nfd.sock
1466016269.202716 INFO: [Transport] [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState UP -> FAILED
1466016269.202831 INFO: [Transport] [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState FAILED -> CLOSED
1466016269.207058 INFO: [FaceTable] Removed face id=261 remote=fd://28 local=unix:///run/nfd.sock


Jeeva

On 15 June 2016 at 17:41, Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>> wrote:
Thanks Ashlesh!

When I tried pingAll experiment today all the pings were getting timed out (no content entries in the text file; only timeout entries)

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:0
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:0
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:0
/tmp/d/ping-data/c.txt:0
rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:10
/tmp/a/ping-data/c.txt:10
/tmp/a/ping-data/d.txt:10
/tmp/b/ping-data/a.txt:10
/tmp/b/ping-data/c.txt:10
/tmp/b/ping-data/d.txt:10
/tmp/c/ping-data/a.txt:10
/tmp/c/ping-data/b.txt:10
/tmp/c/ping-data/d.txt:10
/tmp/d/ping-data/a.txt:10
/tmp/d/ping-data/b.txt:10
/tmp/d/ping-data/c.txt:10

I was running the command from only one terminal (no other terminals are open). NFD and NLSR status are getting displayed for all the nodes

I also tried manually 'ndnping' from the node 'a' to the prefix '/ndn/edu/b' , but it got timed out as well

Is there a way to track the reason behind these timeouts ?

Please advise

thanks,
Jeeva


On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

It is not expected, I think you have timeouts in those, search:

grep -c timeout /tmp/*/ping-data/*.txt


ndnping is timing out for some reason - either NFD went down during the experiment in another terminal

(you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went down on any of the node.


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Tuesday, June 14, 2016 2:48:39 PM

To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thank you for sorting out the problem.

I am using Ubuntu 14.04 LTS.

Yeah. 'nfd-status' was not working even outside the mini-ndn folder  (seems like nfd-start and stop were working, I even got 'NFD already running' message when i triggered nfd-start multiple times)

When i tried checking out the above patch in NFD folder there was 'fatal: reference not in tree' issue. So, i removed '--depth 1' part from git clone of NFD in install.sh of mini-ndn and reinstalled it

I checked out the above patch as well and ran waf configuration and installation

Then i executed both 'nfd-status' and pingall experiment and both got executed successfully with the convergence time of 120 instead of 60. Thank you so much for the help.

I just have one more query. When I executed the command 'sudo minindn --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it showed count for only few files . Is this expected ?

rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
/tmp/a/ping-data/b.txt:243
/tmp/a/ping-data/c.txt:0
/tmp/a/ping-data/d.txt:0
/tmp/b/ping-data/a.txt:0
/tmp/b/ping-data/c.txt:0
/tmp/b/ping-data/d.txt:0
/tmp/c/ping-data/a.txt:0
/tmp/c/ping-data/b.txt:242
/tmp/c/ping-data/d.txt:0
/tmp/d/ping-data/a.txt:0
/tmp/d/ping-data/b.txt:241
/tmp/d/ping-data/c.txt:0

Please advise.

Thanks,
~Jeeva



On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Hi


Some new information may have come to light, if nfd-status is not working outside Mini-NDN can you try the following patch:

https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0


To do so go to your NFD folder and do

git checkout ace83ac9384da037a36695888e829d7337ce36b0

./waf distclean

./waf configure --without-websocket

./waf

sudo ./waf install


Then try to run Mini-NDN experiment again.


And is your OS, Ubuntu 14.04?


Thanks

Ashlesh


________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>>
Sent: Tuesday, June 14, 2016 11:29:50 AM
To: Rajendran Jeeva

Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn


Can you check whether nfd-status works outside of mini-ndn?

Just do nfd-start and then do nfd-status.


Convergence depends on nfd-status as mini-ndn checks whether prefixes and routers have been installed.


> a nfd does not work because we use the a.conf file, if you do" a nfd -f a.conf &" it should work.

But the problem seems to be that nfd-status is not working (even outside of mini-ndn).


Ashlesh

________________________________
From: Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Tuesday, June 14, 2016 9:32:55 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi Ashlesh,

Thanks for the response.

I tried running the command 'a nfd-status -b' for node 'a' and for other nodes as well. It is not displaying anything .

1. NFD status:

mininet> a nfd-status -b
mininet>


NLSR status is displaying as follow

2. NLSR status:

mininet> a nlsrc status
NLSR Status
LSDB:
  OriginRouter: /ndn/edu/%C1.Router/cs/a

    Coordinate LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
      angle=0
      radius=0

    Name LSA:
      info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a, SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
      name=/ndn/edu/a

  OriginRouter: /ndn/edu/%C1.Router/cs/b

3. I just tried running 'nfd' command for a node and it displayed 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'

mininet> a nfd
1465913606.293515 FATAL: [NFD] Failed to read configuration file: /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void nfd::ConfigFile::parse(const string&, bool)]
mininet>

I ensured again that NFD is installed when mini-ndn is installed and the configuration is run.

Not sure whether the convergence is not happening because the conf file is missing.

Any help would be appreciated

Thanks in advance

~Jeeva


On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Try to run just:

sudo minindn


And when the command line comes up, wait for some time and check the FIB of each node:


a nfd-status -b

b nfd-status -b

c nfd-status -b

d nfd-status -b


They should all have each other prefixes (i.e. /ndn/edu/<node>) and routers (/ndn/edu/%C1.Router/<node>).

If not you will get the error you got - NLSR could not converge (only if an experiment was run).


If they do have each other's prefixes then you can try to increase the convergence time:

sudo minindn --experiment=pingall --ctime 100


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Rajendran Jeeva <rajendrj at tcd.ie<mailto:rajendrj at tcd.ie>>
Sent: Sunday, June 12, 2016 10:33:05 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn

Hi All,

I have installed mini-ndn as follows:

1. Cloned 'mini-ndn' from github
2. $ cd mini-ndn
3. Installed it using the command

sudo ./install.sh -mrfti

4. When the above command got executed , NFD, NLSR, ndn, and
mininet got installed in the 'mini-ndn' directory(not in the home directory

as I ran install.sh from inside mini-ndn directory )

5. Once the installation is completed I tried running the --Pingall experiment with

default topology

6. There was an error stating 'mininet.topo module not found'(Rectified this

problem by installing 'mininet' in the home directory)

7. When I ran the minindn command again, I got the following output

rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Setup time: 8
*** Starting controller
c0
*** Starting 0 switches

Loading experiment: pingall
Using 1.000000 traffic
Waiting 60 seconds for convergence...
...done
NLSR has not converged. Exiting...
rajendrj at Jeeva:~$


As shown in the last line, the execution exited with 'NLSR has not converged'

' message


Am I missing something here ? Is this because 'mininet' is running from home directory

but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see

the error output?


Please advise and help me here


Thanks in advance,

~Jeeva










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

From agawande at memphis.edu  Fri Jun 24 08:57:03 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 24 Jun 2016 15:57:03 +0000
Subject: [Mini-NDN] denied permission to nlsr.conf file
In-Reply-To: <CALz2BYHgm8NpdPaEdDXmPvgTtzCmHV8WT4PsmvL92Rbb_eR1og@mail.gmail.com>
References: <CALz2BYHgm8NpdPaEdDXmPvgTtzCmHV8WT4PsmvL92Rbb_eR1og@mail.gmail.com>
Message-ID: <BN3PR04MB2196AFBE9D1604CC22DD9653D92E0@BN3PR04MB2196.namprd04.prod.outlook.com>

You can specify the location of configuration file via nlsr -f /path/to/file.


Can you simply  run:

sudo minindn


then do:

mininet>a nfd-status -b

mininet> a nlsrc status


Also while Mini-NDN is running, in a new terminal, do:

ps aux | grep "sudo nfd"

ps aux | grep "nlsr"


and send the result?


I wanted to see whether NFD and NLSR are running.


Thanks

Ashlesh


________________________________
From: Adarshi Sinha <adarshisinha at gmail.com>
Sent: Friday, June 24, 2016 12:34:31 AM
To: Ashlesh Gawande (agawande)
Subject: denied permission to nlsr.conf file

Dear sir,
           I have installed and built ndn-cxx, nfd, and NLSR. nfd is perfectly running but in case of NLSR there is errer showing about the denied access to the configuration file. So, my NLSR is unable to run. Also, this is affecting my running of mini-ndn as there is an error stating: NLSR could not be converged. Can you suggest me some ways to resolve this?

Yours faithfully,
Adarshi Sinha.
Phn no. : 8102125200
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160624/5fd9d3c0/attachment.html>

From agawande at memphis.edu  Fri Jun 24 11:46:30 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 24 Jun 2016 18:46:30 +0000
Subject: [Mini-NDN] denied permission to nlsr.conf file
In-Reply-To: <CALz2BYHsrpprzqqCnyVLmi56HVMwXFwnpnWm=f2xhG5BcbbjHQ@mail.gmail.com>
References: <CALz2BYHgm8NpdPaEdDXmPvgTtzCmHV8WT4PsmvL92Rbb_eR1og@mail.gmail.com>
	<BN3PR04MB2196AFBE9D1604CC22DD9653D92E0@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CALz2BYHsrpprzqqCnyVLmi56HVMwXFwnpnWm=f2xhG5BcbbjHQ@mail.gmail.com>
Message-ID: <BN3PR04MB2196F2BD43F145531B1DD4DCD92E0@BN3PR04MB2196.namprd04.prod.outlook.com>

Everything looks good, may be just need to wait a little more:

Use --ctime 120 for convergence while running minindn.

(default time is 60 seconds)


Ashlesh

________________________________
From: Adarshi Sinha <adarshisinha at gmail.com>
Sent: Friday, June 24, 2016 1:43:42 PM
To: Ashlesh Gawande (agawande)
Subject: Re: denied permission to nlsr.conf file

Dear sir,
         Attached screenshots are what the results i got.

On Fri, Jun 24, 2016 at 9:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You can specify the location of configuration file via nlsr -f /path/to/file.


Can you simply  run:

sudo minindn


then do:

mininet>a nfd-status -b

mininet> a nlsrc status


Also while Mini-NDN is running, in a new terminal, do:

ps aux | grep "sudo nfd"

ps aux | grep "nlsr"


and send the result?


I wanted to see whether NFD and NLSR are running.


Thanks

Ashlesh


________________________________
From: Adarshi Sinha <adarshisinha at gmail.com<mailto:adarshisinha at gmail.com>>
Sent: Friday, June 24, 2016 12:34:31 AM
To: Ashlesh Gawande (agawande)
Subject: denied permission to nlsr.conf file

Dear sir,
           I have installed and built ndn-cxx, nfd, and NLSR. nfd is perfectly running but in case of NLSR there is errer showing about the denied access to the configuration file. So, my NLSR is unable to run. Also, this is affecting my running of mini-ndn as there is an error stating: NLSR could not be converged. Can you suggest me some ways to resolve this?

Yours faithfully,
Adarshi Sinha.
Phn no. : 8102125200

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

From agawande at memphis.edu  Sat Jun 25 07:40:47 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Sat, 25 Jun 2016 14:40:47 +0000
Subject: [Mini-NDN] NLSR
In-Reply-To: <CAOeyPySA9_=0sJVJ31Bd7Ex07YWg=OcsRmAvTvtw1hQm3fQCRg@mail.gmail.com>
References: <CAOeyPySKEvTqKoodMR6+bCJ2ZB9DUCdji97H6m1dnGsuUTYkuw@mail.gmail.com>
	<BN3PR04MB21963EC21967B1C49C901839D9550@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAOeyPyTMGy9C+nJfnkCJGnsc6z839S6V5QiHr6Kd4GVR5GaZ_Q@mail.gmail.com>
	<BN3PR04MB2196212CE19452C66A02E5D5D92B0@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAOeyPySA9_=0sJVJ31Bd7Ex07YWg=OcsRmAvTvtw1hQm3fQCRg@mail.gmail.com>
Message-ID: <BN3PR04MB219634B47FCD468882B4B9A7D92F0@BN3PR04MB2196.namprd04.prod.outlook.com>

You need to install ndn-tools to use ndnping and ndndump:


git clone --depth 1 https://github.com/named-data/ndn-tools


cd ndn-tools

./waf configure --enable-ping --enable-dump

./waf

sudo ./waf install


Ashlesh

________________________________
From: Tanusree Chatterjee <tnsr.chatterjee at gmail.com>
Sent: Saturday, June 25, 2016 12:51:12 AM
To: Ashlesh Gawande (agawande)
Subject: Re: NLSR

Ashlesh,

In your video after running the nfd status, is the command following one?
mininet> a ndnpingserver /ndn/edu/a  &
then
mininet> a ndnping -c 4 /ndn/edu/a

In my machine it says
bash: ndnpingserver: command not found
bash: ndnping: command not found

Why these commands are not working?

Here, the default configuration is running with the 4 hosts a b c d, right? I should check the log to understand the working thoroughly before doing modifications of any code? This default topology can be found there? And I can set up my own topology afterwards?


On Tue, Jun 21, 2016 at 8:55 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No it won't be  a problem.


You can simply install mininet first by:

git clone --depth 1 https://github.com/mininet/mininet

cd mininet

sudo ./util/install.sh -fnv


Then you can install mini-ndn

git clone --depth 1 https://github.com/named-data/mini-ndn


cd mini-ndn

sudo ./install.sh -i


Further information on mininet and mini-ndn:

https://www.youtube.com/watch?v=UxHPqaUwefg&feature=youtu.be


Ashlesh

________________________________
From: Tanusree Chatterjee <tnsr.chatterjee at gmail.com<mailto:tnsr.chatterjee at gmail.com>>
Sent: Tuesday, June 21, 2016 12:04:40 AM
To: Ashlesh Gawande (agawande)
Subject: Re: NLSR

Ashlesh,

I have installed NLSR already in my machine earlier and so NFD is also installed. Will it be any problem to install Mini-NDN now in Ubuntu 14.04?

On Wed, Jun 15, 2016 at 8:12 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Those are NLSRs neighbors. You need to configure other nodes running NLSR and make them neighbors.


But a better way would be to use Mini-NDN

https://github.com/named-data/mini-ndn
You should be able to find all the documentation in docs.

There is also a security patch here which sets NLSR security for you: http://gerrit.named-data.net/#/c/2873/

on Mini-NDN.


It does the setup for you and runs multiple NLSR on a single machine so you don't need multiple nodes.


NDNSim NLSR is still being prepared and might take a while.


Mini-NDN is an emulator - i.e. it runs actual instances of NFD, NLSR etc. so it does not scale as good. Scaling also depends on CPU rather than RAM. (~100 nodes max scaling on 32 core machine).

NDNSim is a simulator - i.e. it simulates NFD etc and scaling is much better. Scaling depends on RAM.


So if you need scaling in your experiment use NDNSim.

(Very high number of nodes can be simulated.)


I would suggest you read the following papers:

http://named-data.net/publications/nlsr-final/


http://named-data.net/publications/techreports/ndn-0037-1-nlsr/


<http://named-data.net/publications/techreports/ndn-0037-1-nlsr/>You will have to thoroughly understand security in NDN (NLSR) before implementing but you can look at the Mini-NDN patch as to how the security is actually done.

Also you can look at this:

http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html


Ashlesh

________________________________
From: Tanusree Chatterjee <tnsr.chatterjee at gmail.com<mailto:tnsr.chatterjee at gmail.com>>
Sent: Wednesday, June 15, 2016 1:34:03 AM
To: Ashlesh Gawande (agawande)
Subject: NLSR

Hi Ashlesh,

After I run the nlsr now, it is not showing anything in the terminal and crearing a log file which contents the following.

20160615113331480 WARN: [FaceController] Could not convert udp://mira.cs.memphis.edu<http://mira.cs.memphis.edu> to canonical form: Hostname resolution timed out

Can you tell me what is the significance of the above number in the file? And what for the warning is coming? You have commented few lines to disable the security. What if I want to keep the security enable? How and hat I need to configure then?

Which part in NDN you are currently working on? I am new to NDN and currrently I am doing my research to understand the NLSR where I want to propose some changes to enhance its security and also to reduce the overheads of the protocol in few area. Can you suggest me in which sections of the codes I need to concentrate and start working to do the same in future? What research is going on currently on NDNsim? How the simulator can be used in my work? Do I need to built up an app for it? I guess Anil is working to port NLSR in NDNsim. May be in future NLSR will not be needed to install separately.

However, thanks a lot for all your help till now.

-- Regards,
Tanusree Chatterjee




--
Tanusree Chatterjee




-- Regards,
Tanusree Chatterjee
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160625/cf666c2c/attachment.html>

From agawande at memphis.edu  Mon Jun 27 09:20:55 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 27 Jun 2016 16:20:55 +0000
Subject: [Mini-NDN] run with 5 nodes in Minindn
In-Reply-To: <CAOeyPySuaYQgu4vN+E=ruqZ8n3x+fc5jbuBWO2HrygoW3mtjEw@mail.gmail.com>
References: <CAOeyPySuaYQgu4vN+E=ruqZ8n3x+fc5jbuBWO2HrygoW3mtjEw@mail.gmail.com>
Message-ID: <BN3PR04MB2196C78731618C0C2EB3C4D8D9210@BN3PR04MB2196.namprd04.prod.outlook.com>

Can you check if h5 has the prefix for h1?

It might take a while for NLSR to install the prefix (i.e. to converge).


If you have downloaded and installed the security patch - security is already done and NLSR is signing and verifying each data packets according to the hierarchy.


We don't have much more documentation as of yet.

You can read through nlsr.py (in mini-ndn) to see how security files are configured.

Some information about security can be found here:

http://named-data.net/doc/NLSR/current/SECURITY-CONFIG.html

Some more info on NDN security:

http://named-data.net/doc/ndn-cxx/current/tutorials/security-library.html


I am not sure about ndn-validator.conf, maybe you need to install NFD with docs (check ./waf configure --help) and then you can do "man ndn-validator.conf"?


Ashlesh


________________________________
From: Tanusree Chatterjee <tnsr.chatterjee at gmail.com>
Sent: Sunday, June 26, 2016 11:59:43 AM
To: Ashlesh Gawande (agawande)
Subject: run with 5 nodes in Minindn

Ashlesh,

I have tried in minindnedit to add 5 nodes with one linking with next one. No such change in host options. Only log level changed to debug in NLSR option. Why it does not show content received.. The output is as follows.

mininet> h5 ndnpingserver /ndn/edu/h5 &
mininet> h5 ndnping -c 5 /ndn/edu/h1
PING SERVER /ndn/edu/h5
PING /ndn/edu/h1
timeout from /ndn/edu/h1: seq=11583409731735595458
timeout from /ndn/edu/h1: seq=11583409731735595459
timeout from /ndn/edu/h1: seq=11583409731735595460
timeout from /ndn/edu/h1: seq=11583409731735595461
timeout from /ndn/edu/h1: seq=11583409731735595462

--- /ndn/edu/h1 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 0 ms

I have seen all the log and config files. Is the security is already done as I have downloaded the security patch? Anyway, the security and trust model is not well understood. Do you have any more documentation except the NLSR paper to understand the both? Where can I found ndn-validator.conf? It is written in the config files For more information on trust anchor refer to manpage of ndn-validator.conf.

--Thanks & Regards,
Tanusree Chatterjee

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

From rajendrj at tcd.ie  Tue Jun 28 12:06:34 2016
From: rajendrj at tcd.ie (Rajendran Jeeva)
Date: Tue, 28 Jun 2016 20:06:34 +0100
Subject: [Mini-NDN] NLSR has not converged - Issue while running minindn
In-Reply-To: <BN3PR04MB2196083DCDA4ABE24CC1892CD92D0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAMGewCRKPdMXeA2GA0LGFhfN_n6UKVgxY4VF8p-_HSkkaqo5rQ@mail.gmail.com>
	<BN3PR04MB2196F7956162F08CB41550D1D9530@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQSpxCbPOrBCh4-=8dJML5yPKGvsxiPpWXPXdSmS1asgw@mail.gmail.com>
	<BN3PR04MB2196D7247E12253115D566EFD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21961CC0F09D5CF70C3DD4F0D9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCSZWLStocX00zxrbNje_4S-vsdUC24NWn7yAn_SMWjwBQ@mail.gmail.com>
	<BN3PR04MB219657FD986C5647AAB7FCDCD9540@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCQJb7hQFfHgcL5f8DPv8GO_x53vk_TQ-227RxH+U2_Xkg@mail.gmail.com>
	<CAMGewCTCZf7Pf+xY+5SToHk8Q+2hMr7Sgf_ZdfX=1h=Fybs5Wg@mail.gmail.com>
	<BN3PR04MB219609EE2CC48D06ECA86BC4D9550@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAMGewCTqeHmhuL5zetSxWC3z8tmmTmGRhWevy9oqOed3d3WSfQ@mail.gmail.com>
	<SN2PR04MB220561FA14E4E66C7F576FEAD9560@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAMGewCS_yiYHU4xf0V3eByzmu-9TLRbJSGDJa3NEJzh2J+BDsw@mail.gmail.com>
	<BN3PR04MB2196083DCDA4ABE24CC1892CD92D0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAMGewCQD-J3rypfadZzBDbw9JHLH1JQvVr7WOjFqwhXEJ3Vn3w@mail.gmail.com>

Thanks for the help Ashlesh!

~Jeeva

On 23 June 2016 at 23:31, Ashlesh Gawande (agawande) <agawande at memphis.edu>
wrote:

> If you have installed ndn-tools, it has ndndump in it which can be started
> on every node on every interface:
>
>
> for host in self.net.hosts:
>
>          for intf in host.intfNames():
>                 ndnDumpOutputFile = "dump.%s_%s" % (intf,
> str(host.intf(intf).IP()))
>                 host.cmd("sudo ndndump  -i %s > %s &" % (intf,
> ndnDumpOutputFile))
>
> Then dump files would be available in /tmp/<node-name>/dump_intf*
>
> Else there is this unofficial version of NDN wireshark:
> https://github.com/relue2718/ndn-wireshark-dissector
>
> Ashlesh
>
> ------------------------------
> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
> *Sent:* Thursday, June 23, 2016 5:17:18 PM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
> minindn
>
> Hi Ashlesh,
>
> The above scenario is being intermittent now. Sometimes ndnpingserver
> process from setup is running without being killed and in other cases the
> process is getting killed. I noticed the above by doing 'grep' for
> ndnpingserver.
>
> Upon printing ndnpinserver command using 'print(host.cmd.....' , a process
> ID is being printed and this ID is sometimes getting listed in 'ps aux'
> (where the ndnpingserver keeps running) and sometimes not getting listed
> (where the server is killed)
>
> I am still looking into it.
>
> Just by putting the ndnpingserver in ping module, I started working on
> mini-ndn for my project. I like the way mini-ndn is framed.
>
> Meanwhile, Is there is a packet dissector like Wireshark that works for
> minindn ? (I am in need of looking into the packets that get generated out
> of communication between NDN nodes in mini-ndn. Is it possible?)
>
> Please advise
>
> thanks,
> Jeeva
>
> On 17 June 2016 at 17:57, Ashlesh Gawande (agawande) <agawande at memphis.edu
> > wrote:
>
>> I am not sure why ndnpingserver won't work from setup.
>>
>>
>> Were the ndnpingservers running while the experiment ran or did they quit
>> (ps aux | grep ndnpingserver) when you start them from setup?
>>
>>
>> Maybe in setup try:
>>
>>            print(host.cmd("ndnpingserver /ndn/edu/" + str(host) + " >
>> ping-server &"))
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>> *Sent:* Thursday, June 16, 2016 11:44:56 AM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>> minindn
>>
>> Hi Ashlesh,
>>
>> Thanks for the response.
>>
>> I tried the following (sorry for the long mail)
>>
>> #1 - Manual try
>>
>> When I tried invoking 'ndnpingserver' followed by 'ndnping' manually for
>> a host as follows, ndnping received the contents and meanwhile
>> ndnpingserver file showed the interests that are received
>>
>> //
>>
>> mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &
>>
>> mininet> b ndnping -c 5 /ndn/edu/a
>>
>> //
>>
>> Above commands worked for all the hosts
>>
>> #2. - from minindn script - They seem to be not working while running
>> from minindn script
>>
>> I replicated the above manual scenario in the code in experiment.py file
>> , by replacing this line 'host.cmd("ndnpingserver /ndn/edu/" + str(host) +
>> " > ping-server &")' from setup module to ping module as follows:
>>
>> // ndn/experiments/experiment.py
>>
>> def setup(self):
>>
>> ........
>>
>> #host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")
>>
>> .......
>>
>>  def ping(self, source, dest, nPings):
>>
>> .......
>>
>> *dest.cmd("ndnpingserver /ndn/edu/" + str(dest) + " > ping-server &")*
>> source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name + "
>> >> ping-data/" + dest.name + ".txt &")
>>
>> //
>>
>> as quoted in the code above I tried running ndnpingserver just before
>> calling ndnping client , reinstalled mini-ndn , executed pingall experiment
>> and the ping got content for the interests
>>
>>
>> But, executing ndnpingserver from setup module is not keeping
>> ndnpingserver listening (no change in ping-server file-no interests
>> received expect for the prefix entry)
>>
>> // ndn/experiments/experiment.py
>>
>> def setup(self):
>>
>> ........
>>
>> *host.cmd("ndnpingserver /ndn/edu/" + str(host) + " > ping-server &")*
>>
>> .......
>>
>>  def ping(self, source, dest, nPings):
>>
>> .......
>>
>> *#*dest.cmd("ndnpingserver /ndn/edu/" + str(dest)* + " > ping-server &")*
>> source.cmd("ndnping -t -c "+ str(nPings) + " /ndn/edu/" + dest.name + "
>> >> ping-data/" + dest.name + ".txt &")
>> //
>>
>> when I tried with logging statements for both the scenarios,
>> 'statusRouter' printed our an error message for the last one (scenario
>> where ndnpingserver started from setup module and no content received). The
>> error message is shown below:
>>
>>
>> statusRouter
>> ERROR: Key does not exist:/tmp-identity/%16%1B%CA8/ksk-1466093584396
>>   /ndn/edu/%C1.Router/cs/d nexthops={faceid=261 (cost=30)}
>>   /ndn/edu/%C1.Router/cs/b nexthops={faceid=261 (cost=20)}
>>   /ndn/edu/%C1.Router/cs/c nexthops={faceid=258 (cost=0)}
>>   /ndn/edu/%C1.Router/cs/a nexthops={faceid=261 (cost=10)}
>> For the other case there is no error for statusRouter.
>>
>> Please advise
>>
>> Thank you!
>>
>> ~Jeeva
>>
>>
>> On 15 June 2016 at 18:17, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> So in Mini-NDN did you follow these steps to check whether ndnping works:
>>>
>>>
>>> mininet> a ndnpingserver /ndn/edu/a > ndnpingserver &
>>>
>>> mininet> b ndnping -c5 /ndn/edu/a
>>>
>>>
>>> If this does not work can you check if ndnpingserver output anything to
>>> /tmp/a/ndnpingserver or whether it is running (ps aux | grep
>>> ndndpingserver).
>>>
>>> If it is running can you try:
>>>
>>> mininet> a ndnping -c5 /ndn/edua
>>>
>>> I am not sure about the NFD error, are you running NFD while you are
>>> running Mini-NDN?
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>> *Sent:* Wednesday, June 15, 2016 11:48:36 AM
>>>
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while running
>>> minindn
>>>
>>> I tried running 'NFD' in one terminal (using sudo nfd-start) and
>>> meanwhile checked for the nfd-status in another terminal(using sudo
>>> nfd-status), and I saw the following messages in the terminal where NFD was
>>> running:
>>>
>>> 1466016269.157386 INFO: [UnixStreamTransport]
>>> [id=0,local=unix:///run/nfd.sock,remote=fd://28] Creating transport
>>> 1466016269.157470 INFO: [FaceTable] Added face id=261 remote=fd://28
>>> local=unix:///run/nfd.sock
>>> 1466016269.202716 INFO: [Transport]
>>> [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState UP -> FAILED
>>> 1466016269.202831 INFO: [Transport]
>>> [id=261,local=unix:///run/nfd.sock,remote=fd://28] setState FAILED -> CLOSED
>>> 1466016269.207058 INFO: [FaceTable] Removed face id=261 remote=fd://28
>>> local=unix:///run/nfd.sock
>>>
>>>
>>> Jeeva
>>>
>>> On 15 June 2016 at 17:41, Rajendran Jeeva <rajendrj at tcd.ie> wrote:
>>>
>>>> Thanks Ashlesh!
>>>>
>>>> When I tried pingAll experiment today all the pings were getting timed
>>>> out (no content entries in the text file; only timeout entries)
>>>>
>>>> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
>>>> /tmp/a/ping-data/b.txt:0
>>>> /tmp/a/ping-data/c.txt:0
>>>> /tmp/a/ping-data/d.txt:0
>>>> /tmp/b/ping-data/a.txt:0
>>>> /tmp/b/ping-data/c.txt:0
>>>> /tmp/b/ping-data/d.txt:0
>>>> /tmp/c/ping-data/a.txt:0
>>>> /tmp/c/ping-data/b.txt:0
>>>> /tmp/c/ping-data/d.txt:0
>>>> /tmp/d/ping-data/a.txt:0
>>>> /tmp/d/ping-data/b.txt:0
>>>> /tmp/d/ping-data/c.txt:0
>>>> rajendrj at Jeeva:~$ grep -c timeout /tmp/*/ping-data/*.txt
>>>> /tmp/a/ping-data/b.txt:10
>>>> /tmp/a/ping-data/c.txt:10
>>>> /tmp/a/ping-data/d.txt:10
>>>> /tmp/b/ping-data/a.txt:10
>>>> /tmp/b/ping-data/c.txt:10
>>>> /tmp/b/ping-data/d.txt:10
>>>> /tmp/c/ping-data/a.txt:10
>>>> /tmp/c/ping-data/b.txt:10
>>>> /tmp/c/ping-data/d.txt:10
>>>> /tmp/d/ping-data/a.txt:10
>>>> /tmp/d/ping-data/b.txt:10
>>>> /tmp/d/ping-data/c.txt:10
>>>>
>>>> I was running the command from only one terminal (no other terminals
>>>> are open). NFD and NLSR status are getting displayed for all the nodes
>>>>
>>>> I also tried manually 'ndnping' from the node 'a' to the prefix
>>>> '/ndn/edu/b' , but it got timed out as well
>>>>
>>>> Is there a way to track the reason behind these timeouts ?
>>>>
>>>> Please advise
>>>>
>>>> thanks,
>>>> Jeeva
>>>>
>>>>
>>>> On 14 June 2016 at 21:08, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> It is not expected, I think you have timeouts in those, search:
>>>>>
>>>>> grep -c timeout /tmp/*/ping-data/*.txt
>>>>>
>>>>>
>>>>> ndnping is timing out for some reason - either NFD went down during
>>>>> the experiment in another terminal
>>>>>
>>>>> (you can keep checking ps aux | grep "sudo nfd") or ndnpingserver went
>>>>> down on any of the node.
>>>>>
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>>>> *Sent:* Tuesday, June 14, 2016 2:48:39 PM
>>>>>
>>>>> *To:* Ashlesh Gawande (agawande)
>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while
>>>>> running minindn
>>>>>
>>>>> Hi Ashlesh,
>>>>>
>>>>> Thank you for sorting out the problem.
>>>>>
>>>>> I am using Ubuntu 14.04 LTS.
>>>>>
>>>>> Yeah. 'nfd-status' was not working even outside the mini-ndn folder
>>>>> (seems like nfd-start and stop were working, I even got 'NFD already
>>>>> running' message when i triggered nfd-start multiple times)
>>>>>
>>>>> When i tried checking out the above patch in NFD folder there was
>>>>> 'fatal: reference not in tree' issue. So, i removed '--depth 1' part from
>>>>> git clone of NFD in install.sh of mini-ndn and reinstalled it
>>>>>
>>>>> I checked out the above patch as well and ran waf configuration and
>>>>> installation
>>>>>
>>>>> Then i executed both 'nfd-status' and pingall experiment and both got
>>>>> executed successfully with the convergence time of 120 instead of 60. Thank
>>>>> you so much for the help.
>>>>>
>>>>> I just have one more query. When I executed the command 'sudo minindn
>>>>> --experiment=pingall --ctime 120 --nPings=50' and checked ping-data , it
>>>>> showed count for only few files . Is this expected ?
>>>>>
>>>>> rajendrj at Jeeva:~$ grep -c content /tmp/*/ping-data/*.txt
>>>>> /tmp/a/ping-data/b.txt:243
>>>>> /tmp/a/ping-data/c.txt:0
>>>>> /tmp/a/ping-data/d.txt:0
>>>>> /tmp/b/ping-data/a.txt:0
>>>>> /tmp/b/ping-data/c.txt:0
>>>>> /tmp/b/ping-data/d.txt:0
>>>>> /tmp/c/ping-data/a.txt:0
>>>>> /tmp/c/ping-data/b.txt:242
>>>>> /tmp/c/ping-data/d.txt:0
>>>>> /tmp/d/ping-data/a.txt:0
>>>>> /tmp/d/ping-data/b.txt:241
>>>>> /tmp/d/ping-data/c.txt:0
>>>>>
>>>>> Please advise.
>>>>>
>>>>> Thanks,
>>>>> ~Jeeva
>>>>>
>>>>>
>>>>>
>>>>> On 14 June 2016 at 19:42, Ashlesh Gawande (agawande) <
>>>>> agawande at memphis.edu> wrote:
>>>>>
>>>>>> Hi
>>>>>>
>>>>>>
>>>>>> Some new information may have come to light, if nfd-status is not
>>>>>> working outside Mini-NDN can you try the following patch:
>>>>>>
>>>>>>
>>>>>> https://github.com/named-data/NFD/commit/ace83ac9384da037a36695888e829d7337ce36b0
>>>>>>
>>>>>>
>>>>>> To do so go to your NFD folder and do
>>>>>>
>>>>>> git checkout ace83ac9384da037a36695888e829d7337ce36b0
>>>>>>
>>>>>> ./waf distclean
>>>>>>
>>>>>> ./waf configure --without-websocket
>>>>>>
>>>>>> ./waf
>>>>>>
>>>>>> sudo ./waf install
>>>>>>
>>>>>>
>>>>>> Then try to run Mini-NDN experiment again.
>>>>>>
>>>>>>
>>>>>> And is your OS, Ubuntu 14.04?
>>>>>>
>>>>>>
>>>>>> Thanks
>>>>>>
>>>>>> Ashlesh
>>>>>>
>>>>>>
>>>>>> ------------------------------
>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>>> Ashlesh Gawande (agawande) <agawande at memphis.edu>
>>>>>> *Sent:* Tuesday, June 14, 2016 11:29:50 AM
>>>>>> *To:* Rajendran Jeeva
>>>>>>
>>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while
>>>>>> running minindn
>>>>>>
>>>>>>
>>>>>> Can you check whether nfd-status works outside of mini-ndn?
>>>>>>
>>>>>> Just do nfd-start and then do nfd-status.
>>>>>>
>>>>>>
>>>>>> Convergence depends on nfd-status as mini-ndn checks whether prefixes
>>>>>> and routers have been installed.
>>>>>>
>>>>>>
>>>>>> > a nfd does not work because we use the a.conf file, if you do" a
>>>>>> nfd -f a.conf &" it should work.
>>>>>>
>>>>>> But the problem seems to be that nfd-status is not working (even
>>>>>> outside of mini-ndn).
>>>>>>
>>>>>>
>>>>>> Ashlesh
>>>>>> ------------------------------
>>>>>> *From:* Rajendran Jeeva <rajendrj at tcd.ie>
>>>>>> *Sent:* Tuesday, June 14, 2016 9:32:55 AM
>>>>>> *To:* Ashlesh Gawande (agawande)
>>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>>> *Subject:* Re: [Mini-NDN] NLSR has not converged - Issue while
>>>>>> running minindn
>>>>>>
>>>>>> Hi Ashlesh,
>>>>>>
>>>>>> Thanks for the response.
>>>>>>
>>>>>> I tried running the command 'a nfd-status -b' for node 'a' and for
>>>>>> other nodes as well. It is not displaying anything .
>>>>>>
>>>>>> 1. NFD status:
>>>>>>
>>>>>> mininet> a nfd-status -b
>>>>>> mininet>
>>>>>>
>>>>>>
>>>>>> NLSR status is displaying as follow
>>>>>>
>>>>>> 2. NLSR status:
>>>>>>
>>>>>> mininet> a nlsrc status
>>>>>> NLSR Status
>>>>>> LSDB:
>>>>>>   OriginRouter: /ndn/edu/%C1.Router/cs/a
>>>>>>
>>>>>>     Coordinate LSA:
>>>>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>>>>> SequenceNumber: 90, ExpirationPeriod: 3591936 milliseconds)
>>>>>>       angle=0
>>>>>>       radius=0
>>>>>>
>>>>>>     Name LSA:
>>>>>>       info=LsaInfo(OriginRouter: /ndn/edu/%C1.Router/cs/a,
>>>>>> SequenceNumber: 90, ExpirationPeriod: 3591932 milliseconds)
>>>>>>       name=/ndn/edu/a
>>>>>>
>>>>>>   OriginRouter: /ndn/edu/%C1.Router/cs/b
>>>>>>
>>>>>> 3. I just tried running 'nfd' command for a node and it displayed
>>>>>> 'Failed to read configuration file: /usr/local/etc/ndn/nfd.conf'
>>>>>>
>>>>>> mininet> a nfd
>>>>>> 1465913606.293515 FATAL: [NFD] Failed to read configuration file:
>>>>>> /usr/local/etc/ndn/nfd.conf [from ../core/config-file.cpp:94 in void
>>>>>> nfd::ConfigFile::parse(const string&, bool)]
>>>>>> mininet>
>>>>>>
>>>>>> I ensured again that NFD is installed when mini-ndn is installed and
>>>>>> the configuration is run.
>>>>>>
>>>>>> Not sure whether the convergence is not happening because the conf
>>>>>> file is missing.
>>>>>>
>>>>>> Any help would be appreciated
>>>>>>
>>>>>> Thanks in advance
>>>>>>
>>>>>> ~Jeeva
>>>>>>
>>>>>>
>>>>>> On 13 June 2016 at 16:56, Ashlesh Gawande (agawande) <
>>>>>> agawande at memphis.edu> wrote:
>>>>>>
>>>>>>> Try to run just:
>>>>>>>
>>>>>>> sudo minindn
>>>>>>>
>>>>>>>
>>>>>>> And when the command line comes up, wait for some time and check the
>>>>>>> FIB of each node:
>>>>>>>
>>>>>>>
>>>>>>> a nfd-status -b
>>>>>>>
>>>>>>> b nfd-status -b
>>>>>>>
>>>>>>> c nfd-status -b
>>>>>>>
>>>>>>> d nfd-status -b
>>>>>>>
>>>>>>>
>>>>>>> They should all have each other prefixes (i.e. /ndn/edu/<node>) and
>>>>>>> routers (/ndn/edu/%C1.Router/<node>).
>>>>>>>
>>>>>>> If not you will get the error you got - NLSR could not converge
>>>>>>> (only if an experiment was run).
>>>>>>>
>>>>>>>
>>>>>>> If they do have each other's prefixes then you can try to increase
>>>>>>> the convergence time:
>>>>>>>
>>>>>>> sudo minindn --experiment=pingall --ctime 100
>>>>>>>
>>>>>>>
>>>>>>> Ashlesh
>>>>>>> ------------------------------
>>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>>>> Rajendran Jeeva <rajendrj at tcd.ie>
>>>>>>> *Sent:* Sunday, June 12, 2016 10:33:05 AM
>>>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>>>> *Subject:* [Mini-NDN] NLSR has not converged - Issue while running
>>>>>>> minindn
>>>>>>>
>>>>>>> Hi All,
>>>>>>>
>>>>>>> I have installed mini-ndn as follows:
>>>>>>>
>>>>>>> 1. Cloned 'mini-ndn' from github
>>>>>>> 2. $ cd mini-ndn
>>>>>>> 3. Installed it using the command
>>>>>>>
>>>>>>> sudo ./install.sh -mrfti
>>>>>>>
>>>>>>> 4. When the above command got executed , NFD, NLSR, ndn, and
>>>>>>> mininet got installed in the 'mini-ndn' directory(not in the home directory
>>>>>>>
>>>>>>> as I ran install.sh from inside mini-ndn directory )
>>>>>>>
>>>>>>> 5. Once the installation is completed I tried running the --Pingall experiment with
>>>>>>>
>>>>>>> default topology
>>>>>>>
>>>>>>> 6. There was an error stating 'mininet.topo module not found'(Rectified this
>>>>>>>
>>>>>>> problem by installing 'mininet' in the home directory)
>>>>>>>
>>>>>>> 7. When I ran the minindn command again, I got the following output
>>>>>>>
>>>>>>> rajendrj at Jeeva:~$ sudo minindn --experiment=pingall
>>>>>>> No results folder specified; experiment results will remain in the working directory
>>>>>>> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
>>>>>>> *** Creating network
>>>>>>> *** Adding controller
>>>>>>> *** Adding hosts:
>>>>>>> a b c d
>>>>>>> *** Adding switches:
>>>>>>>
>>>>>>> *** Adding links:
>>>>>>> (10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
>>>>>>> *** Configuring hosts
>>>>>>> a b c d
>>>>>>> Setup time: 8
>>>>>>> *** Starting controller
>>>>>>> c0
>>>>>>> *** Starting 0 switches
>>>>>>>
>>>>>>> Loading experiment: pingall
>>>>>>> Using 1.000000 traffic
>>>>>>> *Waiting 60 seconds for convergence...*
>>>>>>> ...done
>>>>>>> *NLSR has not converged. Exiting...*
>>>>>>> rajendrj at Jeeva:~$
>>>>>>>
>>>>>>> As shown in the last line, the execution exited with 'NLSR has not converged'
>>>>>>>
>>>>>>> ' message
>>>>>>>
>>>>>>> Am I missing something here ? Is this because 'mininet' is running from home directory
>>>>>>>
>>>>>>> but NLSR , NFD and ndn run from 'mini-ndn' directory ? Is there a way to see
>>>>>>>
>>>>>>> the error output?
>>>>>>>
>>>>>>> Please advise and help me here
>>>>>>>
>>>>>>> Thanks in advance,
>>>>>>>
>>>>>>> ~Jeeva
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160628/0f4662d9/attachment.html>