From sepehrabdous1375 at gmail.com  Tue Nov  8 06:56:16 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 8 Nov 2016 18:26:16 +0330
Subject: [Mini-NDN] Fwd: nemune mail
In-Reply-To: <CAKaOrij09mHHdzZZ8tYwQxn5hTVfAOVzH0PVr18O=MmSKzTr1g@mail.gmail.com>
References: <CAKaOrihej9qmKn3cPnFRWydkDyi2zKwPLzHPLewfPMR+kpXk4Q@mail.gmail.com>
	<CAKaOrij09mHHdzZZ8tYwQxn5hTVfAOVzH0PVr18O=MmSKzTr1g@mail.gmail.com>
Message-ID: <CAKaOrihZ-cgA_k_2qj-ZQ=ev9_R5tDp04r-Kt57kzCWiaFqTLg@mail.gmail.com>

Hello all,
I'm new to nlsr and I'm trying to configure the following network topology,
means I want to produce a nlsr.conf for these nodes:

[image: Inline image 1]
I'm learning from the nlsr.conf file in mini-ndn nodes(like 'a' node), but
when I do I get the following error using the following command while I
don't encounter this error for the 'a' node:

the command is:

# nlsr -f /home/sepehr/Desktop/projectcheck/node1/nlsr.conf

and the error is:

Failed to parse configuration file
/home/sepehr/Desktop/projectcheck/node1/nlsr.conf
Error in configuration file processing! Exiting from NLSR

also my configuration for node1 is :

general{
  network /ndn/
  site /edu
  router /%C1.Router/cs/node1
  log-level DEBUG
  log-dir /home/sepehr/Desktop/projectcheck//node1/log
  seq-dir /home/sepehr/Desktop/projectcheck//node1/log
  lsa-refresh-time 1800 ;30 minutes
}

neighbors
{
    neighbor
    {
          name /ndn/edu/%C1.Router/cs/node2
          face-uri udp://1.0.0.2        ;not so sure about it
          link-cost 10
    }
    neighbor
    {
          name /ndn/edu/%C1.Router/cs/node3
          face-uri udp://1.0.0.3        ;not so sure about it
          link-cost 10
    }
}

hyperbolic
{
    state off
    radius 0.0
    angle 0.0
}

fib
{
    max-faces-per-prefix 3
}

advertising
{
    prefix /ndn/edu/node1
}


security
{
  validator
  {
    trust-anchor
    {
      type any
    }
  }
  prefix-update-validator
  {
    trust-anchor
    {
      type any
    }
  }
}

which is like 'a' node in mini-ndn.
nodes 2 to 6's configuration is similar.

I'm not sure with the lines like
face-uri udp://1.0.0.2
in neighbor sections? how can I understand how to specify this numbers for
my nodes?

so can anyone please help me with my problem?

Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161108/4e9cd250/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-11-08 03-29-33.png
Type: image/png
Size: 9131 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161108/4e9cd250/attachment.png>

From agawande at memphis.edu  Tue Nov  8 08:10:17 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Tue, 8 Nov 2016 16:10:17 +0000
Subject: [Mini-NDN] Fwd: nemune mail
In-Reply-To: <CAKaOrihZ-cgA_k_2qj-ZQ=ev9_R5tDp04r-Kt57kzCWiaFqTLg@mail.gmail.com>
References: <CAKaOrihej9qmKn3cPnFRWydkDyi2zKwPLzHPLewfPMR+kpXk4Q@mail.gmail.com>
	<CAKaOrij09mHHdzZZ8tYwQxn5hTVfAOVzH0PVr18O=MmSKzTr1g@mail.gmail.com>,
	<CAKaOrihZ-cgA_k_2qj-ZQ=ev9_R5tDp04r-Kt57kzCWiaFqTLg@mail.gmail.com>
Message-ID: <BN3PR04MB21968C83BBA743C46CA7CAA5D9A60@BN3PR04MB2196.namprd04.prod.outlook.com>

The problem with that file is it should be:

general

{


and not general{

The curly should be on a new line.


For the neighbor section, the face-uri is the IP of the neighbor.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Tuesday, November 8, 2016 8:56:16 AM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] Fwd: nemune mail

Hello all,
I'm new to nlsr and I'm trying to configure the following network topology, means I want to produce a nlsr.conf for these nodes:

[Inline image 1]
I'm learning from the nlsr.conf file in mini-ndn nodes(like 'a' node), but when I do I get the following error using the following command while I don't encounter this error for the 'a' node:

the command is:

# nlsr -f /home/sepehr/Desktop/projectcheck/node1/nlsr.conf

and the error is:

Failed to parse configuration file
/home/sepehr/Desktop/projectcheck/node1/nlsr.conf
Error in configuration file processing! Exiting from NLSR

also my configuration for node1 is :

general{
  network /ndn/
  site /edu
  router /%C1.Router/cs/node1
  log-level DEBUG
  log-dir /home/sepehr/Desktop/projectcheck//node1/log
  seq-dir /home/sepehr/Desktop/projectcheck//node1/log
  lsa-refresh-time 1800 ;30 minutes
}

neighbors
{
    neighbor
    {
          name /ndn/edu/%C1.Router/cs/node2
          face-uri udp://1.0.0.2<http://1.0.0.2>        ;not so sure about it
          link-cost 10
    }
    neighbor
    {
          name /ndn/edu/%C1.Router/cs/node3
          face-uri udp://1.0.0.3<http://1.0.0.3>        ;not so sure about it
          link-cost 10
    }
}

hyperbolic
{
    state off
    radius 0.0
    angle 0.0
}

fib
{
    max-faces-per-prefix 3
}

advertising
{
    prefix /ndn/edu/node1
}


security
{
  validator
  {
    trust-anchor
    {
      type any
    }
  }
  prefix-update-validator
  {
    trust-anchor
    {
      type any
    }
  }
}

which is like 'a' node in mini-ndn.
nodes 2 to 6's configuration is similar.

I'm not sure with the lines like
face-uri udp://1.0.0.2<http://1.0.0.2>
in neighbor sections? how can I understand how to specify this numbers for my nodes?

so can anyone please help me with my problem?

Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161108/ab711607/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-11-08 03-29-33.png
Type: image/png
Size: 9131 bytes
Desc: Screenshot from 2016-11-08 03-29-33.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161108/ab711607/attachment.png>

From sepehrabdous1375 at gmail.com  Tue Nov  8 12:04:50 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 8 Nov 2016 23:34:50 +0330
Subject: [Mini-NDN] Fwd: nemune mail
In-Reply-To: <BN3PR04MB21968C83BBA743C46CA7CAA5D9A60@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrihej9qmKn3cPnFRWydkDyi2zKwPLzHPLewfPMR+kpXk4Q@mail.gmail.com>
	<CAKaOrij09mHHdzZZ8tYwQxn5hTVfAOVzH0PVr18O=MmSKzTr1g@mail.gmail.com>
	<CAKaOrihZ-cgA_k_2qj-ZQ=ev9_R5tDp04r-Kt57kzCWiaFqTLg@mail.gmail.com>
	<BN3PR04MB21968C83BBA743C46CA7CAA5D9A60@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrijEwOeAEbQry259F_s-qZOe3A3GcQZ3=GSVJJyUbM8L5Q@mail.gmail.com>

Thank you very much for your help

On Tue, Nov 8, 2016 at 7:40 PM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> The problem with that file is it should be:
>
> general
>
> {
>
>
> and not general{
>
> The curly should be on a new line.
>
>
> For the neighbor section, the face-uri is the IP of the neighbor.
>
>
> Ashlesh
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr
> abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Tuesday, November 8, 2016 8:56:16 AM
> *To:* mini-ndn at lists.cs.ucla.edu
> *Subject:* [Mini-NDN] Fwd: nemune mail
>
> Hello all,
> I'm new to nlsr and I'm trying to configure the following network
> topology, means I want to produce a nlsr.conf for these nodes:
>
> [image: Inline image 1]
> I'm learning from the nlsr.conf file in mini-ndn nodes(like 'a' node), but
> when I do I get the following error using the following command while I
> don't encounter this error for the 'a' node:
>
> the command is:
>
> # nlsr -f /home/sepehr/Desktop/projectcheck/node1/nlsr.conf
>
> and the error is:
>
> Failed to parse configuration file
> /home/sepehr/Desktop/projectcheck/node1/nlsr.conf
> Error in configuration file processing! Exiting from NLSR
>
> also my configuration for node1 is :
>
> general{
>   network /ndn/
>   site /edu
>   router /%C1.Router/cs/node1
>   log-level DEBUG
>   log-dir /home/sepehr/Desktop/projectcheck//node1/log
>   seq-dir /home/sepehr/Desktop/projectcheck//node1/log
>   lsa-refresh-time 1800 ;30 minutes
> }
>
> neighbors
> {
>     neighbor
>     {
>           name /ndn/edu/%C1.Router/cs/node2
>           face-uri udp://1.0.0.2        ;not so sure about it
>           link-cost 10
>     }
>     neighbor
>     {
>           name /ndn/edu/%C1.Router/cs/node3
>           face-uri udp://1.0.0.3        ;not so sure about it
>           link-cost 10
>     }
> }
>
> hyperbolic
> {
>     state off
>     radius 0.0
>     angle 0.0
> }
>
> fib
> {
>     max-faces-per-prefix 3
> }
>
> advertising
> {
>     prefix /ndn/edu/node1
> }
>
>
> security
> {
>   validator
>   {
>     trust-anchor
>     {
>       type any
>     }
>   }
>   prefix-update-validator
>   {
>     trust-anchor
>     {
>       type any
>     }
>   }
> }
>
> which is like 'a' node in mini-ndn.
> nodes 2 to 6's configuration is similar.
>
> I'm not sure with the lines like
> face-uri udp://1.0.0.2
> in neighbor sections? how can I understand how to specify this numbers for
> my nodes?
>
> so can anyone please help me with my problem?
>
> Thank you
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161108/35cf5ad6/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-11-08 03-29-33.png
Type: image/png
Size: 9131 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161108/35cf5ad6/attachment.png>

From sepehrabdous1375 at gmail.com  Thu Nov 10 16:25:58 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Fri, 11 Nov 2016 03:55:58 +0330
Subject: [Mini-NDN] not known command in some topology
Message-ID: <CAKaOrii-KFTYhteASyeqjGvqdxOn7GdNEtbR6NSdrAQMBo-iYQ@mail.gmail.com>

Hello all,
I'm new to mini-ndn, I implemented a topology using minindnEdit as bellow

[nodes]
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


and then wrote the command:
minindn minindn.conf

but when everything was set up and I tried to use the command:
a echo "hello"
for mininet based on the following link:
https://github.com/named-data/mini-ndn/blob/master/docs/GETTING-STARTED.md

I've encountered the following error:
mininet> a echo "hello"
*** Unknown command: a echo "hello"
mininet> a nfd-status
*** Unknown command: a nfd-status
mininet> a nlsrc status
*** Unknown command: a nlsrc status

 while all of these work fine when I use default topology,

could someone help me with this problem please.

the full version is:

minindn minindn.conf
Parse of minindn.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
node1 node2 node3 node4 node5 node6
*** Adding switches:

*** Adding links:
(node1, node2) (node1, node3) (node3, node5) (node3, node6) (node4, node2)
(node4, node3) (node5, node6) (node6, node4)
*** Configuring hosts
node1 node2 node3 node4 node5 node6
Setup time: 12
*** Starting controller
c0
*** Starting 0 switches

*** Starting CLI:
mininet> a echo "hello"
*** Unknown command: a echo "hello"
mininet> a nfd-status
*** Unknown command: a nfd-status
mininet> a nlsrc status
*** Unknown command: a nlsrc status
mininet> quit
*** Stopping 1 controllers
c0
*** Stopping 8 links
........
*** Stopping 0 switches

*** Stopping 6 hosts
node1 node2 node3 node4 node5 node6
*** Done


Thank you

-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161111/ebd39e7e/attachment.html>

From agawande at memphis.edu  Thu Nov 10 16:35:03 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 11 Nov 2016 00:35:03 +0000
Subject: [Mini-NDN] not known command in some topology
In-Reply-To: <CAKaOrii-KFTYhteASyeqjGvqdxOn7GdNEtbR6NSdrAQMBo-iYQ@mail.gmail.com>
References: <CAKaOrii-KFTYhteASyeqjGvqdxOn7GdNEtbR6NSdrAQMBo-iYQ@mail.gmail.com>
Message-ID: <BN3PR04MB2196DA5E13A67159CDDE24DCD9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>

They work in default topology because the name of the node is "a."


For your topology use your node names.

Such as mini-net> node6 nfd-status


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Thursday, November 10, 2016 6:25:58 PM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] not known command in some topology

Hello all,
I'm new to mini-ndn, I implemented a topology using minindnEdit as bellow

[nodes]
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=0 nfd-log-level=INFO
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=0 nfd-log-level=INFO
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=0 nfd-log-level=INFO
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=0 nfd-log-level=INFO
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=0 nfd-log-level=INFO
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=INFO max-faces-per-prefix=0 nfd-log-level=INFO
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


and then wrote the command:
minindn minindn.conf

but when everything was set up and I tried to use the command:
a echo "hello"
for mininet based on the following link:
https://github.com/named-data/mini-ndn/blob/master/docs/GETTING-STARTED.md

I've encountered the following error:
mininet> a echo "hello"
*** Unknown command: a echo "hello"
mininet> a nfd-status
*** Unknown command: a nfd-status
mininet> a nlsrc status
*** Unknown command: a nlsrc status

 while all of these work fine when I use default topology,

could someone help me with this problem please.

the full version is:

minindn minindn.conf
Parse of minindn.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
node1 node2 node3 node4 node5 node6
*** Adding switches:

*** Adding links:
(node1, node2) (node1, node3) (node3, node5) (node3, node6) (node4, node2) (node4, node3) (node5, node6) (node6, node4)
*** Configuring hosts
node1 node2 node3 node4 node5 node6
Setup time: 12
*** Starting controller
c0
*** Starting 0 switches

*** Starting CLI:
mininet> a echo "hello"
*** Unknown command: a echo "hello"
mininet> a nfd-status
*** Unknown command: a nfd-status
mininet> a nlsrc status
*** Unknown command: a nlsrc status
mininet> quit
*** Stopping 1 controllers
c0
*** Stopping 8 links
........
*** Stopping 0 switches

*** Stopping 6 hosts
node1 node2 node3 node4 node5 node6
*** Done


Thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161111/963e17d0/attachment.html>

From sepehrabdous1375 at gmail.com  Fri Nov 11 14:40:01 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sat, 12 Nov 2016 02:10:01 +0330
Subject: [Mini-NDN] minindn experiment
Message-ID: <CAKaOriiKUhKkyd2Fsyv+nZWjD8PRWe9jt3p+n690z2s-RKUtjg@mail.gmail.com>

Hello all,
I'm trying to write a simple experiment for using in minindn
so I make a file called ex1_experiment.py
and put the following code in it:

from ndn.experiments.experiment import Experiment

class ExampleExperiment(Experiment):
    def __init__(self, args):
        Experiment.__init__(self, args)

    def setup(self):
        for host in self.net.hosts:
            host.cmd("ndnpingserver host.name &")

    def run(self):
        for host in self.net.hosts:
            # By default status.txt would be stored
            # at /tmp/host/status.txt
            host.cmd("nfd-status > status.txt")

Experiment.register("ee", ExampleExperiment)

and save it
but when I try to use it by:
sudo minindn --experiment=ee
I get the following error

No experiment named ee


can someone help me with this please?
thank you

-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161112/448cf71f/attachment.html>

From agawande at memphis.edu  Fri Nov 11 14:46:00 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 11 Nov 2016 22:46:00 +0000
Subject: [Mini-NDN] minindn experiment
Message-ID: <BN3PR04MB2196281AA529F990BF439151D9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>

Did you install Mini-NDN again after adding the experiment?

Ashlesh

On Nov 11, 2016 4:40 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
Hello all,
I'm trying to write a simple experiment for using in minindn
so I make a file called ex1_experiment.py
and put the following code in it:

from ndn.experiments.experiment import Experiment

class ExampleExperiment(Experiment):
    def __init__(self, args):
        Experiment.__init__(self, args)

    def setup(self):
        for host in self.net.hosts:
            host.cmd("ndnpingserver host.name<http://host.name> &")

    def run(self):
        for host in self.net.hosts:
            # By default status.txt would be stored
            # at /tmp/host/status.txt
            host.cmd("nfd-status > status.txt")

Experiment.register("ee", ExampleExperiment)

and save it
but when I try to use it by:
sudo minindn --experiment=ee
I get the following error

No experiment named ee


can someone help me with this please?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161111/490b8e10/attachment.html>

From sepehrabdous1375 at gmail.com  Fri Nov 11 14:48:40 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sat, 12 Nov 2016 02:18:40 +0330
Subject: [Mini-NDN] minindn experiment
In-Reply-To: <BN3PR04MB2196281AA529F990BF439151D9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <BN3PR04MB2196281AA529F990BF439151D9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrigdqQ86_9E+5JH5SFkUPVRP0fWN7Ys8uJvqDbmzT5DXmw@mail.gmail.com>

no should I install it again?


On Sat, Nov 12, 2016 at 2:16 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> Did you install Mini-NDN again after adding the experiment?
>
> Ashlesh
> On Nov 11, 2016 4:40 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
>
> Hello all,
> I'm trying to write a simple experiment for using in minindn
> so I make a file called ex1_experiment.py
> and put the following code in it:
>
> from ndn.experiments.experiment import Experiment
>
> class ExampleExperiment(Experiment):
>     def __init__(self, args):
>         Experiment.__init__(self, args)
>
>     def setup(self):
>         for host in self.net.hosts:
>             host.cmd("ndnpingserver host.name &")
>
>     def run(self):
>         for host in self.net.hosts:
>             # By default status.txt would be stored
>             # at /tmp/host/status.txt
>             host.cmd("nfd-status > status.txt")
>
> Experiment.register("ee", ExampleExperiment)
>
> and save it
> but when I try to use it by:
> sudo minindn --experiment=ee
> I get the following error
>
> No experiment named ee
>
>
> can someone help me with this please?
> thank you
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>
>


-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161112/34321765/attachment.html>

From agawande at memphis.edu  Fri Nov 11 14:49:24 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 11 Nov 2016 22:49:24 +0000
Subject: [Mini-NDN] minindn experiment
Message-ID: <BN3PR04MB21969713BB4BA20B8D18959DD9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>

Yes.

Ashlesh

On Nov 11, 2016 4:48 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
no should I install it again?


On Sat, Nov 12, 2016 at 2:16 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Did you install Mini-NDN again after adding the experiment?

Ashlesh

On Nov 11, 2016 4:40 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
Hello all,
I'm trying to write a simple experiment for using in minindn
so I make a file called ex1_experiment.py
and put the following code in it:

from ndn.experiments.experiment import Experiment

class ExampleExperiment(Experiment):
    def __init__(self, args):
        Experiment.__init__(self, args)

    def setup(self):
        for host in self.net.hosts:
            host.cmd("ndnpingserver host.name<http://host.name> &")

    def run(self):
        for host in self.net.hosts:
            # By default status.txt would be stored
            # at /tmp/host/status.txt
            host.cmd("nfd-status > status.txt")

Experiment.register("ee", ExampleExperiment)

and save it
but when I try to use it by:
sudo minindn --experiment=ee
I get the following error

No experiment named ee


can someone help me with this please?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161111/d30c850d/attachment.html>

From sepehrabdous1375 at gmail.com  Fri Nov 11 14:50:46 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sat, 12 Nov 2016 02:20:46 +0330
Subject: [Mini-NDN] minindn experiment
In-Reply-To: <BN3PR04MB21969713BB4BA20B8D18959DD9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <BN3PR04MB21969713BB4BA20B8D18959DD9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrigD0QS+4wuvFUJJom5M=XVToy4+JScc7Ghkw=ZP2--fPw@mail.gmail.com>

You mean I should run install.sh again?

On Nov 12, 2016 2:19 AM, "Ashlesh Gawande (agawande)" <agawande at memphis.edu>
wrote:

> Yes.
>
> Ashlesh
> On Nov 11, 2016 4:48 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
>
> no should I install it again?
>
>
> On Sat, Nov 12, 2016 at 2:16 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
> Did you install Mini-NDN again after adding the experiment?
>
> Ashlesh
> On Nov 11, 2016 4:40 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
>
> Hello all,
> I'm trying to write a simple experiment for using in minindn
> so I make a file called ex1_experiment.py
> and put the following code in it:
>
> from ndn.experiments.experiment import Experiment
>
> class ExampleExperiment(Experiment):
>     def __init__(self, args):
>         Experiment.__init__(self, args)
>
>     def setup(self):
>         for host in self.net.hosts:
>             host.cmd("ndnpingserver host.name &")
>
>     def run(self):
>         for host in self.net.hosts:
>             # By default status.txt would be stored
>             # at /tmp/host/status.txt
>             host.cmd("nfd-status > status.txt")
>
> Experiment.register("ee", ExampleExperiment)
>
> and save it
> but when I try to use it by:
> sudo minindn --experiment=ee
> I get the following error
>
> No experiment named ee
>
>
> can someone help me with this please?
> thank you
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161112/4f444598/attachment.html>

From agawande at memphis.edu  Fri Nov 11 14:52:42 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 11 Nov 2016 22:52:42 +0000
Subject: [Mini-NDN] minindn experiment
Message-ID: <BN3PR04MB219699D7BEF55E0C193B991CD9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>

Yes just ./install.sh -i

That would install only Mini-NDN and not the dependencies.

Ashlesh

On Nov 11, 2016 4:50 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:

You mean I should run install.sh again?

On Nov 12, 2016 2:19 AM, "Ashlesh Gawande (agawande)" <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Yes.

Ashlesh

On Nov 11, 2016 4:48 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
no should I install it again?


On Sat, Nov 12, 2016 at 2:16 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Did you install Mini-NDN again after adding the experiment?

Ashlesh

On Nov 11, 2016 4:40 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
Hello all,
I'm trying to write a simple experiment for using in minindn
so I make a file called ex1_experiment.py
and put the following code in it:

from ndn.experiments.experiment import Experiment

class ExampleExperiment(Experiment):
    def __init__(self, args):
        Experiment.__init__(self, args)

    def setup(self):
        for host in self.net.hosts:
            host.cmd("ndnpingserver host.name<http://host.name> &")

    def run(self):
        for host in self.net.hosts:
            # By default status.txt would be stored
            # at /tmp/host/status.txt
            host.cmd("nfd-status > status.txt")

Experiment.register("ee", ExampleExperiment)

and save it
but when I try to use it by:
sudo minindn --experiment=ee
I get the following error

No experiment named ee


can someone help me with this please?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161111/1a7215f9/attachment.html>

From sepehrabdous1375 at gmail.com  Fri Nov 11 14:53:32 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sat, 12 Nov 2016 02:23:32 +0330
Subject: [Mini-NDN] minindn experiment
In-Reply-To: <BN3PR04MB219699D7BEF55E0C193B991CD9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <BN3PR04MB219699D7BEF55E0C193B991CD9BB0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrih8ponF-g5tRUQ2HizOArFm4KMfzqr0Km3OEZAfXqHm8Q@mail.gmail.com>

Thank you very much

On Nov 12, 2016 2:22 AM, "Ashlesh Gawande (agawande)" <agawande at memphis.edu>
wrote:

> Yes just ./install.sh -i
>
> That would install only Mini-NDN and not the dependencies.
>
> Ashlesh
> On Nov 11, 2016 4:50 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
>
> You mean I should run install.sh again?
>
> On Nov 12, 2016 2:19 AM, "Ashlesh Gawande (agawande)" <
> agawande at memphis.edu> wrote:
>
> Yes.
>
> Ashlesh
> On Nov 11, 2016 4:48 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
>
> no should I install it again?
>
>
> On Sat, Nov 12, 2016 at 2:16 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
> Did you install Mini-NDN again after adding the experiment?
>
> Ashlesh
> On Nov 11, 2016 4:40 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
>
> Hello all,
> I'm trying to write a simple experiment for using in minindn
> so I make a file called ex1_experiment.py
> and put the following code in it:
>
> from ndn.experiments.experiment import Experiment
>
> class ExampleExperiment(Experiment):
>     def __init__(self, args):
>         Experiment.__init__(self, args)
>
>     def setup(self):
>         for host in self.net.hosts:
>             host.cmd("ndnpingserver host.name &")
>
>     def run(self):
>         for host in self.net.hosts:
>             # By default status.txt would be stored
>             # at /tmp/host/status.txt
>             host.cmd("nfd-status > status.txt")
>
> Experiment.register("ee", ExampleExperiment)
>
> and save it
> but when I try to use it by:
> sudo minindn --experiment=ee
> I get the following error
>
> No experiment named ee
>
>
> can someone help me with this please?
> thank you
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161112/5f9d3fe2/attachment.html>

From sepehrabdous1375 at gmail.com  Mon Nov 14 15:06:21 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 15 Nov 2016 02:36:21 +0330
Subject: [Mini-NDN] bringing out a node
Message-ID: <CAKaOrihSmUcvwSpyRY0g360xE4pT=aG0tYgLnM=AwjPaLqjQGA@mail.gmail.com>

Hello all,
I'm trying to write an experiment for the topology below:
[image: Inline image 1]
and in this experiment I just want to bring out node4(like that node 4 has
failed) is there anything I can do in the experiment code to do this?
Thank you

-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161115/be451914/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-11-08 03-29-33.png
Type: image/png
Size: 9131 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161115/be451914/attachment.png>

From Matteo.Bertolino at eurecom.fr  Mon Nov 14 15:23:05 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Tue, 15 Nov 2016 00:23:05 +0100
Subject: [Mini-NDN] bringing out a node
In-Reply-To: <CAKaOrihSmUcvwSpyRY0g360xE4pT=aG0tYgLnM=AwjPaLqjQGA@mail.gmail.com>
References: <CAKaOrihSmUcvwSpyRY0g360xE4pT=aG0tYgLnM=AwjPaLqjQGA@mail.gmail.com>
Message-ID: <20161115002305.jd5mge60w00sskck@webmail.eurecom.fr>

Hi,

I think that you can just running the node4 program and write manually  
in the mini consolle "node4 nfd-stop".
Probably you've to stop also nlsr instance in order to do a clean  
failure simulation, but nfd is enough. I get refer about nfd-start and  
nfd-stop command that I read here:  
http://named-data.net/doc/NFD/current/INSTALL.html

A little better, you can just simulate this running a timer on the  
program running in node4. When timer will expires, you can stop the  
forwarding daemon.
For example, in pseudo-code:

function timer:
     sleep(n seconds)
     system ("node4name nfd-stop")
     exit

main:
    thread t(function timer)
    t.start
    t.detach
    node.initilize
    node.run


Hope that works.
Matteo

Quoting sepehr abdous <sepehrabdous1375 at gmail.com>:

> Hello all,
> I'm trying to write an experiment for the topology below:
> [image: Inline image 1]
> and in this experiment I just want to bring out node4(like that node 4 has
> failed) is there anything I can do in the experiment code to do this?
> Thank you
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr




From agawande at memphis.edu  Mon Nov 14 15:49:22 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 14 Nov 2016 23:49:22 +0000
Subject: [Mini-NDN] bringing out a node
In-Reply-To: <20161115002305.jd5mge60w00sskck@webmail.eurecom.fr>
References: <CAKaOrihSmUcvwSpyRY0g360xE4pT=aG0tYgLnM=AwjPaLqjQGA@mail.gmail.com>,
	<20161115002305.jd5mge60w00sskck@webmail.eurecom.fr>
Message-ID: <BN3PR04MB21961FA264F3DDA5C604201DD9BC0@BN3PR04MB2196.namprd04.prod.outlook.com>

nfd-stop will stop all nodes as it kills all NFDs running on the system.


Take a look at the failure experiment:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/failure_experiment.py#L47


https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L102


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Monday, November 14, 2016 5:23:05 PM
To: sepehr abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] bringing out a node

Hi,

I think that you can just running the node4 program and write manually
in the mini consolle "node4 nfd-stop".
Probably you've to stop also nlsr instance in order to do a clean
failure simulation, but nfd is enough. I get refer about nfd-start and
nfd-stop command that I read here:
http://named-data.net/doc/NFD/current/INSTALL.html

A little better, you can just simulate this running a timer on the
program running in node4. When timer will expires, you can stop the
forwarding daemon.
For example, in pseudo-code:

function timer:
     sleep(n seconds)
     system ("node4name nfd-stop")
     exit

main:
    thread t(function timer)
    t.start
    t.detach
    node.initilize
    node.run


Hope that works.
Matteo

Quoting sepehr abdous <sepehrabdous1375 at gmail.com>:

> Hello all,
> I'm trying to write an experiment for the topology below:
> [image: Inline image 1]
> and in this experiment I just want to bring out node4(like that node 4 has
> failed) is there anything I can do in the experiment code to do this?
> Thank you
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr


_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161114/220dab8e/attachment.html>

From sepehrabdous1375 at gmail.com  Tue Nov 15 11:31:35 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 15 Nov 2016 23:01:35 +0330
Subject: [Mini-NDN] bringing out a node
In-Reply-To: <BN3PR04MB21961FA264F3DDA5C604201DD9BC0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrihSmUcvwSpyRY0g360xE4pT=aG0tYgLnM=AwjPaLqjQGA@mail.gmail.com>
	<20161115002305.jd5mge60w00sskck@webmail.eurecom.fr>
	<BN3PR04MB21961FA264F3DDA5C604201DD9BC0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOriiki9zDzkOP8zWV4g4nmDxiNT5G1MxvF2ABFzBaMbd_Vw@mail.gmail.com>

Thank you very much for your help

On Tue, Nov 15, 2016 at 3:19 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> nfd-stop will stop all nodes as it kills all NFDs running on the system.
>
>
> Take a look at the failure experiment:
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/
> experiments/failure_experiment.py#L47
>
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/
> experiments/experiment.py#L102
>
>
> Ashlesh
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Matteo
> Bertolino <Matteo.Bertolino at eurecom.fr>
> *Sent:* Monday, November 14, 2016 5:23:05 PM
> *To:* sepehr abdous
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] bringing out a node
>
> Hi,
>
> I think that you can just running the node4 program and write manually
> in the mini consolle "node4 nfd-stop".
> Probably you've to stop also nlsr instance in order to do a clean
> failure simulation, but nfd is enough. I get refer about nfd-start and
> nfd-stop command that I read here:
> http://named-data.net/doc/NFD/current/INSTALL.html
>
> A little better, you can just simulate this running a timer on the
> program running in node4. When timer will expires, you can stop the
> forwarding daemon.
> For example, in pseudo-code:
>
> function timer:
>      sleep(n seconds)
>      system ("node4name nfd-stop")
>      exit
>
> main:
>     thread t(function timer)
>     t.start
>     t.detach
>     node.initilize
>     node.run
>
>
> Hope that works.
> Matteo
>
> Quoting sepehr abdous <sepehrabdous1375 at gmail.com>:
>
> > Hello all,
> > I'm trying to write an experiment for the topology below:
> > [image: Inline image 1]
> > and in this experiment I just want to bring out node4(like that node 4
> has
> > failed) is there anything I can do in the experiment code to do this?
> > Thank you
> >
> > --
> > Sepehr Abdous
> > Faculty: abdous at ce.sharif.edu
> > Yahoo mail: sepehrabdous at yahoo.com
> > Cellphone:+989194030591
> > School of computer engineering
> > Sharif University of Technology
> > Tehran, Iran
> >
>
>
>
> ------------------------------------------------------------
> -------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161115/5992a152/attachment.html>

From Matteo.Bertolino at eurecom.fr  Thu Nov 17 09:47:54 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Thu, 17 Nov 2016 18:47:54 +0100
Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network
Message-ID: <20161117184754.h6jvnupy0c4csc4c@webmail.eurecom.fr>

Hello,
I followed this doc:  
https://github.com/named-data/mini-ndn/blob/master/docs/CONNECT-TO-OUTSIDE.md

Unfortunately, at this point:

"Run Mini-NDN with the simple topology and issue ifconfig on the local  
machine to confirm the addition of the interface. You should be able  
to locate "root-eth0" "

I am not able to see the node root neither root-eth0.

Do you manage to run this scenario?
Thanks,
Matteo

-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr


From agawande at memphis.edu  Thu Nov 17 09:52:10 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 17 Nov 2016 17:52:10 +0000
Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network
In-Reply-To: <20161117184754.h6jvnupy0c4csc4c@webmail.eurecom.fr>
References: <20161117184754.h6jvnupy0c4csc4c@webmail.eurecom.fr>
Message-ID: <BN3PR04MB219676BA308033B4C236E267D9B10@BN3PR04MB2196.namprd04.prod.outlook.com>

Are there any errors when Mini-NDN starts?


What is the output of "a ifconfig" in Mini-NDN?


And the output of ifconfig on the machine (not in Mini-NDN)?


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Thursday, November 17, 2016 11:47:54 AM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network

Hello,
I followed this doc:
https://github.com/named-data/mini-ndn/blob/master/docs/CONNECT-TO-OUTSIDE.md

Unfortunately, at this point:

"Run Mini-NDN with the simple topology and issue ifconfig on the local
machine to confirm the addition of the interface. You should be able
to locate "root-eth0" "

I am not able to see the node root neither root-eth0.

Do you manage to run this scenario?
Thanks,
Matteo

-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr

_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161117/64c74954/attachment-0001.html>

From Matteo.Bertolino at eurecom.fr  Fri Nov 18 01:21:53 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Fri, 18 Nov 2016 10:21:53 +0100
Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network
In-Reply-To: <BN3PR04MB219676BA308033B4C236E267D9B10@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <20161117184754.h6jvnupy0c4csc4c@webmail.eurecom.fr>
	<BN3PR04MB219676BA308033B4C236E267D9B10@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <20161118102153.1goknertsgk4ws44@webmail.eurecom.fr>

Dear Ashlesh,
No Errors at the beginning of MiniNDN, and no errors in general.  
However, doing "switch off and reboot" I've some improvements. The  
root-eth0 is present just running ifconfig in the machine. Is it enough?

My output are:

1) MININDN

mininet> a ifconfig
a-eth0    Link encap:Ethernet  HWaddr 12:b7:c7:b0:99:c7
           inet addr:1.0.0.1  Bcast:1.0.0.3  Mask:255.255.255.252
           inet6 addr: fe80::10b7:c7ff:feb0:99c7/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:13 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1404 (1.4 KB)  TX bytes:1404 (1.4 KB)

a-eth1    Link encap:Ethernet  HWaddr fe:2c:28:35:26:dc
           inet addr:1.0.0.5  Bcast:1.0.0.7  Mask:255.255.255.252
           inet6 addr: fe80::fc2c:28ff:fe35:26dc/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:13 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1404 (1.4 KB)  TX bytes:1404 (1.4 KB)

a-eth2    Link encap:Ethernet  HWaddr 26:8e:b9:9a:ec:8a
           inet addr:1.0.0.10  Bcast:1.0.0.11  Mask:255.255.255.252
           inet6 addr: fe80::248e:b9ff:fe9a:ec8a/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
           TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:851 (851.0 B)  TX bytes:931 (931.0 B)

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

------------------------------------------------------------------
------------------------------------------------------------------

2) IN THE MACHINE
ndn at ndn:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:35:af:94:4b
           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
           inet6 addr: fe80::216:35ff:feaf:944b/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:25315 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13892 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:9648263 (9.6 MB)  TX bytes:1989463 (1.9 MB)

eth1      Link encap:Ethernet  HWaddr 52:54:00:12:34:56
           inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
           inet6 addr: fe80::5054:ff:fe12:3456/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:5365 errors:0 dropped:0 overruns:0 frame:0
           TX packets:5399 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:769454 (769.4 KB)  TX bytes:781753 (781.7 KB)

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:23 errors:0 dropped:0 overruns:0 frame:0
           TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1
           RX bytes:2278 (2.2 KB)  TX bytes:2278 (2.2 KB)

root-eth0 Link encap:Ethernet  HWaddr b2:6e:70:b5:4d:60
           inet addr:1.0.0.9  Bcast:1.0.0.11  Mask:255.255.255.252
           inet6 addr: fe80::b06e:70ff:feb5:4d60/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:16 errors:0 dropped:0 overruns:0 frame:0
           TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1190 (1.1 KB)  TX bytes:1138 (1.1 KB)


Bests,
Matteo


Quoting "Ashlesh Gawande (agawande)" <agawande at memphis.edu>:

> Are there any errors when Mini-NDN starts?
>
>
> What is the output of "a ifconfig" in Mini-NDN?
>
>
> And the output of ifconfig on the machine (not in Mini-NDN)?
>
>
> Ashlesh
>
> ________________________________
> From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of   
> Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
> Sent: Thursday, November 17, 2016 11:47:54 AM
> To: mini-ndn at lists.cs.ucla.edu
> Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network
>
> Hello,
> I followed this doc:
> https://github.com/named-data/mini-ndn/blob/master/docs/CONNECT-TO-OUTSIDE.md
>
> Unfortunately, at this point:
>
> "Run Mini-NDN with the simple topology and issue ifconfig on the local
> machine to confirm the addition of the interface. You should be able
> to locate "root-eth0" "
>
> I am not able to see the node root neither root-eth0.
>
> Do you manage to run this scenario?
> Thanks,
> Matteo
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr



From sepehrabdous1375 at gmail.com  Fri Nov 18 04:18:12 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Fri, 18 Nov 2016 15:48:12 +0330
Subject: [Mini-NDN] Fwd: result
In-Reply-To: <CAKaOrijzFQhb+iJDb4sZ2iw6kPOFKtg-=9Dw2M9KqU2wfgYtvw@mail.gmail.com>
References: <CAKaOrigoyZk-NkSBn+0XtoHqs9hZo0N0Ya97SoeDryAPuOsOqQ@mail.gmail.com>
	<CAOU4Q-1rTnEW66dB36rqfP-ioXS+kk7GGtQgWv0xhxhprPAkvw@mail.gmail.com>
	<CAKaOriiA-fPqrpLEHXa9uUrJBqG9+ssHo=wcMihLF7EmF7sQrw@mail.gmail.com>
	<CAKaOrigJ1_OQ6j2OU-BUGa7Ng7XmJe0wUjH5gQDMkV0zK=Q01A@mail.gmail.com>
	<CAOU4Q-0FHsnteZK9vTuEaG5ee+u=SAB1vS1YgzxaYtAQ+-NodA@mail.gmail.com>
	<CAKaOriiAppkXca0-r5zhr_7Jpnb7gvjwc-yL+OdB62-4B10TGA@mail.gmail.com>
	<CAOU4Q-2XtN9yBS5j6VGLnJnCcsa3g3whD4h3hTTW8rC0uP7n3w@mail.gmail.com>
	<CAKaOriiY_i+XSFvHujTtNT5YmLF5n4JM3=E7sHO4YtFDKwx98Q@mail.gmail.com>
	<CAKaOrigXOXTqxPXzPdFHASUh3VoY6WkS_-t44NGw+xJN90ZQzQ@mail.gmail.com>
	<CAOU4Q-08ViM7eXU8dOTd-wZF3dacq-N7-mT9wZCyWJpj14JuBQ@mail.gmail.com>
	<CAKaOriiRv1ZLh2kT7FtQN0virOUXfE_PM9gvk3J8n0e1jHhTLA@mail.gmail.com>
	<CAKaOrigjgCZhd5+YTHDaLB3vyJukSMREpeykaMmr9_U1xgEJeg@mail.gmail.com>
	<CAOU4Q-2CdHop_M0xorpf54UQbGQV8pTYz_MYOv4dBWTHRiwejg@mail.gmail.com>
	<CAKaOrii1GqfsrFXGZjnqzFe2gPtAyFgwQvhrbh-3JzO-HdbiQA@mail.gmail.com>
	<CAKaOrigqYwKx4U2ec9DsYYzSKfFO4PpYQuf-toisBtGA-Td0Vw@mail.gmail.com>
	<CAKaOrihxw1cQqF74OqP-k8jWaUKkFznZX4Qmoq1F2x9Cyp9wKQ@mail.gmail.com>
	<CAKaOrijw6p1zwZK9dU82bO7VbHJP_aUNDFtwX7B81VJiDcJ9ng@mail.gmail.com>
	<CAKaOriiG8E5HfLoOfOyn0UTYHOFqro7U7DBATFjwpCQYKFxjaQ@mail.gmail.com>
	<CAOU4Q-2dbugw=sy8bGhPLUFD3FZN-XLaaedkAYRQeLP51dVyKw@mail.gmail.com>
	<CAKaOriipjJxwTNEkF4wV0WGFEFoUXKR6rfDqqLGZ3XNeU9Ju6w@mail.gmail.com>
	<CAOU4Q-1iPU6_F4f-u0RJ6B13pzv-M21ezanwfKC3e3iFv5mTnQ@mail.gmail.com>
	<CAKaOrii7Kroecx5EVaGjQQt0jYmRLnqnfPVD9o7VFRG=iR7CJg@mail.gmail.com>
	<CAOU4Q-11P3NY6sQpdK6MoyCLnLVfCgQv1Je7FG9y_WwgZeM2cA@mail.gmail.com>
	<CAKaOrij9dSLzuwfZyhLr5hDgKBAcJUY7DX4Pi+b64ib=Ac=MFg@mail.gmail.com>
	<CAKaOrigPPaFPrtrjsZ=Yd6sg_rk9hRT9AWEcu_qxuBgOZqVXvA@mail.gmail.com>
	<CAKaOrijnv8q8THZabNttKE_VzgWOAkEzxUda6cMZbWf3=v_pxQ@mail.gmail.com>
	<CAOU4Q-3V_nDvpPHdviOVqBd8KxSaF6bqcOh5Nmz0x8ejk5mTzQ@mail.gmail.com>
	<CAKaOrihu+qH=NZ1AZJwPttuurumcDmCRP5Y2kEy+BE-Gge8hhg@mail.gmail.com>
	<CAOU4Q-0eKXR15zkq75-oM=XhN5OzUXFDWERPw3d6+CPf4tshGw@mail.gmail.com>
	<CAKaOrij3uPR2cDdN2BPCFFhdABN0AK=AuvTPzjacm34J4N0d_w@mail.gmail.com>
	<CAOU4Q-0zUs1XVMTFd2QdreeXKOJVzkRar-qeJsxU2uBSfaHFvQ@mail.gmail.com>
	<CAKaOrigk9buDyRROBT8P75D6jUd_OdGfr5wRsNGXzfrS6hq9vw@mail.gmail.com>
	<CAOU4Q-0MFez-8Z9MV_JGeh35oarR0WMo1s-vFA-a0U8jJ7oKrA@mail.gmail.com>
	<CAKaOriiKm7CJYrRwMNTbzs=_f7nMBuJijThqk3ZhLd4UhPFHDA@mail.gmail.com>
	<CAKaOrijzFQhb+iJDb4sZ2iw6kPOFKtg-=9Dw2M9KqU2wfgYtvw@mail.gmail.com>
Message-ID: <CAKaOrij0LLEfVkzi1CJ8YUn+9DvUG9r05Y0JXA8d__2eZyynuA@mail.gmail.com>

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[image: Inline image 1]
so I use minindnedit to implement it with the following information:
[image: Inline image 2]
and based on the paper which represents this topology it is expected to get
this figure from it's information:
[image: Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails,
but when I try to implement it using pingall experiment my figure will come
out like this:
[image: Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected,
any idea why it is happening?
thank you

2016-11-18 11:07 GMT+03:30 sepehr abdous <sepehrabdous1375 at gmail.com>:

> salam khubid?
> man harchi var miram in navasan ha hal nemsihe alan tu mailing list
> miporsam
>
> On Fri, Nov 18, 2016 at 12:41 AM, HAMED Yousefi <doctorhy at gmail.com>
> wrote:
>
>> ?
>>
>> 2016-11-16 10:06 GMT-05:00 sepehr abdous <sepehrabdous1375 at gmail.com>:
>>
>>> khahesh... ;)
>>>
>>> 2016-11-16 18:17 GMT+03:30 HAMED Yousefi <doctorhy at gmail.com>:
>>>
>>>> ok, merci
>>>>
>>>> 2016-11-16 9:23 GMT-05:00 sepehr abdous <sepehrabdous1375 at gmail.com>:
>>>>
>>>>> aha ok hala dobare khodam yekam rush kar mikonam age didam be dead end
>>>>> khordam miporsam tu mailing list
>>>>>
>>>>> 2016-11-16 17:42 GMT+03:30 HAMED Yousefi <doctorhy at gmail.com>:
>>>>>
>>>>>> Chera pung bayad fargh kone, age bayad fargh kome pas nlsr chera
>>>>>> nakarde? Va dar morede oon tafavot in result i ke to alan gerrfti ghabeleb
>>>>>> erae nist, nlsr ro bebinnghashang tafavotaa moshakhase vali maale to
>>>>>> nist, inke tafavot dashte bashan bakhsshi az ghaziast amma inke result
>>>>>> ghbele erae bashe bahse digast. Be har haal shekle to ghabele ghabool nist
>>>>>> choon nslr h navasan nadare ham tafavotesh vazehe, dar nahayat age
>>>>>> nemidooni dalilesho mail bezan sheklaa ro befrest va az foroom bepors
>>>>>> dalile in 2 ta soal chie?
>>>>>>
>>>>>>
>>>>>> On Wednesday, November 16, 2016, sepehr abdous <
>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>
>>>>>>> akhe man hes mikonam k ba tavajjoh be in k zamane ping e nabayad
>>>>>>> entezar dashte bashim daghighan yeki she k
>>>>>>> az tarafi age bbinid ghermez tu shekle paper yekam az abi ha
>>>>>>> balataran na kheili k tu shekle man ham in has beine 120 va 180,
>>>>>>> bara hamin fkr mikonam nabayad entezar dashte bashim daghighan hamun
>>>>>>> nemudar tolid she balke bayad nemudar az ravande kolli e shekl peiravi kone
>>>>>>> k age deghghat konid peiravi mikone...
>>>>>>>
>>>>>>> On Wed, Nov 16, 2016 at 5:07 PM, HAMED Yousefi <doctorhy at gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Salam sepehr  khodet ke minini dorost nist, alan tarakomesh khoob
>>>>>>>> shod amma hamoon joor ke mibini nemoodarat roo hame dar soorati ke bade 120
>>>>>>>> bayad ghermez az aabi balatar bashe, nokte dige inke nemidoonam to chera
>>>>>>>> inghadr navasan hast too nemoodaret dar soorati ke shekle nlsr hich
>>>>>>>> noghteye ezafi nadare ta zamani ke masir miahkane ya recover mishe, dar
>>>>>>>> kol shekle nlsr ro bezar jolot alan in shekl shabihe oone?! Pas nemifahmam
>>>>>>>> vaghti in sheklaa yeki nist chera miporsi ok e?!
>>>>>>>>
>>>>>>>> On Wednesday, November 16, 2016, sepehr abdous <
>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> salam didid shekl ro ?
>>>>>>>>> be nazaretun ok shode ya hanuzam bug dare?
>>>>>>>>>
>>>>>>>>> On Wed, Nov 16, 2016 at 2:47 PM, sepehr abdous <
>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>
>>>>>>>>>> salam shekl in shod:
>>>>>>>>>> [image: Inline image 1]
>>>>>>>>>> chetore?
>>>>>>>>>>
>>>>>>>>>> 2016-11-16 14:25 GMT+03:30 sepehr abdous <
>>>>>>>>>> sepehrabdous1375 at gmail.com>:
>>>>>>>>>>
>>>>>>>>>>> salam bbinid man kollan in dafe vaseye tedad ping ha mahdudiat
>>>>>>>>>>> nazashtam
>>>>>>>>>>> va goftam ta mitune tu 200 sanie ping anjam bede
>>>>>>>>>>> bbinid tarakomesh ok shode?
>>>>>>>>>>> fkr konam ok shode...
>>>>>>>>>>>
>>>>>>>>>>> [image: Inline image 1]
>>>>>>>>>>> bbinid age ok shode baghie ro ham bekesham...
>>>>>>>>>>> in alan halate without any fail e...
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Wed, Nov 16, 2016 at 3:27 AM, HAMED Yousefi <
>>>>>>>>>>> doctorhy at gmail.com> wrote:
>>>>>>>>>>>
>>>>>>>>>>>> bashe merci, shab khosh
>>>>>>>>>>>>
>>>>>>>>>>>> On Tue, Nov 15, 2016 at 6:56 PM, sepehr abdous <
>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> alan ye chizi be zehnam resid shayad moshkelesh un bashe farda
>>>>>>>>>>>>> dar asra e vaght miram soraghesh
>>>>>>>>>>>>> shabetun bekheir
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Wed, Nov 16, 2016 at 3:19 AM, HAMED Yousefi <
>>>>>>>>>>>>> doctorhy at gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> Nemidoonam vali mibini ke oon tarakomesh bishtare shayad 1
>>>>>>>>>>>>>> sanie 2 sanie nist..5 sanie ii baahe, nemidoonam
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Tuesday, November 15, 2016, sepehr abdous <
>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> e ras migid un tahesh yekam moshkel dare
>>>>>>>>>>>>>>> vali az tedadesh mage be in shekl nis k 200 noghte ast
>>>>>>>>>>>>>>> yani nPings=200 set shode...?
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> On Wed, Nov 16, 2016 at 3:08 AM, HAMED Yousefi <
>>>>>>>>>>>>>>> doctorhy at gmail.com> wrote:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> Sepehr man hamchenan moahkelam ine ke in ahekl ba oon chizi
>>>>>>>>>>>>>>>> ke too paper e ham too takam az dide mehvare X (na y) fargh dare, yani
>>>>>>>>>>>>>>>> tedade sample aa kamtare va noghtehaa joda jodan, va mehemtar az oon oon
>>>>>>>>>>>>>>>>  shekl hanooz ba in fargh dare alan khodet az sanie 180 be bado moyese kon
>>>>>>>>>>>>>>>> asan inaa shabahati nadaran!
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>> On Tuesday, November 15, 2016, sepehr abdous <
>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> didid?
>>>>>>>>>>>>>>>>> nazaretun chie?
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> On Wed, Nov 16, 2016 at 2:23 AM, sepehr abdous <
>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> inam tu kaghaze nime logarithmi
>>>>>>>>>>>>>>>>>> [image: Inline image 1]
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> 2016-11-16 2:04 GMT+03:30 sepehr abdous <
>>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com>:
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> [image: Inline image 1]
>>>>>>>>>>>>>>>>>>> bbinid man ye tozih bedam:
>>>>>>>>>>>>>>>>>>> alan tuye shekle paper umade tu mehvar haye logarithm i
>>>>>>>>>>>>>>>>>>> rasmesh karde yani masalan az 1(ke hamun 10^0) shoru karde ta bala. va
>>>>>>>>>>>>>>>>>>> faseleye 10 ta 100 va 100 ta 1000 barabare k in yani logarithm i
>>>>>>>>>>>>>>>>>>> hala man umadam az dade ha logarithm gereftam va rasmesh
>>>>>>>>>>>>>>>>>>> kardam yani tu shekle man 0 neshun dahande 10^0=1 e va 1 hamun 10^1=10 e
>>>>>>>>>>>>>>>>>>> hala man moshkel dashtam tu in k chejuri tu matlab tu
>>>>>>>>>>>>>>>>>>> kaghaze nime logarithm i bekesham search zadam kheili nafahmidam vali alan
>>>>>>>>>>>>>>>>>>> estedlal mikonam k shekl shabihe paper e
>>>>>>>>>>>>>>>>>>> bbinid tu kaghaze nime logarithm i tu mehvare y har
>>>>>>>>>>>>>>>>>>> vahede kuchik neshun dahande 0.1 hast va age tu shekl e paper nega konid
>>>>>>>>>>>>>>>>>>> axare maghadir e abi nazdik be 5 omin vahede kuchik an k yani hamun 0.5 va
>>>>>>>>>>>>>>>>>>> tu shekle man ham vahed haye abi hame taghriban hodude 0.5 navasan mikonan
>>>>>>>>>>>>>>>>>>> haminjuri ham baraye ghermez ha k yekam bala taran hala
>>>>>>>>>>>>>>>>>>> chon harchi tu kaghaze nime logarithm i b akhar nazdik mishim faseleye
>>>>>>>>>>>>>>>>>>> beine vahed haye kuchik kamtar mishe yani masalan faseleye beine 0.1 ta 0.2
>>>>>>>>>>>>>>>>>>> kheili az 0.8 ta 0.9 bishtare(nemidunam az AZ physic in ghavanin yadetun
>>>>>>>>>>>>>>>>>>> hast ya na) hala ghermez ha tu shekle paper az taghtriban 1 ta 2 vahed bala
>>>>>>>>>>>>>>>>>>> taran k tu shekle man mishe 0.7 ...
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> bbakshshid majbur shodam inhame tozih bedam chon rasme
>>>>>>>>>>>>>>>>>>> nime logarithmi tu matlab yekam sakhte hala bazam daram search mizanam
>>>>>>>>>>>>>>>>>>> bbinam chi kar mitunam bokonam
>>>>>>>>>>>>>>>>>>> vali tebghe estedlal fkr mikonam shekle tolid shode ok
>>>>>>>>>>>>>>>>>>> hast
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> On Wed, Nov 16, 2016 at 1:36 AM, sepehr abdous <
>>>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> ina dg bahse rasm be sheklaye mokhtalefe
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> On Wed, Nov 16, 2016 at 1:34 AM, sepehr abdous <
>>>>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> e
>>>>>>>>>>>>>>>>>>>>> alan didam aslan in umade tu kaghaz logaritmi rasm
>>>>>>>>>>>>>>>>>>>>> karde
>>>>>>>>>>>>>>>>>>>>> yani 100 andazash 2 barabare 10 e
>>>>>>>>>>>>>>>>>>>>> mehvare y logaritm i e alan ok esh mikonam
>>>>>>>>>>>>>>>>>>>>> :D
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> On Wed, Nov 16, 2016 at 1:29 AM, HAMED Yousefi <
>>>>>>>>>>>>>>>>>>>>> doctorhy at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> affarin sepehr, dare khoob pish mire, va a in
>>>>>>>>>>>>>>>>>>>>>> babatam khoshalam ke dari tahlilam mikoni va fahmidi ke che ettefaghi
>>>>>>>>>>>>>>>>>>>>>> miofti da rhar marhale, merci.
>>>>>>>>>>>>>>>>>>>>>> man nafahmidam faghat ke chi 0-25 e, va hob to ham
>>>>>>>>>>>>>>>>>>>>>> alan bezar roo 0-1000 run she ke motmaen shim daghighan be hamoon shekl
>>>>>>>>>>>>>>>>>>>>>> miresim.
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 15, 2016 at 4:47 PM, sepehr abdous <
>>>>>>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> dalile in ham k una tuye shekle paper dense taran un
>>>>>>>>>>>>>>>>>>>>>>> bazeye y e k baraye una az 0 ta 1000 e man kardam 0 ta 25 k daghigh tar
>>>>>>>>>>>>>>>>>>>>>>> beshe did
>>>>>>>>>>>>>>>>>>>>>>> :)
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> On Wed, Nov 16, 2016 at 1:17 AM, sepehr abdous <
>>>>>>>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> salam man piade kardam
>>>>>>>>>>>>>>>>>>>>>>>> senario ine
>>>>>>>>>>>>>>>>>>>>>>>> abi: node ha hamishe hastan
>>>>>>>>>>>>>>>>>>>>>>>> ghermez: node ha hastan tuye time=60 node e 4 ro
>>>>>>>>>>>>>>>>>>>>>>>> fail mikonam tuye 60 sanie bad dare convergence mikone tuye time=120 ta 180
>>>>>>>>>>>>>>>>>>>>>>>> ping mikone vali node e 4 fail e bad time=181 ta 200 dobare node4 ro
>>>>>>>>>>>>>>>>>>>>>>>> recovery mikone va dobare ba hame node ha ping mikone k dobare zamane ping
>>>>>>>>>>>>>>>>>>>>>>>> ha betore motavasset yeki mishe
>>>>>>>>>>>>>>>>>>>>>>>> in shekli shod:
>>>>>>>>>>>>>>>>>>>>>>>> un khali e un vasat bara ghermez ha 60 sanie e
>>>>>>>>>>>>>>>>>>>>>>>> convergence e bad az fail e node4
>>>>>>>>>>>>>>>>>>>>>>>> ye check konid bbinid ok e
>>>>>>>>>>>>>>>>>>>>>>>> [image: Inline image 1]
>>>>>>>>>>>>>>>>>>>>>>>> in ham shekle paper:
>>>>>>>>>>>>>>>>>>>>>>>> [image: Inline image 2]
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 15, 2016 at 11:20 PM, HAMED Yousefi <
>>>>>>>>>>>>>>>>>>>>>>>> doctorhy at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> OK, vali hanooz in shekl va scenario to ba male
>>>>>>>>>>>>>>>>>>>>>>>>> paper fargh dare, man oono scenario ro mikham
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 15, 2016 at 2:46 PM, sepehr abdous <
>>>>>>>>>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> salam khubid?
>>>>>>>>>>>>>>>>>>>>>>>>>> bbinid man ok kardam karo
>>>>>>>>>>>>>>>>>>>>>>>>>> alan in halat noghate ghermez dar vojude node4
>>>>>>>>>>>>>>>>>>>>>>>>>> and va noghate abi dar fail e kamel e node4 yani engar node e 4 nis kollan
>>>>>>>>>>>>>>>>>>>>>>>>>> vali experiment ha ro k khundam hame kar mishe
>>>>>>>>>>>>>>>>>>>>>>>>>> kard masalan ye time i fail she dobare recover she o in harfa
>>>>>>>>>>>>>>>>>>>>>>>>>> hala in ye noshe ...
>>>>>>>>>>>>>>>>>>>>>>>>>> baste be khasteye shoma bayad experiment benevisim
>>>>>>>>>>>>>>>>>>>>>>>>>> hala alan in khorujimune
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> [image: Inline image 2]
>>>>>>>>>>>>>>>>>>>>>>>>>> :) k neshun mide zamane ping ziad mishe agar 4
>>>>>>>>>>>>>>>>>>>>>>>>>> nabashe noghate abi bala taran.
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 15, 2016 at 6:34 PM, sepehr abdous <
>>>>>>>>>>>>>>>>>>>>>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> ?????
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>> On Nov 15, 2016 6:25 PM, "HAMED Yousefi" <
>>>>>>>>>>>>>>>>>>>>>>>>>>> doctorhy at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> salam, merci, OK e, mamnoon.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 15, 2016 at 9:44 AM, sepehr abdous
>>>>>>>>>>>>>>>>>>>>>>>>>>>> <sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ????
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ??????
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ???? ?? ?????? ???? ???? ?????? ?? ????? ?????
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ?? ??? ??? ???? ?? ???????
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ???? ???? ?????? ???? ?? ?????? ???? ???? ???
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ?? ??? ????
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Result
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ????? ?? ???? ??? ??? ?? ????? ?????
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ???? ?????? ??? ?? ???? ???? ??? ??? ??? ???
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ????? ?????? ??
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tuesday, November 15, 2016, HAMED Yousefi <
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> doctorhy at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> are daghighan
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Nov 14, 2016 at 6:01 PM, sepehr
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> abdous <sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> aha alan dobare daghigh khundam un ghesmat ro
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> un nemudar 2 ta value dare
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> abi rang ha
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> va ghermez rang ha
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> k yeki baraye zamani e ke hameye node ha ok
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> an va multipath darim
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> va yeki baraye zamani e k node e 4 fail
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> mikone va faghat ye path e tanha az node e 2 be 6 mimune
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> in 2 ta ro moghayese karde yani man alan
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bayad node e 4 ro fail konam bad dobare ping bezanam va ba ham rasm konam
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> noghato
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 15, 2016 at 2:03 AM, sepehr
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> abdous <sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Y-> ms->zamane ping
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> X-> s-> zamane ejra
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bale hala bayad besh begam bad az chand
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> sanie node e 4 ro drop kone, daram rush kar mikonam...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Tue, Nov 15, 2016 at 1:59 AM, HAMED
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yousefi <doctorhy at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> affarin meske dari khoob miri jolo, alan
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> in vahede Y chie (second ya milisecond ya ...), X chie, zamane ejra?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> vahedesh chie??
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bara oon shekl ta oonja ke yadam bayad ye
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> node ya link o fail koni bad in zamanaa ro andaze begiri.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> On Mon, Nov 14, 2016 at 5:25 PM, sepehr
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> abdous <sepehrabdous1375 at gmail.com> wrote:
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> salam khubid?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bbinid man in maghale he ro khundam k
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> bbinam chi kar karde
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> fahmidam miad ping mizane az node 2 be
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> node 6 va bad in zaman ha ro rasm mikone
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> man ham hamin experiment ro ok kardam va
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ye file khoruji dad bad ghesmate zamanesh ro keshidam birun ba matlab rasm
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> kardam be shekle zir shod...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> ye nega besh bendazin...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [image: Inline image 1]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> --
>>>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>>>> School of computer engineering
>>>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> --
>>>>>>>>>>> Sepehr Abdous
>>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>>> School of computer engineering
>>>>>>>>>>> Sharif University of Technology
>>>>>>>>>>> Tehran, Iran
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Sepehr Abdous
>>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>>> Cellphone:+989194030591
>>>>>>>>>> School of computer engineering
>>>>>>>>>> Sharif University of Technology
>>>>>>>>>> Tehran, Iran
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sepehr Abdous
>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>> Cellphone:+989194030591
>>>>>>>>> School of computer engineering
>>>>>>>>> Sharif University of Technology
>>>>>>>>> Tehran, Iran
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sepehr Abdous
>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>> Cellphone:+989194030591
>>>>>>> School of computer engineering
>>>>>>> Sharif University of Technology
>>>>>>> Tehran, Iran
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sepehr Abdous
>>>>> Faculty: abdous at ce.sharif.edu
>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>> Cellphone:+989194030591
>>>>> School of computer engineering
>>>>> Sharif University of Technology
>>>>> Tehran, Iran
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 236311 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 92638 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 41888 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0017.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 42375 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 104612 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0019.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 44755 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 44309 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0021.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0022.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 45018 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/672d0ee7/attachment-0023.png>

From sepehrabdous1375 at gmail.com  Fri Nov 18 04:48:35 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Fri, 18 Nov 2016 16:18:35 +0330
Subject: [Mini-NDN] result of a topology
Message-ID: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[image: Inline image 1]
so I use minindnedit to implement it with the following information:
[image: Inline image 2]
and based on the paper which represents this topology it is expected to get
this figure from it's information:
[image: Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails,
but when I try to implement it using pingall experiment my figure will come
out like this:
[image: Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected,
any idea why it is happening?
thank you

-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/f610e949/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/f610e949/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/f610e949/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/f610e949/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/f610e949/attachment-0007.png>

From agawande at memphis.edu  Fri Nov 18 05:13:10 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 18 Nov 2016 13:13:10 +0000
Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network
In-Reply-To: <20161118102153.1goknertsgk4ws44@webmail.eurecom.fr>
References: <20161117184754.h6jvnupy0c4csc4c@webmail.eurecom.fr>
	<BN3PR04MB219676BA308033B4C236E267D9B10@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<20161118102153.1goknertsgk4ws44@webmail.eurecom.fr>
Message-ID: <SN2PR04MB220500AEED7DA22A99CB1A8AD9B00@SN2PR04MB2205.namprd04.prod.outlook.com>

Yes that means it is working.


a-eth2 is connected to root-eth0 (your machine).


You can ping 1.0.0.9 from your machine and see that it works.


Now you can run NFD on your machine and register routes to nodes running in Mini-NDN and to the outside world.


Ashlesh

________________________________
From: Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Friday, November 18, 2016 3:21:53 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Connect mini-ndn nodes to an outside network

Dear Ashlesh,
No Errors at the beginning of MiniNDN, and no errors in general.
However, doing "switch off and reboot" I've some improvements. The
root-eth0 is present just running ifconfig in the machine. Is it enough?

My output are:

1) MININDN

mininet> a ifconfig
a-eth0    Link encap:Ethernet  HWaddr 12:b7:c7:b0:99:c7
           inet addr:1.0.0.1  Bcast:1.0.0.3  Mask:255.255.255.252
           inet6 addr: fe80::10b7:c7ff:feb0:99c7/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:13 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1404 (1.4 KB)  TX bytes:1404 (1.4 KB)

a-eth1    Link encap:Ethernet  HWaddr fe:2c:28:35:26:dc
           inet addr:1.0.0.5  Bcast:1.0.0.7  Mask:255.255.255.252
           inet6 addr: fe80::fc2c:28ff:fe35:26dc/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:13 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1404 (1.4 KB)  TX bytes:1404 (1.4 KB)

a-eth2    Link encap:Ethernet  HWaddr 26:8e:b9:9a:ec:8a
           inet addr:1.0.0.10  Bcast:1.0.0.11  Mask:255.255.255.252
           inet6 addr: fe80::248e:b9ff:fe9a:ec8a/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:10 errors:0 dropped:0 overruns:0 frame:0
           TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:851 (851.0 B)  TX bytes:931 (931.0 B)

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1
           RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

------------------------------------------------------------------
------------------------------------------------------------------

2) IN THE MACHINE
ndn at ndn:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:16:35:af:94:4b
           inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
           inet6 addr: fe80::216:35ff:feaf:944b/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:25315 errors:0 dropped:0 overruns:0 frame:0
           TX packets:13892 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:9648263 (9.6 MB)  TX bytes:1989463 (1.9 MB)

eth1      Link encap:Ethernet  HWaddr 52:54:00:12:34:56
           inet addr:192.168.1.2  Bcast:192.168.1.255  Mask:255.255.255.0
           inet6 addr: fe80::5054:ff:fe12:3456/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:5365 errors:0 dropped:0 overruns:0 frame:0
           TX packets:5399 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:769454 (769.4 KB)  TX bytes:781753 (781.7 KB)

lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           inet6 addr: ::1/128 Scope:Host
           UP LOOPBACK RUNNING  MTU:65536  Metric:1
           RX packets:23 errors:0 dropped:0 overruns:0 frame:0
           TX packets:23 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1
           RX bytes:2278 (2.2 KB)  TX bytes:2278 (2.2 KB)

root-eth0 Link encap:Ethernet  HWaddr b2:6e:70:b5:4d:60
           inet addr:1.0.0.9  Bcast:1.0.0.11  Mask:255.255.255.252
           inet6 addr: fe80::b06e:70ff:feb5:4d60/64 Scope:Link
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:16 errors:0 dropped:0 overruns:0 frame:0
           TX packets:14 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:1190 (1.1 KB)  TX bytes:1138 (1.1 KB)


Bests,
Matteo


Quoting "Ashlesh Gawande (agawande)" <agawande at memphis.edu>:

> Are there any errors when Mini-NDN starts?
>
>
> What is the output of "a ifconfig" in Mini-NDN?
>
>
> And the output of ifconfig on the machine (not in Mini-NDN)?
>
>
> Ashlesh
>
> ________________________________
> From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
> Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
> Sent: Thursday, November 17, 2016 11:47:54 AM
> To: mini-ndn at lists.cs.ucla.edu
> Subject: [Mini-NDN] Connect mini-ndn nodes to an outside network
>
> Hello,
> I followed this doc:
> https://github.com/named-data/mini-ndn/blob/master/docs/CONNECT-TO-OUTSIDE.md
>
> Unfortunately, at this point:
>
> "Run Mini-NDN with the simple topology and issue ifconfig on the local
> machine to confirm the addition of the interface. You should be able
> to locate "root-eth0" "
>
> I am not able to see the node root neither root-eth0.
>
> Do you manage to run this scenario?
> Thanks,
> Matteo
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr

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

From agawande at memphis.edu  Fri Nov 18 05:23:49 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 18 Nov 2016 13:23:49 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
Message-ID: <SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.

What is your current machine configuration?

Usually for such a small topology it should not be a problem.


One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[Inline image 1]
so I use minindnedit to implement it with the following information:
[Inline image 2]
and based on the paper which represents this topology it is expected to get this figure from it's information:
[Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
[Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/138e938b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/138e938b/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/138e938b/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/138e938b/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161118/138e938b/attachment-0007.png>

From agawande at memphis.edu  Fri Nov 18 13:49:26 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 18 Nov 2016 21:49:26 +0000
Subject: [Mini-NDN] [Ndn-interest] ndn-cxx small tutorial: nacks,
 certificates with repo, signed	interest
In-Reply-To: <20161014104022.shiybktq80os44ow@webmail.eurecom.fr>
References: <20161014104022.shiybktq80os44ow@webmail.eurecom.fr>
Message-ID: <SN2PR04MB2205018BBCBDE767157BA29ED9B00@SN2PR04MB2205.namprd04.prod.outlook.com>

RTNETLINK error shows up in Ubuntu 16.04, Mininet has pushed a fix on their github since then.


For the Recommendation 4, "private key does not exist error" is a bug.

Remove "&" on this line:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L49


It will be fixed soon. Thanks, Matteo.


I will try to add a FAQ so that everybody can contribute.

https://github.com/named-data/mini-ndn/wiki


Ashlesh

________________________________
From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Friday, October 14, 2016 3:40:22 AM
To: ndn-interest at lists.cs.ucla.edu
Subject: [Ndn-interest] ndn-cxx small tutorial: nacks, certificates with repo, signed interest

Dear all,
this mail is though for who, like me, is just a beginner about NDN.
At the start of my work, I had some difficulties about "how to
perform" some basic experiments.
Then I resumed in a little pdf the main important steps in the
following topics:
1- Sending a personalized application nack
2- How to build a certificate chain, how to distribute it with
repo-ng, how to verify the data
3- How to send and verify a signed interest.

I am absolutely sure that there will be some errors in my explanation,
but I am sure also that this code and steps here listed  could help a
novice.
I encourage all to publish their personal documentation, because in my
opinion they are very useful.

Disclaimer: I found some pieces of code and some steps on the web, on
the mailing list etc. Most of the work is my own, however.

The pdf is attached. Let me know if you want to contribute to it with
new use cases. In my opinion, one about ndns is needed, like a section
that explains well the difference between ndn-cxx and ndn-cpp, between
mini and ndnsim, and so on.

If there is well done, you can put this file where you want.

You can find it also in my personal git:
https://github.com/MatteoBertolino92/NDN-matteo/blob/master/ndncxx_miniNDN_someUseCases:%20nacks%2C%20certificates%2C%20interest%20verification.pdf

Yours,
Matteo

-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr

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

From sepehrabdous1375 at gmail.com  Fri Nov 18 22:48:23 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sat, 19 Nov 2016 10:18:23 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
Message-ID: <CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>

Hello,
no there aren't any timeouts and what you see there is not a zero it is
10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations
bellow:
[image: Inline image 1]
so you're saying that this results which I've got in my figure is
reasonable for the topology and it shouldn't exactly be like the figure in
the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> Have you verified that the ping data is correctly depicted on your figure?
>
> Are there any timeouts in there? Because I see some zeros.
>
>
> RTT can be have variation in Mini-NDN because of multiple NFDs are running
> on the same machine.
>
> What is your current machine configuration?
>
> Usually for such a small topology it should not be a problem.
>
>
> One thing you can try is that if you are collecting NFD, NLSR, or any
> other logs, turn them off.
>
> That is turn off all the logs except the ping data.
>
>
> Other thing to try is to use a machine with more CPU power.
>
>
> Ashlesh
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr
> abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Friday, November 18, 2016 6:48:35 AM
> *To:* mini-ndn at lists.cs.ucla.edu
> *Subject:* [Mini-NDN] result of a topology
>
> Hello all,
> I'm new to mini-ndn and I'm trying to implement the following topology:
> [image: Inline image 1]
> so I use minindnedit to implement it with the following information:
> [image: Inline image 2]
> and based on the paper which represents this topology it is expected to
> get this figure from it's information:
> [image: Inline image 3]
> which the blue "+" represents the ping-data in the case that no node
> fails, but when I try to implement it using pingall experiment my figure
> will come out like this:
> [image: Inline image 4]
> as you can see there is more swing in the blue '+'s than it is expected,
> any idea why it is happening?
> thank you
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/dae4f7ed/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/dae4f7ed/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/dae4f7ed/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/dae4f7ed/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/dae4f7ed/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/dae4f7ed/attachment-0009.png>

From agawande at memphis.edu  Sat Nov 19 05:57:00 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Sat, 19 Nov 2016 13:57:00 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>,
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
Message-ID: <BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>

No, the figure of the paper should be possible to achieve. The CPU is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB RAM and 2 CPUs without so much variation.


To turn off the logs:

Change DEBUG to NONE here:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123


and make sure that this also set to NONE:

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34


Then reinstall Mini-NDN, sudo ./install.sh -i


Also make sure that in your topology file all the log levels are set to NONE if there is such an option after the nodes.


Then try to run the experiment again (If possible turn off the GUI in VM, i.e. login in to command line and run the experiment from there - just to free up some more CPU).


In your graph the y-axis is the RTT in ms? What are the delays you have set on the links of the topology?

(If possible, can you share the topology file?)


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Saturday, November 19, 2016 12:48:23 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] result of a topology

Hello,
no there aren't any timeouts and what you see there is not a zero it is 10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations bellow:
[Inline image 1]
so you're saying that this results which I've got in my figure is reasonable for the topology and it shouldn't exactly be like the figure in the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.

What is your current machine configuration?

Usually for such a small topology it should not be a problem.


One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[Inline image 1]
so I use minindnedit to implement it with the following information:
[Inline image 2]
and based on the paper which represents this topology it is expected to get this figure from it's information:
[Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
[Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/b5b6f473/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/b5b6f473/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/b5b6f473/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/b5b6f473/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/b5b6f473/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161119/b5b6f473/attachment-0009.png>

From sepehrabdous1375 at gmail.com  Sun Nov 20 06:04:39 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sun, 20 Nov 2016 17:34:39 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>

the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> No, the figure of the paper should be possible to achieve. The CPU is the
> bottleneck because one has to run 6 NFD, 6 NLSR instances on a single
> machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB
> RAM and 2 CPUs without so much variation.
>
>
> To turn off the logs:
>
> Change DEBUG to NONE here:
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>
>
> and make sure that this also set to NONE:
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>
>
> Then reinstall Mini-NDN, sudo ./install.sh -i
>
>
> Also make sure that in your topology file all the log levels are set to
> NONE if there is such an option after the nodes.
>
>
> Then try to run the experiment again (If possible turn off the GUI in VM,
> i.e. login in to command line and run the experiment from there - just to
> free up some more CPU).
>
>
> In your graph the y-axis is the RTT in ms? What are the delays you have
> set on the links of the topology?
>
> (If possible, can you share the topology file?)
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Saturday, November 19, 2016 12:48:23 AM
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] result of a topology
>
> Hello,
> no there aren't any timeouts and what you see there is not a zero it is
> 10^0 which is equal to 1.
> I'm running my linux on a vmware virtual machine with the configurations
> bellow:
> [image: Inline image 1]
> so you're saying that this results which I've got in my figure is
> reasonable for the topology and it shouldn't exactly be like the figure in
> the paper?
> Thank you
>
> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> Have you verified that the ping data is correctly depicted on your figure?
>>
>> Are there any timeouts in there? Because I see some zeros.
>>
>>
>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>> running on the same machine.
>>
>> What is your current machine configuration?
>>
>> Usually for such a small topology it should not be a problem.
>>
>>
>> One thing you can try is that if you are collecting NFD, NLSR, or any
>> other logs, turn them off.
>>
>> That is turn off all the logs except the ping data.
>>
>>
>> Other thing to try is to use a machine with more CPU power.
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>> sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>> *To:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* [Mini-NDN] result of a topology
>>
>> Hello all,
>> I'm new to mini-ndn and I'm trying to implement the following topology:
>> [image: Inline image 1]
>> so I use minindnedit to implement it with the following information:
>> [image: Inline image 2]
>> and based on the paper which represents this topology it is expected to
>> get this figure from it's information:
>> [image: Inline image 3]
>> which the blue "+" represents the ping-data in the case that no node
>> fails, but when I try to implement it using pingall experiment my figure
>> will come out like this:
>> [image: Inline image 4]
>> as you can see there is more swing in the blue '+'s than it is expected,
>> any idea why it is happening?
>> thank you
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/40734115/attachment-0009.png>

From sepehrabdous1375 at gmail.com  Sun Nov 20 07:54:22 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sun, 20 Nov 2016 19:24:22 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
Message-ID: <CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>

I changed the cpu of the machine and the figure became like:
[image: Inline image 1]
as you can see the swap is ok
now I've got a question about the number of pings?
how can I write the experiment to have the maximum number of pings in 200
seconds.
my current experiment is :
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 99999999
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

which the number 99999999 is to have as many pings as possible,
how can I get the maximum pings possible?


On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com>
wrote:

> the delay is zero
> the topology file is:
> [nodes]
> node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
> router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
> max-faces-per-prefix=0 nfd-log-level=NONE
> node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
> router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
> max-faces-per-prefix=0 nfd-log-level=NONE
> node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
> router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
> max-faces-per-prefix=0 nfd-log-level=NONE
> node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
> router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
> max-faces-per-prefix=0 nfd-log-level=NONE
> node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
> router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
> max-faces-per-prefix=0 nfd-log-level=NONE
> node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
> router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
> max-faces-per-prefix=0 nfd-log-level=NONE
> [switches]
> [links]
> node1:node2
> node1:node3
> node3:node5
> node5:node6
> node6:node4
> node4:node2
> node4:node3
> node3:node6
>
>
> On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> No, the figure of the paper should be possible to achieve. The CPU is the
>> bottleneck because one has to run 6 NFD, 6 NLSR instances on a single
>> machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB
>> RAM and 2 CPUs without so much variation.
>>
>>
>> To turn off the logs:
>>
>> Change DEBUG to NONE here:
>>
>> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>>
>>
>> and make sure that this also set to NONE:
>>
>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>>
>>
>> Then reinstall Mini-NDN, sudo ./install.sh -i
>>
>>
>> Also make sure that in your topology file all the log levels are set to
>> NONE if there is such an option after the nodes.
>>
>>
>> Then try to run the experiment again (If possible turn off the GUI in VM,
>> i.e. login in to command line and run the experiment from there - just to
>> free up some more CPU).
>>
>>
>> In your graph the y-axis is the RTT in ms? What are the delays you have
>> set on the links of the topology?
>>
>> (If possible, can you share the topology file?)
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Saturday, November 19, 2016 12:48:23 AM
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] result of a topology
>>
>> Hello,
>> no there aren't any timeouts and what you see there is not a zero it is
>> 10^0 which is equal to 1.
>> I'm running my linux on a vmware virtual machine with the configurations
>> bellow:
>> [image: Inline image 1]
>> so you're saying that this results which I've got in my figure is
>> reasonable for the topology and it shouldn't exactly be like the figure in
>> the paper?
>> Thank you
>>
>> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> Have you verified that the ping data is correctly depicted on your
>>> figure?
>>>
>>> Are there any timeouts in there? Because I see some zeros.
>>>
>>>
>>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>>> running on the same machine.
>>>
>>> What is your current machine configuration?
>>>
>>> Usually for such a small topology it should not be a problem.
>>>
>>>
>>> One thing you can try is that if you are collecting NFD, NLSR, or any
>>> other logs, turn them off.
>>>
>>> That is turn off all the logs except the ping data.
>>>
>>>
>>> Other thing to try is to use a machine with more CPU power.
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>> sepehr abdous <sepehrabdous1375 at gmail.com>
>>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>>> *To:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* [Mini-NDN] result of a topology
>>>
>>> Hello all,
>>> I'm new to mini-ndn and I'm trying to implement the following topology:
>>> [image: Inline image 1]
>>> so I use minindnedit to implement it with the following information:
>>> [image: Inline image 2]
>>> and based on the paper which represents this topology it is expected to
>>> get this figure from it's information:
>>> [image: Inline image 3]
>>> which the blue "+" represents the ping-data in the case that no node
>>> fails, but when I try to implement it using pingall experiment my figure
>>> will come out like this:
>>> [image: Inline image 4]
>>> as you can see there is more swing in the blue '+'s than it is expected,
>>> any idea why it is happening?
>>> thank you
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/337b63c9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/337b63c9/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/337b63c9/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/337b63c9/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/337b63c9/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/337b63c9/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161120/337b63c9/attachment-0009.png>

From agawande at memphis.edu  Mon Nov 21 12:41:22 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 21 Nov 2016 20:41:22 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>,
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
Message-ID: <BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>

Why is the delay zero, I think non-zero delay might give smoother result.


Do you want to send 99999999 pings in 200 seconds?


ndnping allows to send at most 1000 pings/second, so in 200 seconds you can send 200,000 pings at best by using the option "-i 1" here:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L92


You can modify ndnping if you want to have more pings than that.


(This will be heavy on the CPU).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Sunday, November 20, 2016 9:54:22 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] result of a topology

I changed the cpu of the machine and the figure became like:
[Inline image 1]
as you can see the swap is ok
now I've got a question about the number of pings?
how can I write the experiment to have the maximum number of pings in 200 seconds.
my current experiment is :
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 99999999
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

which the number 99999999 is to have as many pings as possible,
how can I get the maximum pings possible?


On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No, the figure of the paper should be possible to achieve. The CPU is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB RAM and 2 CPUs without so much variation.


To turn off the logs:

Change DEBUG to NONE here:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123


and make sure that this also set to NONE:

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34


Then reinstall Mini-NDN, sudo ./install.sh -i


Also make sure that in your topology file all the log levels are set to NONE if there is such an option after the nodes.


Then try to run the experiment again (If possible turn off the GUI in VM, i.e. login in to command line and run the experiment from there - just to free up some more CPU).


In your graph the y-axis is the RTT in ms? What are the delays you have set on the links of the topology?

(If possible, can you share the topology file?)


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Saturday, November 19, 2016 12:48:23 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] result of a topology

Hello,
no there aren't any timeouts and what you see there is not a zero it is 10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations bellow:
[Inline image 1]
so you're saying that this results which I've got in my figure is reasonable for the topology and it shouldn't exactly be like the figure in the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.

What is your current machine configuration?

Usually for such a small topology it should not be a problem.


One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[Inline image 1]
so I use minindnedit to implement it with the following information:
[Inline image 2]
and based on the paper which represents this topology it is expected to get this figure from it's information:
[Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
[Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/f6e70b5e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/f6e70b5e/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/f6e70b5e/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/f6e70b5e/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: photo_2016-11-20_19-21-00.jpg
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/f6e70b5e/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/f6e70b5e/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/f6e70b5e/attachment-0009.png>

From sepehrabdous1375 at gmail.com  Mon Nov 21 13:03:47 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 22 Nov 2016 00:33:47 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>

what would a reasonable delay be?

On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> Why is the delay zero, I think non-zero delay might give smoother result.
>
>
> Do you want to send 99999999 pings in 200 seconds?
>
>
> ndnping allows to send at most 1000 pings/second, so in 200 seconds you
> can send 200,000 pings at best by using the option "-i 1" here:
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/
> experiments/experiment.py#L92
>
>
> You can modify ndnping if you want to have more pings than that.
>
>
> (This will be heavy on the CPU).
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Sunday, November 20, 2016 9:54:22 AM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] result of a topology
>
> I changed the cpu of the machine and the figure became like:
> [image: Inline image 1]
> as you can see the swap is ok
> now I've got a question about the number of pings?
> how can I write the experiment to have the maximum number of pings in 200
> seconds.
> my current experiment is :
> from ndn.experiments.experiment import Experiment
> from ndn.nlsr import Nlsr
>
> import time
>
> class pingallreg(Experiment):
>
>     def __init__(self, args):
>         args["nPings"] = 99999999
>         Experiment.__init__(self, args)
>
>     def run(self):
>         self.startPctPings()
>         time.sleep(200)
>
> Experiment.register("wofail", pingallreg)
>
> which the number 99999999 is to have as many pings as possible,
> how can I get the maximum pings possible?
>
>
> On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com
> > wrote:
>
>> the delay is zero
>> the topology file is:
>> [nodes]
>> node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>> router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
>> max-faces-per-prefix=0 nfd-log-level=NONE
>> node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>> router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
>> max-faces-per-prefix=0 nfd-log-level=NONE
>> node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>> router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
>> max-faces-per-prefix=0 nfd-log-level=NONE
>> node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>> router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
>> max-faces-per-prefix=0 nfd-log-level=NONE
>> node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>> router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
>> max-faces-per-prefix=0 nfd-log-level=NONE
>> node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>> router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
>> max-faces-per-prefix=0 nfd-log-level=NONE
>> [switches]
>> [links]
>> node1:node2
>> node1:node3
>> node3:node5
>> node5:node6
>> node6:node4
>> node4:node2
>> node4:node3
>> node3:node6
>>
>>
>> On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> No, the figure of the paper should be possible to achieve. The CPU is
>>> the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single
>>> machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB
>>> RAM and 2 CPUs without so much variation.
>>>
>>>
>>> To turn off the logs:
>>>
>>> Change DEBUG to NONE here:
>>>
>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>>>
>>>
>>> and make sure that this also set to NONE:
>>>
>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>>>
>>>
>>> Then reinstall Mini-NDN, sudo ./install.sh -i
>>>
>>>
>>> Also make sure that in your topology file all the log levels are set to
>>> NONE if there is such an option after the nodes.
>>>
>>>
>>> Then try to run the experiment again (If possible turn off the GUI in
>>> VM, i.e. login in to command line and run the experiment from there - just
>>> to free up some more CPU).
>>>
>>>
>>> In your graph the y-axis is the RTT in ms? What are the delays you have
>>> set on the links of the topology?
>>>
>>> (If possible, can you share the topology file?)
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>> *Sent:* Saturday, November 19, 2016 12:48:23 AM
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>
>>> Hello,
>>> no there aren't any timeouts and what you see there is not a zero it is
>>> 10^0 which is equal to 1.
>>> I'm running my linux on a vmware virtual machine with the configurations
>>> bellow:
>>> [image: Inline image 1]
>>> so you're saying that this results which I've got in my figure is
>>> reasonable for the topology and it shouldn't exactly be like the figure in
>>> the paper?
>>> Thank you
>>>
>>> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> Have you verified that the ping data is correctly depicted on your
>>>> figure?
>>>>
>>>> Are there any timeouts in there? Because I see some zeros.
>>>>
>>>>
>>>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>>>> running on the same machine.
>>>>
>>>> What is your current machine configuration?
>>>>
>>>> Usually for such a small topology it should not be a problem.
>>>>
>>>>
>>>> One thing you can try is that if you are collecting NFD, NLSR, or any
>>>> other logs, turn them off.
>>>>
>>>> That is turn off all the logs except the ping data.
>>>>
>>>>
>>>> Other thing to try is to use a machine with more CPU power.
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>> sepehr abdous <sepehrabdous1375 at gmail.com>
>>>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* [Mini-NDN] result of a topology
>>>>
>>>> Hello all,
>>>> I'm new to mini-ndn and I'm trying to implement the following topology:
>>>> [image: Inline image 1]
>>>> so I use minindnedit to implement it with the following information:
>>>> [image: Inline image 2]
>>>> and based on the paper which represents this topology it is expected to
>>>> get this figure from it's information:
>>>> [image: Inline image 3]
>>>> which the blue "+" represents the ping-data in the case that no node
>>>> fails, but when I try to implement it using pingall experiment my figure
>>>> will come out like this:
>>>> [image: Inline image 4]
>>>> as you can see there is more swing in the blue '+'s than it is
>>>> expected, any idea why it is happening?
>>>> thank you
>>>>
>>>> --
>>>> Sepehr Abdous
>>>> Faculty: abdous at ce.sharif.edu
>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>> Cellphone:+989194030591
>>>> School of computer engineering
>>>> Sharif University of Technology
>>>> Tehran, Iran
>>>>
>>>
>>>
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/eaac0889/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/eaac0889/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/eaac0889/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/eaac0889/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/eaac0889/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/eaac0889/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/eaac0889/attachment-0009.png>

From agawande at memphis.edu  Mon Nov 21 13:10:23 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 21 Nov 2016 21:10:23 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
Message-ID: <BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>

You can try 20 or 30 ms and see if you get better results?


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Monday, November 21, 2016 3:03:47 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] result of a topology

what would a reasonable delay be?

On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Why is the delay zero, I think non-zero delay might give smoother result.


Do you want to send 99999999 pings in 200 seconds?


ndnping allows to send at most 1000 pings/second, so in 200 seconds you can send 200,000 pings at best by using the option "-i 1" here:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L92


You can modify ndnping if you want to have more pings than that.


(This will be heavy on the CPU).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Sunday, November 20, 2016 9:54:22 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] result of a topology

I changed the cpu of the machine and the figure became like:
[Inline image 1]
as you can see the swap is ok
now I've got a question about the number of pings?
how can I write the experiment to have the maximum number of pings in 200 seconds.
my current experiment is :
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 99999999
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

which the number 99999999 is to have as many pings as possible,
how can I get the maximum pings possible?


On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No, the figure of the paper should be possible to achieve. The CPU is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB RAM and 2 CPUs without so much variation.


To turn off the logs:

Change DEBUG to NONE here:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123


and make sure that this also set to NONE:

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34


Then reinstall Mini-NDN, sudo ./install.sh -i


Also make sure that in your topology file all the log levels are set to NONE if there is such an option after the nodes.


Then try to run the experiment again (If possible turn off the GUI in VM, i.e. login in to command line and run the experiment from there - just to free up some more CPU).


In your graph the y-axis is the RTT in ms? What are the delays you have set on the links of the topology?

(If possible, can you share the topology file?)


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Saturday, November 19, 2016 12:48:23 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] result of a topology

Hello,
no there aren't any timeouts and what you see there is not a zero it is 10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations bellow:
[Inline image 1]
so you're saying that this results which I've got in my figure is reasonable for the topology and it shouldn't exactly be like the figure in the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.

What is your current machine configuration?

Usually for such a small topology it should not be a problem.


One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[Inline image 1]
so I use minindnedit to implement it with the following information:
[Inline image 2]
and based on the paper which represents this topology it is expected to get this figure from it's information:
[Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
[Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/784e3b58/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/784e3b58/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: photo_2016-11-20_19-21-00.jpg
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/784e3b58/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/784e3b58/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/784e3b58/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/784e3b58/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/784e3b58/attachment-0009.png>

From sepehrabdous1375 at gmail.com  Mon Nov 21 13:36:44 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 22 Nov 2016 01:06:44 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>

ok thank you very much
I also have another question:
as you can see, the red marks in the paper's figure have a gap of about 60
seconds after that node4 fails,
how can I produce this gap or in another words cause convergence after
node's failure in my experiment, I know how to put the node off and how to
get in back on but I don't know how to cause convergence in my
experiment...?

On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> You can try 20 or 30 ms and see if you get better results?
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Monday, November 21, 2016 3:03:47 PM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] result of a topology
>
> what would a reasonable delay be?
>
> On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> Why is the delay zero, I think non-zero delay might give smoother result.
>>
>>
>> Do you want to send 99999999 pings in 200 seconds?
>>
>>
>> ndnping allows to send at most 1000 pings/second, so in 200 seconds you
>> can send 200,000 pings at best by using the option "-i 1" here:
>>
>> https://github.com/named-data/mini-ndn/blob/master/ndn/exper
>> iments/experiment.py#L92
>>
>>
>> You can modify ndnping if you want to have more pings than that.
>>
>>
>> (This will be heavy on the CPU).
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Sunday, November 20, 2016 9:54:22 AM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] result of a topology
>>
>> I changed the cpu of the machine and the figure became like:
>> [image: Inline image 1]
>> as you can see the swap is ok
>> now I've got a question about the number of pings?
>> how can I write the experiment to have the maximum number of pings in 200
>> seconds.
>> my current experiment is :
>> from ndn.experiments.experiment import Experiment
>> from ndn.nlsr import Nlsr
>>
>> import time
>>
>> class pingallreg(Experiment):
>>
>>     def __init__(self, args):
>>         args["nPings"] = 99999999
>>         Experiment.__init__(self, args)
>>
>>     def run(self):
>>         self.startPctPings()
>>         time.sleep(200)
>>
>> Experiment.register("wofail", pingallreg)
>>
>> which the number 99999999 is to have as many pings as possible,
>> how can I get the maximum pings possible?
>>
>>
>> On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <
>> sepehrabdous1375 at gmail.com> wrote:
>>
>>> the delay is zero
>>> the topology file is:
>>> [nodes]
>>> node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>> router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>> node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>> router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>> node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>> router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>> node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>> router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>> node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>> router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>> node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>> router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>> [switches]
>>> [links]
>>> node1:node2
>>> node1:node3
>>> node3:node5
>>> node5:node6
>>> node6:node4
>>> node4:node2
>>> node4:node3
>>> node3:node6
>>>
>>>
>>> On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> No, the figure of the paper should be possible to achieve. The CPU is
>>>> the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single
>>>> machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB
>>>> RAM and 2 CPUs without so much variation.
>>>>
>>>>
>>>> To turn off the logs:
>>>>
>>>> Change DEBUG to NONE here:
>>>>
>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>>>>
>>>>
>>>> and make sure that this also set to NONE:
>>>>
>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>>>>
>>>>
>>>> Then reinstall Mini-NDN, sudo ./install.sh -i
>>>>
>>>>
>>>> Also make sure that in your topology file all the log levels are set to
>>>> NONE if there is such an option after the nodes.
>>>>
>>>>
>>>> Then try to run the experiment again (If possible turn off the GUI in
>>>> VM, i.e. login in to command line and run the experiment from there - just
>>>> to free up some more CPU).
>>>>
>>>>
>>>> In your graph the y-axis is the RTT in ms? What are the delays you have
>>>> set on the links of the topology?
>>>>
>>>> (If possible, can you share the topology file?)
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>> *Sent:* Saturday, November 19, 2016 12:48:23 AM
>>>> *To:* Ashlesh Gawande (agawande)
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>
>>>> Hello,
>>>> no there aren't any timeouts and what you see there is not a zero it is
>>>> 10^0 which is equal to 1.
>>>> I'm running my linux on a vmware virtual machine with the
>>>> configurations bellow:
>>>> [image: Inline image 1]
>>>> so you're saying that this results which I've got in my figure is
>>>> reasonable for the topology and it shouldn't exactly be like the figure in
>>>> the paper?
>>>> Thank you
>>>>
>>>> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> Have you verified that the ping data is correctly depicted on your
>>>>> figure?
>>>>>
>>>>> Are there any timeouts in there? Because I see some zeros.
>>>>>
>>>>>
>>>>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>>>>> running on the same machine.
>>>>>
>>>>> What is your current machine configuration?
>>>>>
>>>>> Usually for such a small topology it should not be a problem.
>>>>>
>>>>>
>>>>> One thing you can try is that if you are collecting NFD, NLSR, or any
>>>>> other logs, turn them off.
>>>>>
>>>>> That is turn off all the logs except the ping data.
>>>>>
>>>>>
>>>>> Other thing to try is to use a machine with more CPU power.
>>>>>
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>> sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* [Mini-NDN] result of a topology
>>>>>
>>>>> Hello all,
>>>>> I'm new to mini-ndn and I'm trying to implement the following topology:
>>>>> [image: Inline image 1]
>>>>> so I use minindnedit to implement it with the following information:
>>>>> [image: Inline image 2]
>>>>> and based on the paper which represents this topology it is expected
>>>>> to get this figure from it's information:
>>>>> [image: Inline image 3]
>>>>> which the blue "+" represents the ping-data in the case that no node
>>>>> fails, but when I try to implement it using pingall experiment my figure
>>>>> will come out like this:
>>>>> [image: Inline image 4]
>>>>> as you can see there is more swing in the blue '+'s than it is
>>>>> expected, any idea why it is happening?
>>>>> thank you
>>>>>
>>>>> --
>>>>> Sepehr Abdous
>>>>> Faculty: abdous at ce.sharif.edu
>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>> Cellphone:+989194030591
>>>>> School of computer engineering
>>>>> Sharif University of Technology
>>>>> Tehran, Iran
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sepehr Abdous
>>>> Faculty: abdous at ce.sharif.edu
>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>> Cellphone:+989194030591
>>>> School of computer engineering
>>>> Sharif University of Technology
>>>> Tehran, Iran
>>>>
>>>
>>>
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/d285d7c4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/d285d7c4/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/d285d7c4/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/d285d7c4/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/d285d7c4/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/d285d7c4/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/d285d7c4/attachment-0009.png>

From agawande at memphis.edu  Mon Nov 21 13:42:51 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 21 Nov 2016 21:42:51 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
Message-ID: <BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>

So when the node is failed, NFD should automatically use the next best path installed by NLSR. Convergence is already checked before running the experiment: https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L82


If it does not, then maybe the max-faces-per-prefix is set to 3 by default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115) .You can use the option --faces 0 in Mini-NDN to use all the available paths and then it should use the next best path. This probably won't happen with this small topology.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Monday, November 21, 2016 3:36:44 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] result of a topology

ok thank you very much
I also have another question:
as you can see, the red marks in the paper's figure have a gap of about 60 seconds after that node4 fails,
how can I produce this gap or in another words cause convergence after node's failure in my experiment, I know how to put the node off and how to get in back on but I don't know how to cause convergence in my experiment...?

On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You can try 20 or 30 ms and see if you get better results?


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:03:47 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] result of a topology

what would a reasonable delay be?

On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Why is the delay zero, I think non-zero delay might give smoother result.


Do you want to send 99999999 pings in 200 seconds?


ndnping allows to send at most 1000 pings/second, so in 200 seconds you can send 200,000 pings at best by using the option "-i 1" here:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L92


You can modify ndnping if you want to have more pings than that.


(This will be heavy on the CPU).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Sunday, November 20, 2016 9:54:22 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] result of a topology

I changed the cpu of the machine and the figure became like:
[Inline image 1]
as you can see the swap is ok
now I've got a question about the number of pings?
how can I write the experiment to have the maximum number of pings in 200 seconds.
my current experiment is :
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 99999999
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

which the number 99999999 is to have as many pings as possible,
how can I get the maximum pings possible?


On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No, the figure of the paper should be possible to achieve. The CPU is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB RAM and 2 CPUs without so much variation.


To turn off the logs:

Change DEBUG to NONE here:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123


and make sure that this also set to NONE:

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34


Then reinstall Mini-NDN, sudo ./install.sh -i


Also make sure that in your topology file all the log levels are set to NONE if there is such an option after the nodes.


Then try to run the experiment again (If possible turn off the GUI in VM, i.e. login in to command line and run the experiment from there - just to free up some more CPU).


In your graph the y-axis is the RTT in ms? What are the delays you have set on the links of the topology?

(If possible, can you share the topology file?)


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Saturday, November 19, 2016 12:48:23 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] result of a topology

Hello,
no there aren't any timeouts and what you see there is not a zero it is 10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations bellow:
[Inline image 1]
so you're saying that this results which I've got in my figure is reasonable for the topology and it shouldn't exactly be like the figure in the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.

What is your current machine configuration?

Usually for such a small topology it should not be a problem.


One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[Inline image 1]
so I use minindnedit to implement it with the following information:
[Inline image 2]
and based on the paper which represents this topology it is expected to get this figure from it's information:
[Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
[Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/5d29d5be/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/5d29d5be/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: photo_2016-11-20_19-21-00.jpg
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/5d29d5be/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/5d29d5be/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/5d29d5be/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/5d29d5be/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/5d29d5be/attachment-0009.png>

From sepehrabdous1375 at gmail.com  Mon Nov 21 13:46:05 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 22 Nov 2016 01:16:05 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
	<BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>

then how can that gap be explained?
I mean then why that convergence gap is considered in the paper's figure?

On Tue, Nov 22, 2016 at 1:12 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> So when the node is failed, NFD should automatically use the next best
> path installed by NLSR. Convergence is already checked before running the
> experiment: https://github.com/named-data/mini-ndn/blob/
> master/ndn/experiments/experiment.py#L82
>
>
> If it does not, then maybe the max-faces-per-prefix is set to 3 by
> default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115) .You
> can use the option --faces 0 in Mini-NDN to use all the available paths and
> then it should use the next best path. This probably won't happen with this
> small topology.
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Monday, November 21, 2016 3:36:44 PM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] result of a topology
>
> ok thank you very much
> I also have another question:
> as you can see, the red marks in the paper's figure have a gap of about 60
> seconds after that node4 fails,
> how can I produce this gap or in another words cause convergence after
> node's failure in my experiment, I know how to put the node off and how to
> get in back on but I don't know how to cause convergence in my
> experiment...?
>
> On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> You can try 20 or 30 ms and see if you get better results?
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Monday, November 21, 2016 3:03:47 PM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] result of a topology
>>
>> what would a reasonable delay be?
>>
>> On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> Why is the delay zero, I think non-zero delay might give smoother result.
>>>
>>>
>>> Do you want to send 99999999 pings in 200 seconds?
>>>
>>>
>>> ndnping allows to send at most 1000 pings/second, so in 200 seconds you
>>> can send 200,000 pings at best by using the option "-i 1" here:
>>>
>>> https://github.com/named-data/mini-ndn/blob/master/ndn/exper
>>> iments/experiment.py#L92
>>>
>>>
>>> You can modify ndnping if you want to have more pings than that.
>>>
>>>
>>> (This will be heavy on the CPU).
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>> *Sent:* Sunday, November 20, 2016 9:54:22 AM
>>>
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>
>>> I changed the cpu of the machine and the figure became like:
>>> [image: Inline image 1]
>>> as you can see the swap is ok
>>> now I've got a question about the number of pings?
>>> how can I write the experiment to have the maximum number of pings in
>>> 200 seconds.
>>> my current experiment is :
>>> from ndn.experiments.experiment import Experiment
>>> from ndn.nlsr import Nlsr
>>>
>>> import time
>>>
>>> class pingallreg(Experiment):
>>>
>>>     def __init__(self, args):
>>>         args["nPings"] = 99999999
>>>         Experiment.__init__(self, args)
>>>
>>>     def run(self):
>>>         self.startPctPings()
>>>         time.sleep(200)
>>>
>>> Experiment.register("wofail", pingallreg)
>>>
>>> which the number 99999999 is to have as many pings as possible,
>>> how can I get the maximum pings possible?
>>>
>>>
>>> On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <
>>> sepehrabdous1375 at gmail.com> wrote:
>>>
>>>> the delay is zero
>>>> the topology file is:
>>>> [nodes]
>>>> node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>> router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>> node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>> router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>> node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>> router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>> node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>> router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>> node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>> router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>> node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>> router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>> [switches]
>>>> [links]
>>>> node1:node2
>>>> node1:node3
>>>> node3:node5
>>>> node5:node6
>>>> node6:node4
>>>> node4:node2
>>>> node4:node3
>>>> node3:node6
>>>>
>>>>
>>>> On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> No, the figure of the paper should be possible to achieve. The CPU is
>>>>> the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single
>>>>> machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB
>>>>> RAM and 2 CPUs without so much variation.
>>>>>
>>>>>
>>>>> To turn off the logs:
>>>>>
>>>>> Change DEBUG to NONE here:
>>>>>
>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>>>>>
>>>>>
>>>>> and make sure that this also set to NONE:
>>>>>
>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>>>>>
>>>>>
>>>>> Then reinstall Mini-NDN, sudo ./install.sh -i
>>>>>
>>>>>
>>>>> Also make sure that in your topology file all the log levels are set
>>>>> to NONE if there is such an option after the nodes.
>>>>>
>>>>>
>>>>> Then try to run the experiment again (If possible turn off the GUI in
>>>>> VM, i.e. login in to command line and run the experiment from there - just
>>>>> to free up some more CPU).
>>>>>
>>>>>
>>>>> In your graph the y-axis is the RTT in ms? What are the delays you
>>>>> have set on the links of the topology?
>>>>>
>>>>> (If possible, can you share the topology file?)
>>>>>
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>> *Sent:* Saturday, November 19, 2016 12:48:23 AM
>>>>> *To:* Ashlesh Gawande (agawande)
>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>>
>>>>> Hello,
>>>>> no there aren't any timeouts and what you see there is not a zero it
>>>>> is 10^0 which is equal to 1.
>>>>> I'm running my linux on a vmware virtual machine with the
>>>>> configurations bellow:
>>>>> [image: Inline image 1]
>>>>> so you're saying that this results which I've got in my figure is
>>>>> reasonable for the topology and it shouldn't exactly be like the figure in
>>>>> the paper?
>>>>> Thank you
>>>>>
>>>>> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
>>>>> agawande at memphis.edu> wrote:
>>>>>
>>>>>> Have you verified that the ping data is correctly depicted on your
>>>>>> figure?
>>>>>>
>>>>>> Are there any timeouts in there? Because I see some zeros.
>>>>>>
>>>>>>
>>>>>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>>>>>> running on the same machine.
>>>>>>
>>>>>> What is your current machine configuration?
>>>>>>
>>>>>> Usually for such a small topology it should not be a problem.
>>>>>>
>>>>>>
>>>>>> One thing you can try is that if you are collecting NFD, NLSR, or any
>>>>>> other logs, turn them off.
>>>>>>
>>>>>> That is turn off all the logs except the ping data.
>>>>>>
>>>>>>
>>>>>> Other thing to try is to use a machine with more CPU power.
>>>>>>
>>>>>>
>>>>>> Ashlesh
>>>>>> ------------------------------
>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>>> sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>>> *Subject:* [Mini-NDN] result of a topology
>>>>>>
>>>>>> Hello all,
>>>>>> I'm new to mini-ndn and I'm trying to implement the following
>>>>>> topology:
>>>>>> [image: Inline image 1]
>>>>>> so I use minindnedit to implement it with the following information:
>>>>>> [image: Inline image 2]
>>>>>> and based on the paper which represents this topology it is expected
>>>>>> to get this figure from it's information:
>>>>>> [image: Inline image 3]
>>>>>> which the blue "+" represents the ping-data in the case that no node
>>>>>> fails, but when I try to implement it using pingall experiment my figure
>>>>>> will come out like this:
>>>>>> [image: Inline image 4]
>>>>>> as you can see there is more swing in the blue '+'s than it is
>>>>>> expected, any idea why it is happening?
>>>>>> thank you
>>>>>>
>>>>>> --
>>>>>> Sepehr Abdous
>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>> Cellphone:+989194030591
>>>>>> School of computer engineering
>>>>>> Sharif University of Technology
>>>>>> Tehran, Iran
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sepehr Abdous
>>>>> Faculty: abdous at ce.sharif.edu
>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>> Cellphone:+989194030591
>>>>> School of computer engineering
>>>>> Sharif University of Technology
>>>>> Tehran, Iran
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sepehr Abdous
>>>> Faculty: abdous at ce.sharif.edu
>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>> Cellphone:+989194030591
>>>> School of computer engineering
>>>> Sharif University of Technology
>>>> Tehran, Iran
>>>>
>>>
>>>
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/ebd4da6b/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/ebd4da6b/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/ebd4da6b/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/ebd4da6b/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/ebd4da6b/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/ebd4da6b/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/ebd4da6b/attachment-0009.png>

From agawande at memphis.edu  Mon Nov 21 13:48:04 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 21 Nov 2016 21:48:04 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
	<BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>
Message-ID: <BN3PR04MB2196358A45A5793060774C56D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>

Oh I see, convergence for the best path will happen automatically once the node recovers (i.e. once NLSR comes back up on the failed node).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Monday, November 21, 2016 3:46:05 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] result of a topology

then how can that gap be explained?
I mean then why that convergence gap is considered in the paper's figure?

On Tue, Nov 22, 2016 at 1:12 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

So when the node is failed, NFD should automatically use the next best path installed by NLSR. Convergence is already checked before running the experiment: https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L82


If it does not, then maybe the max-faces-per-prefix is set to 3 by default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115) .You can use the option --faces 0 in Mini-NDN to use all the available paths and then it should use the next best path. This probably won't happen with this small topology.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:36:44 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] result of a topology

ok thank you very much
I also have another question:
as you can see, the red marks in the paper's figure have a gap of about 60 seconds after that node4 fails,
how can I produce this gap or in another words cause convergence after node's failure in my experiment, I know how to put the node off and how to get in back on but I don't know how to cause convergence in my experiment...?

On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You can try 20 or 30 ms and see if you get better results?


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:03:47 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] result of a topology

what would a reasonable delay be?

On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Why is the delay zero, I think non-zero delay might give smoother result.


Do you want to send 99999999 pings in 200 seconds?


ndnping allows to send at most 1000 pings/second, so in 200 seconds you can send 200,000 pings at best by using the option "-i 1" here:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L92


You can modify ndnping if you want to have more pings than that.


(This will be heavy on the CPU).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Sunday, November 20, 2016 9:54:22 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] result of a topology

I changed the cpu of the machine and the figure became like:
[Inline image 1]
as you can see the swap is ok
now I've got a question about the number of pings?
how can I write the experiment to have the maximum number of pings in 200 seconds.
my current experiment is :
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 99999999
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

which the number 99999999 is to have as many pings as possible,
how can I get the maximum pings possible?


On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No, the figure of the paper should be possible to achieve. The CPU is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB RAM and 2 CPUs without so much variation.


To turn off the logs:

Change DEBUG to NONE here:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123


and make sure that this also set to NONE:

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34


Then reinstall Mini-NDN, sudo ./install.sh -i


Also make sure that in your topology file all the log levels are set to NONE if there is such an option after the nodes.


Then try to run the experiment again (If possible turn off the GUI in VM, i.e. login in to command line and run the experiment from there - just to free up some more CPU).


In your graph the y-axis is the RTT in ms? What are the delays you have set on the links of the topology?

(If possible, can you share the topology file?)


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Saturday, November 19, 2016 12:48:23 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] result of a topology

Hello,
no there aren't any timeouts and what you see there is not a zero it is 10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations bellow:
[Inline image 1]
so you're saying that this results which I've got in my figure is reasonable for the topology and it shouldn't exactly be like the figure in the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.

What is your current machine configuration?

Usually for such a small topology it should not be a problem.


One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[Inline image 1]
so I use minindnedit to implement it with the following information:
[Inline image 2]
and based on the paper which represents this topology it is expected to get this figure from it's information:
[Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
[Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/9aef2fce/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/9aef2fce/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: photo_2016-11-20_19-21-00.jpg
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/9aef2fce/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/9aef2fce/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/9aef2fce/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/9aef2fce/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/9aef2fce/attachment-0009.png>

From sepehrabdous1375 at gmail.com  Mon Nov 21 13:57:39 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 22 Nov 2016 01:27:39 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <BN3PR04MB2196358A45A5793060774C56D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
	<BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>
	<BN3PR04MB2196358A45A5793060774C56D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrijQe2_Qw4OYE9GAoXUM-aL4HRFdN791BzFvN7-UZTaRWw@mail.gmail.com>

so you mean that it will automatically happen and I shouldn't consider
anything for it in my experiment?

On Tue, Nov 22, 2016 at 1:18 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> Oh I see, convergence for the best path will happen automatically once the
> node recovers (i.e. once NLSR comes back up on the failed node).
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Monday, November 21, 2016 3:46:05 PM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] result of a topology
>
> then how can that gap be explained?
> I mean then why that convergence gap is considered in the paper's figure?
>
> On Tue, Nov 22, 2016 at 1:12 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> So when the node is failed, NFD should automatically use the next best
>> path installed by NLSR. Convergence is already checked before running the
>> experiment: https://github.com/named-data/mini-ndn/blob/mast
>> er/ndn/experiments/experiment.py#L82
>>
>>
>> If it does not, then maybe the max-faces-per-prefix is set to 3 by
>> default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115) .You
>> can use the option --faces 0 in Mini-NDN to use all the available paths and
>> then it should use the next best path. This probably won't happen with this
>> small topology.
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Monday, November 21, 2016 3:36:44 PM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] result of a topology
>>
>> ok thank you very much
>> I also have another question:
>> as you can see, the red marks in the paper's figure have a gap of about
>> 60 seconds after that node4 fails,
>> how can I produce this gap or in another words cause convergence after
>> node's failure in my experiment, I know how to put the node off and how to
>> get in back on but I don't know how to cause convergence in my
>> experiment...?
>>
>> On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> You can try 20 or 30 ms and see if you get better results?
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>> *Sent:* Monday, November 21, 2016 3:03:47 PM
>>>
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>
>>> what would a reasonable delay be?
>>>
>>> On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> Why is the delay zero, I think non-zero delay might give smoother
>>>> result.
>>>>
>>>>
>>>> Do you want to send 99999999 pings in 200 seconds?
>>>>
>>>>
>>>> ndnping allows to send at most 1000 pings/second, so in 200 seconds you
>>>> can send 200,000 pings at best by using the option "-i 1" here:
>>>>
>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/exper
>>>> iments/experiment.py#L92
>>>>
>>>>
>>>> You can modify ndnping if you want to have more pings than that.
>>>>
>>>>
>>>> (This will be heavy on the CPU).
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>> *Sent:* Sunday, November 20, 2016 9:54:22 AM
>>>>
>>>> *To:* Ashlesh Gawande (agawande)
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>
>>>> I changed the cpu of the machine and the figure became like:
>>>> [image: Inline image 1]
>>>> as you can see the swap is ok
>>>> now I've got a question about the number of pings?
>>>> how can I write the experiment to have the maximum number of pings in
>>>> 200 seconds.
>>>> my current experiment is :
>>>> from ndn.experiments.experiment import Experiment
>>>> from ndn.nlsr import Nlsr
>>>>
>>>> import time
>>>>
>>>> class pingallreg(Experiment):
>>>>
>>>>     def __init__(self, args):
>>>>         args["nPings"] = 99999999
>>>>         Experiment.__init__(self, args)
>>>>
>>>>     def run(self):
>>>>         self.startPctPings()
>>>>         time.sleep(200)
>>>>
>>>> Experiment.register("wofail", pingallreg)
>>>>
>>>> which the number 99999999 is to have as many pings as possible,
>>>> how can I get the maximum pings possible?
>>>>
>>>>
>>>> On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <
>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>
>>>>> the delay is zero
>>>>> the topology file is:
>>>>> [nodes]
>>>>> node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>> router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>> node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>> router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>> node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>> router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>> node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>> router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>> node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>> router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>> node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>> router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>> [switches]
>>>>> [links]
>>>>> node1:node2
>>>>> node1:node3
>>>>> node3:node5
>>>>> node5:node6
>>>>> node6:node4
>>>>> node4:node2
>>>>> node4:node3
>>>>> node3:node6
>>>>>
>>>>>
>>>>> On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
>>>>> agawande at memphis.edu> wrote:
>>>>>
>>>>>> No, the figure of the paper should be possible to achieve. The CPU is
>>>>>> the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single
>>>>>> machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB
>>>>>> RAM and 2 CPUs without so much variation.
>>>>>>
>>>>>>
>>>>>> To turn off the logs:
>>>>>>
>>>>>> Change DEBUG to NONE here:
>>>>>>
>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>>>>>>
>>>>>>
>>>>>> and make sure that this also set to NONE:
>>>>>>
>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>>>>>>
>>>>>>
>>>>>> Then reinstall Mini-NDN, sudo ./install.sh -i
>>>>>>
>>>>>>
>>>>>> Also make sure that in your topology file all the log levels are set
>>>>>> to NONE if there is such an option after the nodes.
>>>>>>
>>>>>>
>>>>>> Then try to run the experiment again (If possible turn off the GUI in
>>>>>> VM, i.e. login in to command line and run the experiment from there - just
>>>>>> to free up some more CPU).
>>>>>>
>>>>>>
>>>>>> In your graph the y-axis is the RTT in ms? What are the delays you
>>>>>> have set on the links of the topology?
>>>>>>
>>>>>> (If possible, can you share the topology file?)
>>>>>>
>>>>>>
>>>>>> Ashlesh
>>>>>> ------------------------------
>>>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>> *Sent:* Saturday, November 19, 2016 12:48:23 AM
>>>>>> *To:* Ashlesh Gawande (agawande)
>>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>>>
>>>>>> Hello,
>>>>>> no there aren't any timeouts and what you see there is not a zero it
>>>>>> is 10^0 which is equal to 1.
>>>>>> I'm running my linux on a vmware virtual machine with the
>>>>>> configurations bellow:
>>>>>> [image: Inline image 1]
>>>>>> so you're saying that this results which I've got in my figure is
>>>>>> reasonable for the topology and it shouldn't exactly be like the figure in
>>>>>> the paper?
>>>>>> Thank you
>>>>>>
>>>>>> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
>>>>>> agawande at memphis.edu> wrote:
>>>>>>
>>>>>>> Have you verified that the ping data is correctly depicted on your
>>>>>>> figure?
>>>>>>>
>>>>>>> Are there any timeouts in there? Because I see some zeros.
>>>>>>>
>>>>>>>
>>>>>>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>>>>>>> running on the same machine.
>>>>>>>
>>>>>>> What is your current machine configuration?
>>>>>>>
>>>>>>> Usually for such a small topology it should not be a problem.
>>>>>>>
>>>>>>>
>>>>>>> One thing you can try is that if you are collecting NFD, NLSR, or
>>>>>>> any other logs, turn them off.
>>>>>>>
>>>>>>> That is turn off all the logs except the ping data.
>>>>>>>
>>>>>>>
>>>>>>> Other thing to try is to use a machine with more CPU power.
>>>>>>>
>>>>>>>
>>>>>>> Ashlesh
>>>>>>> ------------------------------
>>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>>>> sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>>>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>>>> *Subject:* [Mini-NDN] result of a topology
>>>>>>>
>>>>>>> Hello all,
>>>>>>> I'm new to mini-ndn and I'm trying to implement the following
>>>>>>> topology:
>>>>>>> [image: Inline image 1]
>>>>>>> so I use minindnedit to implement it with the following information:
>>>>>>> [image: Inline image 2]
>>>>>>> and based on the paper which represents this topology it is expected
>>>>>>> to get this figure from it's information:
>>>>>>> [image: Inline image 3]
>>>>>>> which the blue "+" represents the ping-data in the case that no node
>>>>>>> fails, but when I try to implement it using pingall experiment my figure
>>>>>>> will come out like this:
>>>>>>> [image: Inline image 4]
>>>>>>> as you can see there is more swing in the blue '+'s than it is
>>>>>>> expected, any idea why it is happening?
>>>>>>> thank you
>>>>>>>
>>>>>>> --
>>>>>>> Sepehr Abdous
>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>> Cellphone:+989194030591
>>>>>>> School of computer engineering
>>>>>>> Sharif University of Technology
>>>>>>> Tehran, Iran
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sepehr Abdous
>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>> Cellphone:+989194030591
>>>>>> School of computer engineering
>>>>>> Sharif University of Technology
>>>>>> Tehran, Iran
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sepehr Abdous
>>>>> Faculty: abdous at ce.sharif.edu
>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>> Cellphone:+989194030591
>>>>> School of computer engineering
>>>>> Sharif University of Technology
>>>>> Tehran, Iran
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sepehr Abdous
>>>> Faculty: abdous at ce.sharif.edu
>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>> Cellphone:+989194030591
>>>> School of computer engineering
>>>> Sharif University of Technology
>>>> Tehran, Iran
>>>>
>>>
>>>
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/83f19b40/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/83f19b40/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/83f19b40/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/83f19b40/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/83f19b40/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/83f19b40/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/83f19b40/attachment-0009.png>

From agawande at memphis.edu  Mon Nov 21 13:59:31 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 21 Nov 2016 21:59:31 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOrijQe2_Qw4OYE9GAoXUM-aL4HRFdN791BzFvN7-UZTaRWw@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
	<BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>
	<BN3PR04MB2196358A45A5793060774C56D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOrijQe2_Qw4OYE9GAoXUM-aL4HRFdN791BzFvN7-UZTaRWw@mail.gmail.com>
Message-ID: <BN3PR04MB219693FE0EA16A57D6A1B306D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>

Yes it will happen automatically. I think in the paper the node was down for 2 minutes then brought up.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Monday, November 21, 2016 3:57:39 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] result of a topology

so you mean that it will automatically happen and I shouldn't consider anything for it in my experiment?

On Tue, Nov 22, 2016 at 1:18 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Oh I see, convergence for the best path will happen automatically once the node recovers (i.e. once NLSR comes back up on the failed node).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:46:05 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] result of a topology

then how can that gap be explained?
I mean then why that convergence gap is considered in the paper's figure?

On Tue, Nov 22, 2016 at 1:12 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

So when the node is failed, NFD should automatically use the next best path installed by NLSR. Convergence is already checked before running the experiment: https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L82


If it does not, then maybe the max-faces-per-prefix is set to 3 by default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115) .You can use the option --faces 0 in Mini-NDN to use all the available paths and then it should use the next best path. This probably won't happen with this small topology.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:36:44 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] result of a topology

ok thank you very much
I also have another question:
as you can see, the red marks in the paper's figure have a gap of about 60 seconds after that node4 fails,
how can I produce this gap or in another words cause convergence after node's failure in my experiment, I know how to put the node off and how to get in back on but I don't know how to cause convergence in my experiment...?

On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You can try 20 or 30 ms and see if you get better results?


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:03:47 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] result of a topology

what would a reasonable delay be?

On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Why is the delay zero, I think non-zero delay might give smoother result.


Do you want to send 99999999 pings in 200 seconds?


ndnping allows to send at most 1000 pings/second, so in 200 seconds you can send 200,000 pings at best by using the option "-i 1" here:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L92


You can modify ndnping if you want to have more pings than that.


(This will be heavy on the CPU).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Sunday, November 20, 2016 9:54:22 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] result of a topology

I changed the cpu of the machine and the figure became like:
[Inline image 1]
as you can see the swap is ok
now I've got a question about the number of pings?
how can I write the experiment to have the maximum number of pings in 200 seconds.
my current experiment is :
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 99999999
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

which the number 99999999 is to have as many pings as possible,
how can I get the maximum pings possible?


On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No, the figure of the paper should be possible to achieve. The CPU is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB RAM and 2 CPUs without so much variation.


To turn off the logs:

Change DEBUG to NONE here:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123


and make sure that this also set to NONE:

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34


Then reinstall Mini-NDN, sudo ./install.sh -i


Also make sure that in your topology file all the log levels are set to NONE if there is such an option after the nodes.


Then try to run the experiment again (If possible turn off the GUI in VM, i.e. login in to command line and run the experiment from there - just to free up some more CPU).


In your graph the y-axis is the RTT in ms? What are the delays you have set on the links of the topology?

(If possible, can you share the topology file?)


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Saturday, November 19, 2016 12:48:23 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] result of a topology

Hello,
no there aren't any timeouts and what you see there is not a zero it is 10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations bellow:
[Inline image 1]
so you're saying that this results which I've got in my figure is reasonable for the topology and it shouldn't exactly be like the figure in the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.

What is your current machine configuration?

Usually for such a small topology it should not be a problem.


One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
[Inline image 1]
so I use minindnedit to implement it with the following information:
[Inline image 2]
and based on the paper which represents this topology it is expected to get this figure from it's information:
[Inline image 3]
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
[Inline image 4]
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/8753cb19/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/8753cb19/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/8753cb19/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: photo_2016-11-20_19-21-00.jpg
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/8753cb19/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/8753cb19/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: image.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/8753cb19/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161121/8753cb19/attachment-0009.png>

From sepehrabdous1375 at gmail.com  Mon Nov 21 14:01:01 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 22 Nov 2016 01:31:01 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <BN3PR04MB219693FE0EA16A57D6A1B306D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
	<BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>
	<BN3PR04MB2196358A45A5793060774C56D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijQe2_Qw4OYE9GAoXUM-aL4HRFdN791BzFvN7-UZTaRWw@mail.gmail.com>
	<BN3PR04MB219693FE0EA16A57D6A1B306D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrig-TDR4T55G6tb+HPXjTX97KiO5avRVBaz4sWCu8QPgCg@mail.gmail.com>

thank you very much

On Tue, Nov 22, 2016 at 1:29 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> Yes it will happen automatically. I think in the paper the node was down
> for 2 minutes then brought up.
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Monday, November 21, 2016 3:57:39 PM
>
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] result of a topology
>
> so you mean that it will automatically happen and I shouldn't consider
> anything for it in my experiment?
>
> On Tue, Nov 22, 2016 at 1:18 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> Oh I see, convergence for the best path will happen automatically once
>> the node recovers (i.e. once NLSR comes back up on the failed node).
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Monday, November 21, 2016 3:46:05 PM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] result of a topology
>>
>> then how can that gap be explained?
>> I mean then why that convergence gap is considered in the paper's figure?
>>
>> On Tue, Nov 22, 2016 at 1:12 AM, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> So when the node is failed, NFD should automatically use the next best
>>> path installed by NLSR. Convergence is already checked before running the
>>> experiment: https://github.com/named-data/mini-ndn/blob/mast
>>> er/ndn/experiments/experiment.py#L82
>>>
>>>
>>> If it does not, then maybe the max-faces-per-prefix is set to 3 by
>>> default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115)
>>> .You can use the option --faces 0 in Mini-NDN to use all the available
>>> paths and then it should use the next best path. This probably won't happen
>>> with this small topology.
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>> *Sent:* Monday, November 21, 2016 3:36:44 PM
>>>
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>
>>> ok thank you very much
>>> I also have another question:
>>> as you can see, the red marks in the paper's figure have a gap of about
>>> 60 seconds after that node4 fails,
>>> how can I produce this gap or in another words cause convergence after
>>> node's failure in my experiment, I know how to put the node off and how to
>>> get in back on but I don't know how to cause convergence in my
>>> experiment...?
>>>
>>> On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> You can try 20 or 30 ms and see if you get better results?
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>> *Sent:* Monday, November 21, 2016 3:03:47 PM
>>>>
>>>> *To:* Ashlesh Gawande (agawande)
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>
>>>> what would a reasonable delay be?
>>>>
>>>> On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> Why is the delay zero, I think non-zero delay might give smoother
>>>>> result.
>>>>>
>>>>>
>>>>> Do you want to send 99999999 pings in 200 seconds?
>>>>>
>>>>>
>>>>> ndnping allows to send at most 1000 pings/second, so in 200 seconds
>>>>> you can send 200,000 pings at best by using the option "-i 1" here:
>>>>>
>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/exper
>>>>> iments/experiment.py#L92
>>>>>
>>>>>
>>>>> You can modify ndnping if you want to have more pings than that.
>>>>>
>>>>>
>>>>> (This will be heavy on the CPU).
>>>>>
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>> *Sent:* Sunday, November 20, 2016 9:54:22 AM
>>>>>
>>>>> *To:* Ashlesh Gawande (agawande)
>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>>
>>>>> I changed the cpu of the machine and the figure became like:
>>>>> [image: Inline image 1]
>>>>> as you can see the swap is ok
>>>>> now I've got a question about the number of pings?
>>>>> how can I write the experiment to have the maximum number of pings in
>>>>> 200 seconds.
>>>>> my current experiment is :
>>>>> from ndn.experiments.experiment import Experiment
>>>>> from ndn.nlsr import Nlsr
>>>>>
>>>>> import time
>>>>>
>>>>> class pingallreg(Experiment):
>>>>>
>>>>>     def __init__(self, args):
>>>>>         args["nPings"] = 99999999
>>>>>         Experiment.__init__(self, args)
>>>>>
>>>>>     def run(self):
>>>>>         self.startPctPings()
>>>>>         time.sleep(200)
>>>>>
>>>>> Experiment.register("wofail", pingallreg)
>>>>>
>>>>> which the number 99999999 is to have as many pings as possible,
>>>>> how can I get the maximum pings possible?
>>>>>
>>>>>
>>>>> On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <
>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>
>>>>>> the delay is zero
>>>>>> the topology file is:
>>>>>> [nodes]
>>>>>> node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>> router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>> node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>> router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>> node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>> router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>> node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>> router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>> node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>> router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>> node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>> router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>> [switches]
>>>>>> [links]
>>>>>> node1:node2
>>>>>> node1:node3
>>>>>> node3:node5
>>>>>> node5:node6
>>>>>> node6:node4
>>>>>> node4:node2
>>>>>> node4:node3
>>>>>> node3:node6
>>>>>>
>>>>>>
>>>>>> On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
>>>>>> agawande at memphis.edu> wrote:
>>>>>>
>>>>>>> No, the figure of the paper should be possible to achieve. The CPU
>>>>>>> is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a
>>>>>>> single machine. I have run a 10 node pingall experiment on a VBox VM with
>>>>>>> 2.5GB RAM and 2 CPUs without so much variation.
>>>>>>>
>>>>>>>
>>>>>>> To turn off the logs:
>>>>>>>
>>>>>>> Change DEBUG to NONE here:
>>>>>>>
>>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>>>>>>>
>>>>>>>
>>>>>>> and make sure that this also set to NONE:
>>>>>>>
>>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>>>>>>>
>>>>>>>
>>>>>>> Then reinstall Mini-NDN, sudo ./install.sh -i
>>>>>>>
>>>>>>>
>>>>>>> Also make sure that in your topology file all the log levels are set
>>>>>>> to NONE if there is such an option after the nodes.
>>>>>>>
>>>>>>>
>>>>>>> Then try to run the experiment again (If possible turn off the GUI
>>>>>>> in VM, i.e. login in to command line and run the experiment from there -
>>>>>>> just to free up some more CPU).
>>>>>>>
>>>>>>>
>>>>>>> In your graph the y-axis is the RTT in ms? What are the delays you
>>>>>>> have set on the links of the topology?
>>>>>>>
>>>>>>> (If possible, can you share the topology file?)
>>>>>>>
>>>>>>>
>>>>>>> Ashlesh
>>>>>>> ------------------------------
>>>>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>>> *Sent:* Saturday, November 19, 2016 12:48:23 AM
>>>>>>> *To:* Ashlesh Gawande (agawande)
>>>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>>>>
>>>>>>> Hello,
>>>>>>> no there aren't any timeouts and what you see there is not a zero it
>>>>>>> is 10^0 which is equal to 1.
>>>>>>> I'm running my linux on a vmware virtual machine with the
>>>>>>> configurations bellow:
>>>>>>> [image: Inline image 1]
>>>>>>> so you're saying that this results which I've got in my figure is
>>>>>>> reasonable for the topology and it shouldn't exactly be like the figure in
>>>>>>> the paper?
>>>>>>> Thank you
>>>>>>>
>>>>>>> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
>>>>>>> agawande at memphis.edu> wrote:
>>>>>>>
>>>>>>>> Have you verified that the ping data is correctly depicted on your
>>>>>>>> figure?
>>>>>>>>
>>>>>>>> Are there any timeouts in there? Because I see some zeros.
>>>>>>>>
>>>>>>>>
>>>>>>>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>>>>>>>> running on the same machine.
>>>>>>>>
>>>>>>>> What is your current machine configuration?
>>>>>>>>
>>>>>>>> Usually for such a small topology it should not be a problem.
>>>>>>>>
>>>>>>>>
>>>>>>>> One thing you can try is that if you are collecting NFD, NLSR, or
>>>>>>>> any other logs, turn them off.
>>>>>>>>
>>>>>>>> That is turn off all the logs except the ping data.
>>>>>>>>
>>>>>>>>
>>>>>>>> Other thing to try is to use a machine with more CPU power.
>>>>>>>>
>>>>>>>>
>>>>>>>> Ashlesh
>>>>>>>> ------------------------------
>>>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>>>>>>>> sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>>>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>>>>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>>>>> *Subject:* [Mini-NDN] result of a topology
>>>>>>>>
>>>>>>>> Hello all,
>>>>>>>> I'm new to mini-ndn and I'm trying to implement the following
>>>>>>>> topology:
>>>>>>>> [image: Inline image 1]
>>>>>>>> so I use minindnedit to implement it with the following information:
>>>>>>>> [image: Inline image 2]
>>>>>>>> and based on the paper which represents this topology it is
>>>>>>>> expected to get this figure from it's information:
>>>>>>>> [image: Inline image 3]
>>>>>>>> which the blue "+" represents the ping-data in the case that no
>>>>>>>> node fails, but when I try to implement it using pingall experiment my
>>>>>>>> figure will come out like this:
>>>>>>>> [image: Inline image 4]
>>>>>>>> as you can see there is more swing in the blue '+'s than it is
>>>>>>>> expected, any idea why it is happening?
>>>>>>>> thank you
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sepehr Abdous
>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>> Cellphone:+989194030591
>>>>>>>> School of computer engineering
>>>>>>>> Sharif University of Technology
>>>>>>>> Tehran, Iran
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sepehr Abdous
>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>> Cellphone:+989194030591
>>>>>>> School of computer engineering
>>>>>>> Sharif University of Technology
>>>>>>> Tehran, Iran
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sepehr Abdous
>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>> Cellphone:+989194030591
>>>>>> School of computer engineering
>>>>>> Sharif University of Technology
>>>>>> Tehran, Iran
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sepehr Abdous
>>>>> Faculty: abdous at ce.sharif.edu
>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>> Cellphone:+989194030591
>>>>> School of computer engineering
>>>>> Sharif University of Technology
>>>>> Tehran, Iran
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sepehr Abdous
>>>> Faculty: abdous at ce.sharif.edu
>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>> Cellphone:+989194030591
>>>> School of computer engineering
>>>> Sharif University of Technology
>>>> Tehran, Iran
>>>>
>>>
>>>
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/2825050d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 150795 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/2825050d/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: photo_2016-11-20_19-21-00.jpg
Type: image/jpeg
Size: 96638 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/2825050d/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 53235 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/2825050d/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/2825050d/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/2825050d/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/2825050d/attachment-0009.png>

From lanwang at memphis.edu  Mon Nov 21 20:21:32 2016
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Tue, 22 Nov 2016 04:21:32 +0000
Subject: [Mini-NDN] result of a topology
In-Reply-To: <CAKaOrig-TDR4T55G6tb+HPXjTX97KiO5avRVBaz4sWCu8QPgCg@mail.gmail.com>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
	<BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>
	<BN3PR04MB2196358A45A5793060774C56D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijQe2_Qw4OYE9GAoXUM-aL4HRFdN791BzFvN7-UZTaRWw@mail.gmail.com>
	<BN3PR04MB219693FE0EA16A57D6A1B306D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig-TDR4T55G6tb+HPXjTX97KiO5avRVBaz4sWCu8QPgCg@mail.gmail.com>
Message-ID: <4057B4D3-BDC4-49EA-BFD2-86A6BE214DA4@memphis.edu>

Yes, we fail a node in the experiment for some time period.

The red line that has a gap is for single path routing/forwarding.  You need to set the multipath factor to 1 (number of faces in the FIB for each prefix) in the NLSR configuration to achieve this effect.  If I remember correctly, when the number is 0, the router will put all the faces in the FIB entry (ranked by their path cost).

We have an updated version of the paper as an NDN technical report: https://named-data.net/wp-content/uploads/2016/01/ndn-0037-1-nlsr.pdf.  It doesn?t have this specific figure though.

Lan

On Nov 21, 2016, at 4:01 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:

thank you very much

On Tue, Nov 22, 2016 at 1:29 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Yes it will happen automatically. I think in the paper the node was down for 2 minutes then brought up.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:57: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] result of a topology

so you mean that it will automatically happen and I shouldn't consider anything for it in my experiment?

On Tue, Nov 22, 2016 at 1:18 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Oh I see, convergence for the best path will happen automatically once the node recovers (i.e. once NLSR comes back up on the failed node).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:46:05 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] result of a topology

then how can that gap be explained?
I mean then why that convergence gap is considered in the paper's figure?

On Tue, Nov 22, 2016 at 1:12 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

So when the node is failed, NFD should automatically use the next best path installed by NLSR. Convergence is already checked before running the experiment: https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L82


If it does not, then maybe the max-faces-per-prefix is set to 3 by default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115) .You can use the option --faces 0 in Mini-NDN to use all the available paths and then it should use the next best path. This probably won't happen with this small topology.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:36:44 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] result of a topology

ok thank you very much
I also have another question:
as you can see, the red marks in the paper's figure have a gap of about 60 seconds after that node4 fails,
how can I produce this gap or in another words cause convergence after node's failure in my experiment, I know how to put the node off and how to get in back on but I don't know how to cause convergence in my experiment...?

On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You can try 20 or 30 ms and see if you get better results?


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Monday, November 21, 2016 3:03:47 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] result of a topology

what would a reasonable delay be?

On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Why is the delay zero, I think non-zero delay might give smoother result.


Do you want to send 99999999 pings in 200 seconds?


ndnping allows to send at most 1000 pings/second, so in 200 seconds you can send 200,000 pings at best by using the option "-i 1" here:

https://github.com/named-data/mini-ndn/blob/master/ndn/experiments/experiment.py#L92


You can modify ndnping if you want to have more pings than that.


(This will be heavy on the CPU).


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Sunday, November 20, 2016 9:54:22 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] result of a topology

I changed the cpu of the machine and the figure became like:
<photo_2016-11-20_19-21-00.jpg>
as you can see the swap is ok
now I've got a question about the number of pings?
how can I write the experiment to have the maximum number of pings in 200 seconds.
my current experiment is :
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 99999999
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

which the number 99999999 is to have as many pings as possible,
how can I get the maximum pings possible?


On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
the delay is zero
the topology file is:
[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE max-faces-per-prefix=0 nfd-log-level=NONE
[switches]
[links]
node1:node2
node1:node3
node3:node5
node5:node6
node6:node4
node4:node2
node4:node3
node3:node6


On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

No, the figure of the paper should be possible to achieve. The CPU is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a single machine. I have run a 10 node pingall experiment on a VBox VM with 2.5GB RAM and 2 CPUs without so much variation.


To turn off the logs:

Change DEBUG to NONE here:

https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123


and make sure that this also set to NONE:

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34


Then reinstall Mini-NDN, sudo ./install.sh -i


Also make sure that in your topology file all the log levels are set to NONE if there is such an option after the nodes.


Then try to run the experiment again (If possible turn off the GUI in VM, i.e. login in to command line and run the experiment from there - just to free up some more CPU).


In your graph the y-axis is the RTT in ms? What are the delays you have set on the links of the topology?

(If possible, can you share the topology file?)


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Saturday, November 19, 2016 12:48:23 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] result of a topology

Hello,
no there aren't any timeouts and what you see there is not a zero it is 10^0 which is equal to 1.
I'm running my linux on a vmware virtual machine with the configurations bellow:
<image.png>
so you're saying that this results which I've got in my figure is reasonable for the topology and it shouldn't exactly be like the figure in the paper?
Thank you

On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Have you verified that the ping data is correctly depicted on your figure?

Are there any timeouts in there? Because I see some zeros.


RTT can be have variation in Mini-NDN because of multiple NFDs are running on the same machine.


What is your current machine configuration?

Usually for such a small topology it should not be a problem.



One thing you can try is that if you are collecting NFD, NLSR, or any other logs, turn them off.

That is turn off all the logs except the ping data.


Other thing to try is to use a machine with more CPU power.



Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, November 18, 2016 6:48:35 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] result of a topology

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology:
<Untitled.png>
so I use minindnedit to implement it with the following information:
<Untitled.png>
and based on the paper which represents this topology it is expected to get this figure from it's information:
<Untitled.png>
which the blue "+" represents the ping-data in the case that no node fails, but when I try to implement it using pingall experiment my figure will come out like this:
<image.png>
as you can see there is more swing in the blue '+'s than it is expected, any idea why it is happening?
thank you

--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn

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

From sepehrabdous1375 at gmail.com  Mon Nov 21 23:53:34 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 22 Nov 2016 11:23:34 +0330
Subject: [Mini-NDN] result of a topology
In-Reply-To: <4057B4D3-BDC4-49EA-BFD2-86A6BE214DA4@memphis.edu>
References: <CAKaOrig1NEJ_9FnTmLq-ELEuNWUxg2oCg3NBkunAKGNJShF+1w@mail.gmail.com>
	<SN2PR04MB2205D9C17B9620EC659C5626D9B00@SN2PR04MB2205.namprd04.prod.outlook.com>
	<CAKaOriii4wUe50LkCU5cymGkbg0Eb5u_dUONw5mprQ20KzcQ3w@mail.gmail.com>
	<BN3PR04MB2196C829FF2560A88B429288D9B30@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijNwwvb-Wm0FHTC_zp8uQpdyXE+BE_=Dbcgx_0GwCva+A@mail.gmail.com>
	<CAKaOrihicUH7fz0DXdAEB3po9XaHNHga9ee955UMacmXu_izYQ@mail.gmail.com>
	<BN3PR04MB21963A773A9271C33145B1B8D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig9NsKyhc0ePsC3P=hd2hBiT3Hhi=48PVgcgfcj2UMbTQ@mail.gmail.com>
	<BN3PR04MB219696EE04043FF17211FB3ED9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrihPM+Su64UzVr4Yp0JTCkn8=+vvqxR8pQY00EyzkGiKTg@mail.gmail.com>
	<BN3PR04MB2196E52ED5E4757281D03BEBD9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOriiBtzMuiCXpYadaUnLq1PbYX3NogWT9vjG16CW_kLW3gg@mail.gmail.com>
	<BN3PR04MB2196358A45A5793060774C56D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrijQe2_Qw4OYE9GAoXUM-aL4HRFdN791BzFvN7-UZTaRWw@mail.gmail.com>
	<BN3PR04MB219693FE0EA16A57D6A1B306D9B50@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrig-TDR4T55G6tb+HPXjTX97KiO5avRVBaz4sWCu8QPgCg@mail.gmail.com>
	<4057B4D3-BDC4-49EA-BFD2-86A6BE214DA4@memphis.edu>
Message-ID: <CAKaOrihboCBQhiJObz4JWrgQscMu=H-LVc-etcJ7ghSFEYT_gw@mail.gmail.com>

Thank you very much

On Nov 22, 2016 7:51 AM, "Lan Wang (lanwang)" <lanwang at memphis.edu> wrote:

> Yes, we fail a node in the experiment for some time period.
>
> The red line that has a gap is for single path routing/forwarding.  You
> need to set the multipath factor to 1 (number of faces in the FIB for each
> prefix) in the NLSR configuration to achieve this effect.  If I remember
> correctly, when the number is 0, the router will put all the faces in the
> FIB entry (ranked by their path cost).
>
> We have an updated version of the paper as an NDN technical report:
> https://named-data.net/wp-content/uploads/2016/01/ndn-0037-1-nlsr.pdf.
> It doesn?t have this specific figure though.
>
> Lan
>
> On Nov 21, 2016, at 4:01 PM, sepehr abdous <sepehrabdous1375 at gmail.com>
> wrote:
>
> thank you very much
>
> On Tue, Nov 22, 2016 at 1:29 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> Yes it will happen automatically. I think in the paper the node was down
>> for 2 minutes then brought up.
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Monday, November 21, 2016 3:57:39 PM
>>
>> *To:* Ashlesh Gawande (agawande)
>> *Cc:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] result of a topology
>>
>> so you mean that it will automatically happen and I shouldn't consider
>> anything for it in my experiment?
>>
>> On Tue, Nov 22, 2016 at 1:18 AM, Ashlesh Gawande (agawande) <
>> agawande at memphis.edu> wrote:
>>
>>> Oh I see, convergence for the best path will happen automatically once
>>> the node recovers (i.e. once NLSR comes back up on the failed node).
>>>
>>>
>>> Ashlesh
>>> ------------------------------
>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>> *Sent:* Monday, November 21, 2016 3:46:05 PM
>>>
>>> *To:* Ashlesh Gawande (agawande)
>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>
>>> then how can that gap be explained?
>>> I mean then why that convergence gap is considered in the paper's figure?
>>>
>>> On Tue, Nov 22, 2016 at 1:12 AM, Ashlesh Gawande (agawande) <
>>> agawande at memphis.edu> wrote:
>>>
>>>> So when the node is failed, NFD should automatically use the next best
>>>> path installed by NLSR. Convergence is already checked before running the
>>>> experiment: https://github.com/named-data/mini-ndn/blob/mast
>>>> er/ndn/experiments/experiment.py#L82
>>>>
>>>>
>>>> If it does not, then maybe the max-faces-per-prefix is set to 3 by
>>>> default (https://github.com/named-data/NLSR/blob/master/nlsr.conf#L115)
>>>> .You can use the option --faces 0 in Mini-NDN to use all the available
>>>> paths and then it should use the next best path. This probably won't happen
>>>> with this small topology.
>>>>
>>>>
>>>> Ashlesh
>>>> ------------------------------
>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>> *Sent:* Monday, November 21, 2016 3:36:44 PM
>>>>
>>>> *To:* Ashlesh Gawande (agawande)
>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>
>>>> ok thank you very much
>>>> I also have another question:
>>>> as you can see, the red marks in the paper's figure have a gap of about
>>>> 60 seconds after that node4 fails,
>>>> how can I produce this gap or in another words cause convergence after
>>>> node's failure in my experiment, I know how to put the node off and how to
>>>> get in back on but I don't know how to cause convergence in my
>>>> experiment...?
>>>>
>>>> On Tue, Nov 22, 2016 at 12:40 AM, Ashlesh Gawande (agawande) <
>>>> agawande at memphis.edu> wrote:
>>>>
>>>>> You can try 20 or 30 ms and see if you get better results?
>>>>>
>>>>>
>>>>> Ashlesh
>>>>> ------------------------------
>>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>> *Sent:* Monday, November 21, 2016 3:03:47 PM
>>>>>
>>>>> *To:* Ashlesh Gawande (agawande)
>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>>
>>>>> what would a reasonable delay be?
>>>>>
>>>>> On Tue, Nov 22, 2016 at 12:11 AM, Ashlesh Gawande (agawande) <
>>>>> agawande at memphis.edu> wrote:
>>>>>
>>>>>> Why is the delay zero, I think non-zero delay might give smoother
>>>>>> result.
>>>>>>
>>>>>>
>>>>>> Do you want to send 99999999 pings in 200 seconds?
>>>>>>
>>>>>>
>>>>>> ndnping allows to send at most 1000 pings/second, so in 200 seconds
>>>>>> you can send 200,000 pings at best by using the option "-i 1" here:
>>>>>>
>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/exper
>>>>>> iments/experiment.py#L92
>>>>>>
>>>>>>
>>>>>> You can modify ndnping if you want to have more pings than that.
>>>>>>
>>>>>>
>>>>>> (This will be heavy on the CPU).
>>>>>>
>>>>>>
>>>>>> Ashlesh
>>>>>> ------------------------------
>>>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>> *Sent:* Sunday, November 20, 2016 9:54:22 AM
>>>>>>
>>>>>> *To:* Ashlesh Gawande (agawande)
>>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>>>
>>>>>> I changed the cpu of the machine and the figure became like:
>>>>>> <photo_2016-11-20_19-21-00.jpg>
>>>>>> as you can see the swap is ok
>>>>>> now I've got a question about the number of pings?
>>>>>> how can I write the experiment to have the maximum number of pings in
>>>>>> 200 seconds.
>>>>>> my current experiment is :
>>>>>> from ndn.experiments.experiment import Experiment
>>>>>> from ndn.nlsr import Nlsr
>>>>>>
>>>>>> import time
>>>>>>
>>>>>> class pingallreg(Experiment):
>>>>>>
>>>>>>     def __init__(self, args):
>>>>>>         args["nPings"] = 99999999
>>>>>>         Experiment.__init__(self, args)
>>>>>>
>>>>>>     def run(self):
>>>>>>         self.startPctPings()
>>>>>>         time.sleep(200)
>>>>>>
>>>>>> Experiment.register("wofail", pingallreg)
>>>>>>
>>>>>> which the number 99999999 is to have as many pings as possible,
>>>>>> how can I get the maximum pings possible?
>>>>>>
>>>>>>
>>>>>> On Sun, Nov 20, 2016 at 5:34 PM, sepehr abdous <
>>>>>> sepehrabdous1375 at gmail.com> wrote:
>>>>>>
>>>>>>> the delay is zero
>>>>>>> the topology file is:
>>>>>>> [nodes]
>>>>>>> node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>>> router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=NONE
>>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>>> node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>>> router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
>>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>>> node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>>> router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=NONE
>>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>>> node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>>> router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=NONE
>>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>>> node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>>> router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=NONE
>>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>>> node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
>>>>>>> router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=NONE
>>>>>>> max-faces-per-prefix=0 nfd-log-level=NONE
>>>>>>> [switches]
>>>>>>> [links]
>>>>>>> node1:node2
>>>>>>> node1:node3
>>>>>>> node3:node5
>>>>>>> node5:node6
>>>>>>> node6:node4
>>>>>>> node4:node2
>>>>>>> node4:node3
>>>>>>> node3:node6
>>>>>>>
>>>>>>>
>>>>>>> On Sat, Nov 19, 2016 at 5:27 PM, Ashlesh Gawande (agawande) <
>>>>>>> agawande at memphis.edu> wrote:
>>>>>>>
>>>>>>>> No, the figure of the paper should be possible to achieve. The CPU
>>>>>>>> is the bottleneck because one has to run 6 NFD, 6 NLSR instances on a
>>>>>>>> single machine. I have run a 10 node pingall experiment on a VBox VM with
>>>>>>>> 2.5GB RAM and 2 CPUs without so much variation.
>>>>>>>>
>>>>>>>>
>>>>>>>> To turn off the logs:
>>>>>>>>
>>>>>>>> Change DEBUG to NONE here:
>>>>>>>>
>>>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nlsr.py#L123
>>>>>>>>
>>>>>>>>
>>>>>>>> and make sure that this also set to NONE:
>>>>>>>>
>>>>>>>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L34
>>>>>>>>
>>>>>>>>
>>>>>>>> Then reinstall Mini-NDN, sudo ./install.sh -i
>>>>>>>>
>>>>>>>>
>>>>>>>> Also make sure that in your topology file all the log levels are
>>>>>>>> set to NONE if there is such an option after the nodes.
>>>>>>>>
>>>>>>>>
>>>>>>>> Then try to run the experiment again (If possible turn off the GUI
>>>>>>>> in VM, i.e. login in to command line and run the experiment from there -
>>>>>>>> just to free up some more CPU).
>>>>>>>>
>>>>>>>>
>>>>>>>> In your graph the y-axis is the RTT in ms? What are the delays you
>>>>>>>> have set on the links of the topology?
>>>>>>>>
>>>>>>>> (If possible, can you share the topology file?)
>>>>>>>>
>>>>>>>>
>>>>>>>> Ashlesh
>>>>>>>> ------------------------------
>>>>>>>> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>>>> *Sent:* Saturday, November 19, 2016 12:48:23 AM
>>>>>>>> *To:* Ashlesh Gawande (agawande)
>>>>>>>> *Cc:* mini-ndn at lists.cs.ucla.edu
>>>>>>>> *Subject:* Re: [Mini-NDN] result of a topology
>>>>>>>>
>>>>>>>> Hello,
>>>>>>>> no there aren't any timeouts and what you see there is not a zero
>>>>>>>> it is 10^0 which is equal to 1.
>>>>>>>> I'm running my linux on a vmware virtual machine with the
>>>>>>>> configurations bellow:
>>>>>>>> <image.png>
>>>>>>>> so you're saying that this results which I've got in my figure is
>>>>>>>> reasonable for the topology and it shouldn't exactly be like the figure in
>>>>>>>> the paper?
>>>>>>>> Thank you
>>>>>>>>
>>>>>>>> On Fri, Nov 18, 2016 at 4:53 PM, Ashlesh Gawande (agawande) <
>>>>>>>> agawande at memphis.edu> wrote:
>>>>>>>>
>>>>>>>>> Have you verified that the ping data is correctly depicted on your
>>>>>>>>> figure?
>>>>>>>>>
>>>>>>>>> Are there any timeouts in there? Because I see some zeros.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> RTT can be have variation in Mini-NDN because of multiple NFDs are
>>>>>>>>> running on the same machine.
>>>>>>>>>
>>>>>>>>> What is your current machine configuration?
>>>>>>>>>
>>>>>>>>> Usually for such a small topology it should not be a problem.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> One thing you can try is that if you are collecting NFD, NLSR, or
>>>>>>>>> any other logs, turn them off.
>>>>>>>>>
>>>>>>>>> That is turn off all the logs except the ping data.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Other thing to try is to use a machine with more CPU power.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Ashlesh
>>>>>>>>> ------------------------------
>>>>>>>>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf
>>>>>>>>> of sepehr abdous <sepehrabdous1375 at gmail.com>
>>>>>>>>> *Sent:* Friday, November 18, 2016 6:48:35 AM
>>>>>>>>> *To:* mini-ndn at lists.cs.ucla.edu
>>>>>>>>> *Subject:* [Mini-NDN] result of a topology
>>>>>>>>>
>>>>>>>>> Hello all,
>>>>>>>>> I'm new to mini-ndn and I'm trying to implement the following
>>>>>>>>> topology:
>>>>>>>>> <Untitled.png>
>>>>>>>>> so I use minindnedit to implement it with the following
>>>>>>>>> information:
>>>>>>>>> <Untitled.png>
>>>>>>>>> and based on the paper which represents this topology it is
>>>>>>>>> expected to get this figure from it's information:
>>>>>>>>> <Untitled.png>
>>>>>>>>> which the blue "+" represents the ping-data in the case that no
>>>>>>>>> node fails, but when I try to implement it using pingall experiment my
>>>>>>>>> figure will come out like this:
>>>>>>>>> <image.png>
>>>>>>>>> as you can see there is more swing in the blue '+'s than it is
>>>>>>>>> expected, any idea why it is happening?
>>>>>>>>> thank you
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Sepehr Abdous
>>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>>> Cellphone:+989194030591
>>>>>>>>> School of computer engineering
>>>>>>>>> Sharif University of Technology
>>>>>>>>> Tehran, Iran
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Sepehr Abdous
>>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>>> Cellphone:+989194030591
>>>>>>>> School of computer engineering
>>>>>>>> Sharif University of Technology
>>>>>>>> Tehran, Iran
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Sepehr Abdous
>>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>>> Cellphone:+989194030591
>>>>>>> School of computer engineering
>>>>>>> Sharif University of Technology
>>>>>>> Tehran, Iran
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sepehr Abdous
>>>>>> Faculty: abdous at ce.sharif.edu
>>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>>> Cellphone:+989194030591
>>>>>> School of computer engineering
>>>>>> Sharif University of Technology
>>>>>> Tehran, Iran
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sepehr Abdous
>>>>> Faculty: abdous at ce.sharif.edu
>>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>>> Cellphone:+989194030591
>>>>> School of computer engineering
>>>>> Sharif University of Technology
>>>>> Tehran, Iran
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Sepehr Abdous
>>>> Faculty: abdous at ce.sharif.edu
>>>> Yahoo mail: sepehrabdous at yahoo.com
>>>> Cellphone:+989194030591
>>>> School of computer engineering
>>>> Sharif University of Technology
>>>> Tehran, Iran
>>>>
>>>
>>>
>>>
>>> --
>>> Sepehr Abdous
>>> Faculty: abdous at ce.sharif.edu
>>> Yahoo mail: sepehrabdous at yahoo.com
>>> Cellphone:+989194030591
>>> School of computer engineering
>>> Sharif University of Technology
>>> Tehran, Iran
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161122/0297ab0b/attachment-0001.html>

From Matteo.Bertolino at eurecom.fr  Wed Nov 23 02:25:33 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Wed, 23 Nov 2016 11:25:33 +0100
Subject: [Mini-NDN] Where does mini start the nfd?
Message-ID: <20161123112533.tseknslmw4g8w088@webmail.eurecom.fr>

Good morning,
I would like to study how mini launch several NFD instance on its nodes.

Where I open minindn script, I don't read something like "sudo nfd-start"  or
"sudo /NFD/bin/nfd".


I just read:

nfdConfFile = "%s/nfd.conf" % install_dir
     if os.path.isfile("/usr/local/etc/ndn/nfd.conf") == True:
         shutil.copy2("/usr/local/etc/ndn/nfd.conf", nfdConfFile)
     elif os.path.isfile("/usr/local/etc/ndn/nfd.conf.sample") == True:
         shutil.copy2("/usr/local/etc/ndn/nfd.conf.sample", nfdConfFile)
     else:
         sys.exit("nfd.conf or nfd.conf.sample cannot be found in the  
expected directory. Exit.")

     call(["sudo", "sed", "-i", 's|default_level [A-Z]*$|default_level  
$LOG_LEVEL|g', nfdConfFile])

Where is the nfd started?

Thanks!

-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr


From agawande at memphis.edu  Wed Nov 23 05:06:55 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Wed, 23 Nov 2016 13:06:55 +0000
Subject: [Mini-NDN] Where does mini start the nfd?
Message-ID: <SN2PR04MB22050B80DC335E3FF735DB7DD9B70@SN2PR04MB2205.namprd04.prod.outlook.com>

https://github.com/named-data/mini-ndn/blob/master/ndn/ndn_host.py#L102

https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L62

Ashlesh

On Nov 23, 2016 4:25 AM, Matteo Bertolino <Matteo.Bertolino at eurecom.fr> wrote:
Good morning,
I would like to study how mini launch several NFD instance on its nodes.

Where I open minindn script, I don't read something like "sudo nfd-start"  or
"sudo /NFD/bin/nfd".


I just read:

nfdConfFile = "%s/nfd.conf" % install_dir
     if os.path.isfile("/usr/local/etc/ndn/nfd.conf") == True:
         shutil.copy2("/usr/local/etc/ndn/nfd.conf", nfdConfFile)
     elif os.path.isfile("/usr/local/etc/ndn/nfd.conf.sample") == True:
         shutil.copy2("/usr/local/etc/ndn/nfd.conf.sample", nfdConfFile)
     else:
         sys.exit("nfd.conf or nfd.conf.sample cannot be found in the
expected directory. Exit.")

     call(["sudo", "sed", "-i", 's|default_level [A-Z]*$|default_level
$LOG_LEVEL|g', nfdConfFile])

Where is the nfd started?

Thanks!

-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr

_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161123/7f39324a/attachment.html>

From Matteo.Bertolino at eurecom.fr  Wed Nov 23 05:19:41 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Wed, 23 Nov 2016 14:19:41 +0100
Subject: [Mini-NDN] Where does mini start the nfd?
In-Reply-To: <SN2PR04MB22050B80DC335E3FF735DB7DD9B70@SN2PR04MB2205.namprd04.prod.outlook.com>
References: <SN2PR04MB22050B80DC335E3FF735DB7DD9B70@SN2PR04MB2205.namprd04.prod.outlook.com>
Message-ID: <20161123141941.k6zaeza1w0wg8wg0@webmail.eurecom.fr>

Thanks! An important question.

I would like to avoid mini and run two nfd different istances in two  
different process.
I noticed that it is not possible use nfd-start, then I do the following:

Process 1:
nfd --config nfd.conf

Process 2:
nfd --config nfd2.conf

Where "diff nfd.conf nfd2.conf" is:
90c90
<     path /var/run/nfd.sock ; Unix stream listener path
---
>     path /var/run/nfd2.sock ; Unix stream listener path
97c97
<     port 6363 ; TCP listener port number
---
>     port 6364 ; TCP listener port number
106c106
<     port 6363 ; UDP unicast port number
---
>     port 6364 ; UDP unicast port number
179c179
<     port 9696 ; WebSocket listener port number
---
>     port 9697 ; WebSocket listener port number


I noticed that it is not enough. I had a look on the code that you  
passed me in the previous answer. I notice that client.conf file has a  
role. How can I reach my goal?
Thanks a lot.

matteo



Quoting "Ashlesh Gawande (agawande)" <agawande at memphis.edu>:

> https://github.com/named-data/mini-ndn/blob/master/ndn/ndn_host.py#L102
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L62
>
> Ashlesh
>
> On Nov 23, 2016 4:25 AM, Matteo Bertolino   
> <Matteo.Bertolino at eurecom.fr> wrote:
> Good morning,
> I would like to study how mini launch several NFD instance on its nodes.
>
> Where I open minindn script, I don't read something like "sudo nfd-start"  or
> "sudo /NFD/bin/nfd".
>
>
> I just read:
>
> nfdConfFile = "%s/nfd.conf" % install_dir
>      if os.path.isfile("/usr/local/etc/ndn/nfd.conf") == True:
>          shutil.copy2("/usr/local/etc/ndn/nfd.conf", nfdConfFile)
>      elif os.path.isfile("/usr/local/etc/ndn/nfd.conf.sample") == True:
>          shutil.copy2("/usr/local/etc/ndn/nfd.conf.sample", nfdConfFile)
>      else:
>          sys.exit("nfd.conf or nfd.conf.sample cannot be found in the
> expected directory. Exit.")
>
>      call(["sudo", "sed", "-i", 's|default_level [A-Z]*$|default_level
> $LOG_LEVEL|g', nfdConfFile])
>
> Where is the nfd started?
>
> Thanks!
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr



From agawande at memphis.edu  Wed Nov 23 06:59:52 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Wed, 23 Nov 2016 14:59:52 +0000
Subject: [Mini-NDN] Where does mini start the nfd?
In-Reply-To: <20161123141941.k6zaeza1w0wg8wg0@webmail.eurecom.fr>
References: <SN2PR04MB22050B80DC335E3FF735DB7DD9B70@SN2PR04MB2205.namprd04.prod.outlook.com>,
	<20161123141941.k6zaeza1w0wg8wg0@webmail.eurecom.fr>
Message-ID: <SN2PR04MB2205F050085533A5C0309384D9B70@SN2PR04MB2205.namprd04.prod.outlook.com>

I am not sure how you would run two instances without Mini-NDN.


client.conf tells programs (NLSR etc.) how to connect to NFD i.e. which sock file/transport to use.


I think you can export different $HOME in two different terminals and then put two different client files in there and then run NFD.


Ashlesh

________________________________
From: Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Wednesday, November 23, 2016 7:19:41 AM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Where does mini start the nfd?

Thanks! An important question.

I would like to avoid mini and run two nfd different istances in two
different process.
I noticed that it is not possible use nfd-start, then I do the following:

Process 1:
nfd --config nfd.conf

Process 2:
nfd --config nfd2.conf

Where "diff nfd.conf nfd2.conf" is:
90c90
<     path /var/run/nfd.sock ; Unix stream listener path
---
>     path /var/run/nfd2.sock ; Unix stream listener path
97c97
<     port 6363 ; TCP listener port number
---
>     port 6364 ; TCP listener port number
106c106
<     port 6363 ; UDP unicast port number
---
>     port 6364 ; UDP unicast port number
179c179
<     port 9696 ; WebSocket listener port number
---
>     port 9697 ; WebSocket listener port number


I noticed that it is not enough. I had a look on the code that you
passed me in the previous answer. I notice that client.conf file has a
role. How can I reach my goal?
Thanks a lot.

matteo



Quoting "Ashlesh Gawande (agawande)" <agawande at memphis.edu>:

> https://github.com/named-data/mini-ndn/blob/master/ndn/ndn_host.py#L102
>
> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L62
>
> Ashlesh
>
> On Nov 23, 2016 4:25 AM, Matteo Bertolino
> <Matteo.Bertolino at eurecom.fr> wrote:
> Good morning,
> I would like to study how mini launch several NFD instance on its nodes.
>
> Where I open minindn script, I don't read something like "sudo nfd-start"  or
> "sudo /NFD/bin/nfd".
>
>
> I just read:
>
> nfdConfFile = "%s/nfd.conf" % install_dir
>      if os.path.isfile("/usr/local/etc/ndn/nfd.conf") == True:
>          shutil.copy2("/usr/local/etc/ndn/nfd.conf", nfdConfFile)
>      elif os.path.isfile("/usr/local/etc/ndn/nfd.conf.sample") == True:
>          shutil.copy2("/usr/local/etc/ndn/nfd.conf.sample", nfdConfFile)
>      else:
>          sys.exit("nfd.conf or nfd.conf.sample cannot be found in the
> expected directory. Exit.")
>
>      call(["sudo", "sed", "-i", 's|default_level [A-Z]*$|default_level
> $LOG_LEVEL|g', nfdConfFile])
>
> Where is the nfd started?
>
> Thanks!
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr

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

From Matteo.Bertolino at eurecom.fr  Wed Nov 23 09:18:08 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Wed, 23 Nov 2016 18:18:08 +0100
Subject: [Mini-NDN] Where does mini start the nfd?
In-Reply-To: <SN2PR04MB2205F050085533A5C0309384D9B70@SN2PR04MB2205.namprd04.prod.outlook.com>
References: <SN2PR04MB22050B80DC335E3FF735DB7DD9B70@SN2PR04MB2205.namprd04.prod.outlook.com>,
	<20161123141941.k6zaeza1w0wg8wg0@webmail.eurecom.fr>
	<SN2PR04MB2205F050085533A5C0309384D9B70@SN2PR04MB2205.namprd04.prod.outlook.com>
Message-ID: <20161123181808.ohsm6l1p3k8oooc0@webmail.eurecom.fr>

I confirm that your solution is right!
Thank you for the advices Ashlesh!!
matteo

Quoting "Ashlesh Gawande (agawande)" <agawande at memphis.edu>:

> I am not sure how you would run two instances without Mini-NDN.
>
>
> client.conf tells programs (NLSR etc.) how to connect to NFD i.e.   
> which sock file/transport to use.
>
>
> I think you can export different $HOME in two different terminals   
> and then put two different client files in there and then run NFD.
>
>
> Ashlesh
>
> ________________________________
> From: Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
> Sent: Wednesday, November 23, 2016 7:19:41 AM
> To: Ashlesh Gawande (agawande)
> Cc: mini-ndn at lists.cs.ucla.edu
> Subject: Re: [Mini-NDN] Where does mini start the nfd?
>
> Thanks! An important question.
>
> I would like to avoid mini and run two nfd different istances in two
> different process.
> I noticed that it is not possible use nfd-start, then I do the following:
>
> Process 1:
> nfd --config nfd.conf
>
> Process 2:
> nfd --config nfd2.conf
>
> Where "diff nfd.conf nfd2.conf" is:
> 90c90
> <     path /var/run/nfd.sock ; Unix stream listener path
> ---
>>     path /var/run/nfd2.sock ; Unix stream listener path
> 97c97
> <     port 6363 ; TCP listener port number
> ---
>>     port 6364 ; TCP listener port number
> 106c106
> <     port 6363 ; UDP unicast port number
> ---
>>     port 6364 ; UDP unicast port number
> 179c179
> <     port 9696 ; WebSocket listener port number
> ---
>>     port 9697 ; WebSocket listener port number
>
>
> I noticed that it is not enough. I had a look on the code that you
> passed me in the previous answer. I notice that client.conf file has a
> role. How can I reach my goal?
> Thanks a lot.
>
> matteo
>
>
>
> Quoting "Ashlesh Gawande (agawande)" <agawande at memphis.edu>:
>
>> https://github.com/named-data/mini-ndn/blob/master/ndn/ndn_host.py#L102
>>
>> https://github.com/named-data/mini-ndn/blob/master/ndn/nfd.py#L62
>>
>> Ashlesh
>>
>> On Nov 23, 2016 4:25 AM, Matteo Bertolino
>> <Matteo.Bertolino at eurecom.fr> wrote:
>> Good morning,
>> I would like to study how mini launch several NFD instance on its nodes.
>>
>> Where I open minindn script, I don't read something like "sudo   
>> nfd-start"  or
>> "sudo /NFD/bin/nfd".
>>
>>
>> I just read:
>>
>> nfdConfFile = "%s/nfd.conf" % install_dir
>>      if os.path.isfile("/usr/local/etc/ndn/nfd.conf") == True:
>>          shutil.copy2("/usr/local/etc/ndn/nfd.conf", nfdConfFile)
>>      elif os.path.isfile("/usr/local/etc/ndn/nfd.conf.sample") == True:
>>          shutil.copy2("/usr/local/etc/ndn/nfd.conf.sample", nfdConfFile)
>>      else:
>>          sys.exit("nfd.conf or nfd.conf.sample cannot be found in the
>> expected directory. Exit.")
>>
>>      call(["sudo", "sed", "-i", 's|default_level [A-Z]*$|default_level
>> $LOG_LEVEL|g', nfdConfFile])
>>
>> Where is the nfd started?
>>
>> Thanks!
>>
>> -------------------------------------------------------------------------------
>> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>>
>> _______________________________________________
>> Mini-NDN mailing list
>> Mini-NDN at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>>
>
>
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
>



-------------------------------------------------------------------------------
This message was sent using EURECOM Webmail: http://webmail.eurecom.fr



From sepehrabdous1375 at gmail.com  Wed Nov 23 14:01:59 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Thu, 24 Nov 2016 01:31:59 +0330
Subject: [Mini-NDN] topology result
Message-ID: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>

Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology

[image: Inline image 2]
I implemented it with the following information:
[image: Inline image 3]
and based on the paper the expected results on ping is :
[image: Inline image 4]
but when I implement it I get the following image

[image: Inline image 5]
and as you can see there are some problems:
(1) the values on the y-axis is much higher than in the paper, I figured
out that It's caused by the delay, I set the delay for every link to 20ms
so the values are around 80ms but when I set the delay to 0ms the values
are around 10ms but the swing of values become more and values are not
united like when the delay is 20ms
(2) as you can see when node4 fails we have some values that shows
something happened:
[image: Inline image 6]
but this values doesn't exist in my figure.
(3) the density of red points in my figure isn't the same in all aspects.
can you please help me with this problems.
Thank you
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/b1daff01/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(1).png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/b1daff01/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NLSR.jpg
Type: image/jpeg
Size: 24551 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/b1daff01/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image(1).png
Type: image/png
Size: 42436 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/b1daff01/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/b1daff01/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(2).png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/b1daff01/attachment-0007.png>

From sepehrabdous1375 at gmail.com  Wed Nov 23 14:06:01 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Thu, 24 Nov 2016 01:36:01 +0330
Subject: [Mini-NDN] topology result
In-Reply-To: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>
References: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>
Message-ID: <CAKaOrihiMqb4Ryuo3xSNNZhi06U1-uxxgia+qMzo1SejPPOCoA@mail.gmail.com>

also my experiments codes are:
for blue points:


from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 200000
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

and for red points which involve failure:

from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class fail(Experiment):

    def __init__(self, args):
        args["nPings"] = 140000
        Experiment.__init__(self, args)

        self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
        self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20

    def run(self):
        self.startPctPings()

        # After the pings are scheduled, collect pings for 1 minute
        time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)

        # Bring down CSU
        for host in self.net.hosts:
            if host.name == "node4":
                self.failNode(host)
                break

        # CSU is down for 2 minutes
        time.sleep(120)

        # Bring CSU back up
        for host in self.net.hosts:
            if host.name == "node4":
                self.recoverNode(host)

                for other in self.net.hosts:
                    if host.name != other.name:
                        self.ping(host, other,
self.PING_COLLECTION_TIME_AFTER_RECOVERY)

        # Collect pings for more seconds after CSU is up
        time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)

Experiment.register("failone", fail)



On Thu, Nov 24, 2016 at 1:31 AM, sepehr abdous <sepehrabdous1375 at gmail.com>
wrote:

> Hello all,
> I'm new to mini-ndn and I'm trying to implement the following topology
>
> [image: Inline image 2]
> I implemented it with the following information:
> [image: Inline image 3]
> and based on the paper the expected results on ping is :
> [image: Inline image 4]
> but when I implement it I get the following image
>
> [image: Inline image 5]
> and as you can see there are some problems:
> (1) the values on the y-axis is much higher than in the paper, I figured
> out that It's caused by the delay, I set the delay for every link to 20ms
> so the values are around 80ms but when I set the delay to 0ms the values
> are around 10ms but the swing of values become more and values are not
> united like when the delay is 20ms
> (2) as you can see when node4 fails we have some values that shows
> something happened:
> [image: Inline image 6]
> but this values doesn't exist in my figure.
> (3) the density of red points in my figure isn't the same in all aspects.
> can you please help me with this problems.
> Thank you
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/ecd44bf4/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(2).png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/ecd44bf4/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image(1).png
Type: image/png
Size: 42436 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/ecd44bf4/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NLSR.jpg
Type: image/jpeg
Size: 24551 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/ecd44bf4/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(1).png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/ecd44bf4/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/ecd44bf4/attachment-0007.png>

From agawande at memphis.edu  Wed Nov 23 23:02:40 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 24 Nov 2016 07:02:40 +0000
Subject: [Mini-NDN] topology result
In-Reply-To: <CAKaOrihiMqb4Ryuo3xSNNZhi06U1-uxxgia+qMzo1SejPPOCoA@mail.gmail.com>
References: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>,
	<CAKaOrihiMqb4Ryuo3xSNNZhi06U1-uxxgia+qMzo1SejPPOCoA@mail.gmail.com>
Message-ID: <BN3PR04MB21965B872501ED9D03ACDF9BD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>

1) I think the experiment from paper was run on real testbed which would explain the outliers in the RTT.


2) The experiment for blue line is not correct as it also a failure experiment. The difference is the number of faces.

For blue line the experiment would be the same as the red line except you would run mini-NDN with option --faces 0 (i.e. multipath). For the red line you would run with --faces 1 (i.e. single path).


Blue line:

sudo minindn --experiment=failureExp --faces 0


Red line:

sudo minindn --experiment=failureExp --faces 1


3) I am not sure about the density but the figure on the paper should not have more than 200 pings. Maybe the small size of the figure and different point size is leading to more observed density.

Another case could be that there are some timeouts in your experiment that are not represented on the graphs?


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Wednesday, November 23, 2016 4:06:01 PM
To: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] topology result

also my experiments codes are:
for blue points:


from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 200000
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

and for red points which involve failure:

from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class fail(Experiment):

    def __init__(self, args):
        args["nPings"] = 140000
        Experiment.__init__(self, args)

        self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
        self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20

    def run(self):
        self.startPctPings()

        # After the pings are scheduled, collect pings for 1 minute
        time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)

        # Bring down CSU
        for host in self.net.hosts:
            if host.name<http://host.name> == "node4":
                self.failNode(host)
                break

        # CSU is down for 2 minutes
        time.sleep(120)

        # Bring CSU back up
        for host in self.net.hosts:
            if host.name<http://host.name> == "node4":
                self.recoverNode(host)

                for other in self.net.hosts:
                    if host.name<http://host.name> != other.name<http://other.name>:
                        self.ping(host, other, self.PING_COLLECTION_TIME_AFTER_RECOVERY)

        # Collect pings for more seconds after CSU is up
        time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)

Experiment.register("failone", fail)



On Thu, Nov 24, 2016 at 1:31 AM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology

[Inline image 2]
I implemented it with the following information:
[Inline image 3]
and based on the paper the expected results on ping is :
[Inline image 4]
but when I implement it I get the following image

[Inline image 5]
and as you can see there are some problems:
(1) the values on the y-axis is much higher than in the paper, I figured out that It's caused by the delay, I set the delay for every link to 20ms so the values are around 80ms but when I set the delay to 0ms the values are around 10ms but the swing of values become more and values are not united like when the delay is 20ms
(2) as you can see when node4 fails we have some values that shows something happened:
[Inline image 6]
but this values doesn't exist in my figure.
(3) the density of red points in my figure isn't the same in all aspects.
can you please help me with this problems.
Thank you



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/45c611a0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(2).png
Type: image/png
Size: 29814 bytes
Desc: Untitled(2).png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/45c611a0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image(1).png
Type: image/png
Size: 42436 bytes
Desc: image(1).png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/45c611a0/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NLSR.jpg
Type: image/jpeg
Size: 24551 bytes
Desc: NLSR.jpg
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/45c611a0/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(1).png
Type: image/png
Size: 72749 bytes
Desc: Untitled(1).png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/45c611a0/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/45c611a0/attachment-0007.png>

From sepehrabdous1375 at gmail.com  Thu Nov 24 12:27:18 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Thu, 24 Nov 2016 23:57:18 +0330
Subject: [Mini-NDN] topology result
In-Reply-To: <BN3PR04MB21965B872501ED9D03ACDF9BD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>
	<CAKaOrihiMqb4Ryuo3xSNNZhi06U1-uxxgia+qMzo1SejPPOCoA@mail.gmail.com>
	<BN3PR04MB21965B872501ED9D03ACDF9BD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrigrdCP-fonQzSN-ohA-vWaZNasiwwsJ5XbGA5hqPyistg@mail.gmail.com>

about (2) you mean that I should write the following experiment with
different faces?
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class fail(Experiment):

    def __init__(self, args):
        args["nPings"] = 140000
        Experiment.__init__(self, args)

        self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
        self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20

    def run(self):
        self.startPctPings()

        # After the pings are scheduled, collect pings for 1 minute
        time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)

        # Bring down CSU
        for host in self.net.hosts:
            if host.name == "node4":
                self.failNode(host)
                break

        # CSU is down for 2 minutes
        time.sleep(120)

        # Bring CSU back up
        for host in self.net.hosts:
            if host.name == "node4":
                self.recoverNode(host)

                for other in self.net.hosts:
                    if host.name != other.name:
                        self.ping(host, other, self.PING_COLLECTION_TIME_
AFTER_RECOVERY)

        # Collect pings for more seconds after CSU is up
        time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)

Experiment.register("failone", fail)


On Thu, Nov 24, 2016 at 10:32 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> 1) I think the experiment from paper was run on real testbed which would
> explain the outliers in the RTT.
>
>
> 2) The experiment for blue line is not correct as it also a failure
> experiment. The difference is the number of faces.
>
> For blue line the experiment would be the same as the red line except you
> would run mini-NDN with option --faces 0 (i.e. multipath). For the red line
> you would run with --faces 1 (i.e. single path).
>
>
> Blue line:
>
> sudo minindn --experiment=failureExp --faces 0
>
>
> Red line:
>
> sudo minindn --experiment=failureExp --faces 1
>
>
> 3) I am not sure about the density but the figure on the paper should not
> have more than 200 pings. Maybe the small size of the figure and different
> point size is leading to more observed density.
>
> Another case could be that there are some timeouts in your experiment that
> are not represented on the graphs?
>
>
> Ashlesh
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr
> abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Wednesday, November 23, 2016 4:06:01 PM
> *To:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] topology result
>
> also my experiments codes are:
> for blue points:
>
>
> from ndn.experiments.experiment import Experiment
> from ndn.nlsr import Nlsr
>
> import time
>
> class pingallreg(Experiment):
>
>     def __init__(self, args):
>         args["nPings"] = 200000
>         Experiment.__init__(self, args)
>
>     def run(self):
>         self.startPctPings()
>         time.sleep(200)
>
> Experiment.register("wofail", pingallreg)
>
> and for red points which involve failure:
>
> from ndn.experiments.experiment import Experiment
> from ndn.nlsr import Nlsr
>
> import time
>
> class fail(Experiment):
>
>     def __init__(self, args):
>         args["nPings"] = 140000
>         Experiment.__init__(self, args)
>
>         self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
>         self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20
>
>     def run(self):
>         self.startPctPings()
>
>         # After the pings are scheduled, collect pings for 1 minute
>         time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)
>
>         # Bring down CSU
>         for host in self.net.hosts:
>             if host.name == "node4":
>                 self.failNode(host)
>                 break
>
>         # CSU is down for 2 minutes
>         time.sleep(120)
>
>         # Bring CSU back up
>         for host in self.net.hosts:
>             if host.name == "node4":
>                 self.recoverNode(host)
>
>                 for other in self.net.hosts:
>                     if host.name != other.name:
>                         self.ping(host, other, self.PING_COLLECTION_TIME_
> AFTER_RECOVERY)
>
>         # Collect pings for more seconds after CSU is up
>         time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)
>
> Experiment.register("failone", fail)
>
>
>
> On Thu, Nov 24, 2016 at 1:31 AM, sepehr abdous <sepehrabdous1375 at gmail.com
> > wrote:
>
>> Hello all,
>> I'm new to mini-ndn and I'm trying to implement the following topology
>>
>> [image: Inline image 2]
>> I implemented it with the following information:
>> [image: Inline image 3]
>> and based on the paper the expected results on ping is :
>> [image: Inline image 4]
>> but when I implement it I get the following image
>>
>> [image: Inline image 5]
>> and as you can see there are some problems:
>> (1) the values on the y-axis is much higher than in the paper, I figured
>> out that It's caused by the delay, I set the delay for every link to 20ms
>> so the values are around 80ms but when I set the delay to 0ms the values
>> are around 10ms but the swing of values become more and values are not
>> united like when the delay is 20ms
>> (2) as you can see when node4 fails we have some values that shows
>> something happened:
>> [image: Inline image 6]
>> but this values doesn't exist in my figure.
>> (3) the density of red points in my figure isn't the same in all aspects.
>> can you please help me with this problems.
>> Thank you
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/1372aad0/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/1372aad0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NLSR.jpg
Type: image/jpeg
Size: 24551 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/1372aad0/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(1).png
Type: image/png
Size: 72749 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/1372aad0/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(2).png
Type: image/png
Size: 29814 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/1372aad0/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image(1).png
Type: image/png
Size: 42436 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/1372aad0/attachment-0007.png>

From agawande at memphis.edu  Thu Nov 24 12:38:14 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 24 Nov 2016 20:38:14 +0000
Subject: [Mini-NDN] topology result
In-Reply-To: <CAKaOrigrdCP-fonQzSN-ohA-vWaZNasiwwsJ5XbGA5hqPyistg@mail.gmail.com>
References: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>
	<CAKaOrihiMqb4Ryuo3xSNNZhi06U1-uxxgia+qMzo1SejPPOCoA@mail.gmail.com>
	<BN3PR04MB21965B872501ED9D03ACDF9BD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOrigrdCP-fonQzSN-ohA-vWaZNasiwwsJ5XbGA5hqPyistg@mail.gmail.com>
Message-ID: <BN3PR04MB2196A2E1ADB08DBE448D39DBD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>

Yes run the experiment with different faces. No need to write anything.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Thursday, November 24, 2016 2:27:18 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] topology result

about (2) you mean that I should write the following experiment with different faces?
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class fail(Experiment):

    def __init__(self, args):
        args["nPings"] = 140000
        Experiment.__init__(self, args)

        self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
        self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20

    def run(self):
        self.startPctPings()

        # After the pings are scheduled, collect pings for 1 minute
        time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)

        # Bring down CSU
        for host in self.net.hosts:
            if host.name<http://host.name> == "node4":
                self.failNode(host)
                break

        # CSU is down for 2 minutes
        time.sleep(120)

        # Bring CSU back up
        for host in self.net.hosts:
            if host.name<http://host.name> == "node4":
                self.recoverNode(host)

                for other in self.net.hosts:
                    if host.name<http://host.name> != other.name<http://other.name>:
                        self.ping(host, other, self.PING_COLLECTION_TIME_AFTER_RECOVERY)

        # Collect pings for more seconds after CSU is up
        time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)

Experiment.register("failone", fail)
[https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif]


On Thu, Nov 24, 2016 at 10:32 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

1) I think the experiment from paper was run on real testbed which would explain the outliers in the RTT.


2) The experiment for blue line is not correct as it also a failure experiment. The difference is the number of faces.

For blue line the experiment would be the same as the red line except you would run mini-NDN with option --faces 0 (i.e. multipath). For the red line you would run with --faces 1 (i.e. single path).


Blue line:

sudo minindn --experiment=failureExp --faces 0


Red line:

sudo minindn --experiment=failureExp --faces 1


3) I am not sure about the density but the figure on the paper should not have more than 200 pings. Maybe the small size of the figure and different point size is leading to more observed density.

Another case could be that there are some timeouts in your experiment that are not represented on the graphs?


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Wednesday, November 23, 2016 4:06:01 PM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] topology result

also my experiments codes are:
for blue points:


from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 200000
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

and for red points which involve failure:

from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class fail(Experiment):

    def __init__(self, args):
        args["nPings"] = 140000
        Experiment.__init__(self, args)

        self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
        self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20

    def run(self):
        self.startPctPings()

        # After the pings are scheduled, collect pings for 1 minute
        time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)

        # Bring down CSU
        for host in self.net.hosts:
            if host.name<http://host.name> == "node4":
                self.failNode(host)
                break

        # CSU is down for 2 minutes
        time.sleep(120)

        # Bring CSU back up
        for host in self.net.hosts:
            if host.name<http://host.name> == "node4":
                self.recoverNode(host)

                for other in self.net.hosts:
                    if host.name<http://host.name> != other.name<http://other.name>:
                        self.ping(host, other, self.PING_COLLECTION_TIME_AFTER_RECOVERY)

        # Collect pings for more seconds after CSU is up
        time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)

Experiment.register("failone", fail)



On Thu, Nov 24, 2016 at 1:31 AM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology

[Inline image 2]
I implemented it with the following information:
[Inline image 3]
and based on the paper the expected results on ping is :
[Inline image 4]
but when I implement it I get the following image

[Inline image 5]
and as you can see there are some problems:
(1) the values on the y-axis is much higher than in the paper, I figured out that It's caused by the delay, I set the delay for every link to 20ms so the values are around 80ms but when I set the delay to 0ms the values are around 10ms but the swing of values become more and values are not united like when the delay is 20ms
(2) as you can see when node4 fails we have some values that shows something happened:
[Inline image 6]
but this values doesn't exist in my figure.
(3) the density of red points in my figure isn't the same in all aspects.
can you please help me with this problems.
Thank you



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/37d6b785/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 11179 bytes
Desc: Untitled.png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/37d6b785/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: NLSR.jpg
Type: image/jpeg
Size: 24551 bytes
Desc: NLSR.jpg
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/37d6b785/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(1).png
Type: image/png
Size: 72749 bytes
Desc: Untitled(1).png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/37d6b785/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled(2).png
Type: image/png
Size: 29814 bytes
Desc: Untitled(2).png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/37d6b785/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image(1).png
Type: image/png
Size: 42436 bytes
Desc: image(1).png
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161124/37d6b785/attachment-0007.png>

From lanwang at memphis.edu  Fri Nov 25 13:01:50 2016
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Fri, 25 Nov 2016 21:01:50 +0000
Subject: [Mini-NDN] topology result
In-Reply-To: <BN3PR04MB2196A2E1ADB08DBE448D39DBD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>
	<CAKaOrihiMqb4Ryuo3xSNNZhi06U1-uxxgia+qMzo1SejPPOCoA@mail.gmail.com>
	<BN3PR04MB21965B872501ED9D03ACDF9BD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrigrdCP-fonQzSN-ohA-vWaZNasiwwsJ5XbGA5hqPyistg@mail.gmail.com>
	<BN3PR04MB2196A2E1ADB08DBE448D39DBD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <F3B35504-9F2D-41BA-9377-9D0A6FE08974@memphis.edu>

Also the figure from the paper shows a round trip time of around 5ms so you should set your link delay accordingly to get this RTT (not 20ms as suggested earlier).

Lan

On Nov 24, 2016, at 2:38 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

Yes run the experiment with different faces. No need to write anything.

Ashlesh
________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Thursday, November 24, 2016 2:27:18 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] topology result

about (2) you mean that I should write the following experiment with different faces?
from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class fail(Experiment):

    def __init__(self, args):
        args["nPings"] = 140000
        Experiment.__init__(self, args)

        self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
        self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20

    def run(self):
        self.startPctPings()

        # After the pings are scheduled, collect pings for 1 minute
        time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)

        # Bring down CSU
        for host in self.net.hosts:
            if host.name<http://host.name/> == "node4":
                self.failNode(host)
                break

        # CSU is down for 2 minutes
        time.sleep(120)

        # Bring CSU back up
        for host in self.net.hosts:
            if host.name<http://host.name/> == "node4":
                self.recoverNode(host)

                for other in self.net.hosts:
                    if host.name<http://host.name/> != other.name<http://other.name/>:
                        self.ping(host, other, self.PING_COLLECTION_TIME_AFTER_RECOVERY)

        # Collect pings for more seconds after CSU is up
        time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)

Experiment.register("failone", fail)
[https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif]


On Thu, Nov 24, 2016 at 10:32 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:
1) I think the experiment from paper was run on real testbed which would explain the outliers in the RTT.

2) The experiment for blue line is not correct as it also a failure experiment. The difference is the number of faces.
For blue line the experiment would be the same as the red line except you would run mini-NDN with option --faces 0 (i.e. multipath). For the red line you would run with --faces 1 (i.e. single path).

Blue line:
sudo minindn --experiment=failureExp --faces 0

Red line:
sudo minindn --experiment=failureExp --faces 1

3) I am not sure about the density but the figure on the paper should not have more than 200 pings. Maybe the small size of the figure and different point size is leading to more observed density.
Another case could be that there are some timeouts in your experiment that are not represented on the graphs?

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Wednesday, November 23, 2016 4:06:01 PM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: Re: [Mini-NDN] topology result

also my experiments codes are:
for blue points:


from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class pingallreg(Experiment):

    def __init__(self, args):
        args["nPings"] = 200000
        Experiment.__init__(self, args)

    def run(self):
        self.startPctPings()
        time.sleep(200)

Experiment.register("wofail", pingallreg)

and for red points which involve failure:

from ndn.experiments.experiment import Experiment
from ndn.nlsr import Nlsr

import time

class fail(Experiment):

    def __init__(self, args):
        args["nPings"] = 140000
        Experiment.__init__(self, args)

        self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
        self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20

    def run(self):
        self.startPctPings()

        # After the pings are scheduled, collect pings for 1 minute
        time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)

        # Bring down CSU
        for host in self.net.hosts:
            if host.name<http://host.name/> == "node4":
                self.failNode(host)
                break

        # CSU is down for 2 minutes
        time.sleep(120)

        # Bring CSU back up
        for host in self.net.hosts:
            if host.name<http://host.name/> == "node4":
                self.recoverNode(host)

                for other in self.net.hosts:
                    if host.name<http://host.name/> != other.name<http://other.name/>:
                        self.ping(host, other, self.PING_COLLECTION_TIME_AFTER_RECOVERY)

        # Collect pings for more seconds after CSU is up
        time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)

Experiment.register("failone", fail)



On Thu, Nov 24, 2016 at 1:31 AM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
Hello all,
I'm new to mini-ndn and I'm trying to implement the following topology

<Untitled.png>
I implemented it with the following information:
<Untitled(1).png>
and based on the paper the expected results on ping is :
<Untitled(2).png>
but when I implement it I get the following image

<image(1).png>
and as you can see there are some problems:
(1) the values on the y-axis is much higher than in the paper, I figured out that It's caused by the delay, I set the delay for every link to 20ms so the values are around 80ms but when I set the delay to 0ms the values are around 10ms but the swing of values become more and values are not united like when the delay is 20ms
(2) as you can see when node4 fails we have some values that shows something happened:
<NLSR.jpg>
but this values doesn't exist in my figure.
(3) the density of red points in my figure isn't the same in all aspects.
can you please help me with this problems.
Thank you



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran



--
Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn

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

From sepehrabdous1375 at gmail.com  Fri Nov 25 13:14:48 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sat, 26 Nov 2016 00:44:48 +0330
Subject: [Mini-NDN] topology result
In-Reply-To: <F3B35504-9F2D-41BA-9377-9D0A6FE08974@memphis.edu>
References: <CAKaOrii9g+UrJHVjkg17ZkdnOnG4gU9g3WgHYNcCWqY=ifmkCg@mail.gmail.com>
	<CAKaOrihiMqb4Ryuo3xSNNZhi06U1-uxxgia+qMzo1SejPPOCoA@mail.gmail.com>
	<BN3PR04MB21965B872501ED9D03ACDF9BD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrigrdCP-fonQzSN-ohA-vWaZNasiwwsJ5XbGA5hqPyistg@mail.gmail.com>
	<BN3PR04MB2196A2E1ADB08DBE448D39DBD9B60@BN3PR04MB2196.namprd04.prod.outlook.com>
	<F3B35504-9F2D-41BA-9377-9D0A6FE08974@memphis.edu>
Message-ID: <CAKaOrijmX1Ny6L4uSYbchoNburYzuJmg2FVmi8Jg1=5iFT8B_g@mail.gmail.com>

Thank you very much

On Sat, Nov 26, 2016 at 12:31 AM, Lan Wang (lanwang) <lanwang at memphis.edu>
wrote:

> Also the figure from the paper shows a round trip time of around 5ms so
> you should set your link delay accordingly to get this RTT (not 20ms as
> suggested earlier).
>
> Lan
>
> On Nov 24, 2016, at 2:38 PM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
> Yes *run *the experiment with different faces. No need to write anything.
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Thursday, November 24, 2016 2:27:18 PM
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] topology result
>
> about (2) you mean that I should write the following experiment with
> different faces?
> from ndn.experiments.experiment import Experiment
> from ndn.nlsr import Nlsr
>
> import time
>
> class fail(Experiment):
>
>     def __init__(self, args):
>         args["nPings"] = 140000
>         Experiment.__init__(self, args)
>
>         self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
>         self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20
>
>     def run(self):
>         self.startPctPings()
>
>         # After the pings are scheduled, collect pings for 1 minute
>         time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)
>
>         # Bring down CSU
>         for host in self.net.hosts:
>             if host.name == "node4":
>                 self.failNode(host)
>                 break
>
>         # CSU is down for 2 minutes
>         time.sleep(120)
>
>         # Bring CSU back up
>         for host in self.net.hosts:
>             if host.name == "node4":
>                 self.recoverNode(host)
>
>                 for other in self.net.hosts:
>                     if host.name != other.name:
>                         self.ping(host, other,
> self.PING_COLLECTION_TIME_AFTER_RECOVERY)
>
>         # Collect pings for more seconds after CSU is up
>         time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)
>
> Experiment.register("failone", fail)
>
>
> On Thu, Nov 24, 2016 at 10:32 AM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> 1) I think the experiment from paper was run on real testbed which would
>> explain the outliers in the RTT.
>>
>> 2) The experiment for blue line is not correct as it also a failure
>> experiment. The difference is the number of faces.
>> For blue line the experiment would be the same as the red line except you
>> would run mini-NDN with option --faces 0 (i.e. multipath). For the red line
>> you would run with --faces 1 (i.e. single path).
>>
>> Blue line:
>> sudo minindn --experiment=failureExp --faces 0
>>
>> Red line:
>> sudo minindn --experiment=failureExp --faces 1
>>
>> 3) I am not sure about the density but the figure on the paper should not
>> have more than 200 pings. Maybe the small size of the figure and different
>> point size is leading to more observed density.
>> Another case could be that there are some timeouts in your experiment
>> that are not represented on the graphs?
>>
>> Ashlesh
>> ------------------------------
>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>> sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Wednesday, November 23, 2016 4:06:01 PM
>> *To:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* Re: [Mini-NDN] topology result
>>
>> also my experiments codes are:
>> for blue points:
>>
>>
>> from ndn.experiments.experiment import Experiment
>> from ndn.nlsr import Nlsr
>>
>> import time
>>
>> class pingallreg(Experiment):
>>
>>     def __init__(self, args):
>>         args["nPings"] = 200000
>>         Experiment.__init__(self, args)
>>
>>     def run(self):
>>         self.startPctPings()
>>         time.sleep(200)
>>
>> Experiment.register("wofail", pingallreg)
>>
>> and for red points which involve failure:
>>
>> from ndn.experiments.experiment import Experiment
>> from ndn.nlsr import Nlsr
>>
>> import time
>>
>> class fail(Experiment):
>>
>>     def __init__(self, args):
>>         args["nPings"] = 140000
>>         Experiment.__init__(self, args)
>>
>>         self.PING_COLLECTION_TIME_BEFORE_FAILURE = 60
>>         self.PING_COLLECTION_TIME_AFTER_RECOVERY = 20
>>
>>     def run(self):
>>         self.startPctPings()
>>
>>         # After the pings are scheduled, collect pings for 1 minute
>>         time.sleep(self.PING_COLLECTION_TIME_BEFORE_FAILURE)
>>
>>         # Bring down CSU
>>         for host in self.net.hosts:
>>             if host.name == "node4":
>>                 self.failNode(host)
>>                 break
>>
>>         # CSU is down for 2 minutes
>>         time.sleep(120)
>>
>>         # Bring CSU back up
>>         for host in self.net.hosts:
>>             if host.name == "node4":
>>                 self.recoverNode(host)
>>
>>                 for other in self.net.hosts:
>>                     if host.name != other.name:
>>                         self.ping(host, other,
>> self.PING_COLLECTION_TIME_AFTER_RECOVERY)
>>
>>         # Collect pings for more seconds after CSU is up
>>         time.sleep(self.PING_COLLECTION_TIME_AFTER_RECOVERY)
>>
>> Experiment.register("failone", fail)
>>
>>
>>
>> On Thu, Nov 24, 2016 at 1:31 AM, sepehr abdous <sepehrabdous1375@
>> gmail.com> wrote:
>>
>>> Hello all,
>>> I'm new to mini-ndn and I'm trying to implement the following topology
>>>
>>> <Untitled.png>
>>> I implemented it with the following information:
>>> <Untitled(1).png>
>>> and based on the paper the expected results on ping is :
>>> <Untitled(2).png>
>>> but when I implement it I get the following image
>>>
>>> <image(1).png>
>>> and as you can see there are some problems:
>>> (1) the values on the y-axis is much higher than in the paper, I figured
>>> out that It's caused by the delay, I set the delay for every link to 20ms
>>> so the values are around 80ms but when I set the delay to 0ms the values
>>> are around 10ms but the swing of values become more and values are not
>>> united like when the delay is 20ms
>>> (2) as you can see when node4 fails we have some values that shows
>>> something happened:
>>> <NLSR.jpg>
>>> but this values doesn't exist in my figure.
>>> (3) the density of red points in my figure isn't the same in all aspects.
>>> can you please help me with this problems.
>>> Thank you
>>>
>>
>>
>>
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
>
>


-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161126/2bc740b0/attachment-0001.html>

From sepehrabdous1375 at gmail.com  Mon Nov 28 16:14:06 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 29 Nov 2016 03:44:06 +0330
Subject: [Mini-NDN] convergence time
Message-ID: <CAKaOriiYFAtrSKWJEVGRHH0HzDWvw7dRMgAHzcwkopOM6FAJfA@mail.gmail.com>

Hello all,
I'm trying to implement the following topology with the information bellow:
[image: Inline image 1]
[image: Inline image 2]
and the expected result is:
[image: Inline image 3]
but when I used the experiment which will be added bellow I got the
following result:
[image: Inline image 4]
and I have 2 questions:
(1) why the convergence takes 20 pings while it's expected to take 60 pings
while I set ctime=60?
(2)why does the last 20 pings still about 60 ms while they're expected to
be about 40 ms like the first 60 pings?

the experiment that caused the figure above is:


class test(CustomExperiment):

    def __init__(self, args):
        self.pctTraffic = float(args["pctTraffic"])
        print "Using %f traffic" % self.pctTraffic
        self.nFaces = int(input())
        print "number of faces is %f" %self.nFaces
        if self.nFaces==0:
            args["nPings"] = 1000
        if self.nFaces==1:
            args["nPings"] = 700
        self.strategy = args["strategy"]
        print self.strategy
        CustomExperiment.__init__(self, args)

    def run(self):
        self.startPctPings("node2","node6")

        time.sleep(60)

        for host in self.net.hosts:
            if host.name == "node4":
                self.failNode(host)
                break

        if self.nFaces==1:
            print "Waiting " + str(self.convergenceTime) + " seconds for
convergence..."
            time.sleep(self.convergenceTime)
            print "...done"

            # To check whether all the nodes of NLSR have converged
            didNlsrConverge = True

            # Checking for convergence
            for host in self.net.hosts:
                if host.name=="node2":
                    statusRouter = host.cmd("nfd-status -b | grep
/ndn/edu/%C1.Router/cs/")
                    statusPrefix = host.cmd("nfd-status -b | grep
/ndn/edu/")
                    didNodeConverge = True
                    for node in self.nodes.split(","):
                        # print node
                        if node!="node4":
                            if ("/ndn/edu/%C1.Router/cs/" + node) not in
statusRouter:
                                print "fuck"
                                didNodeConverge = False
                                didNlsrConverge = False
                            if str(host) != node and ("/ndn/edu/" + node)
not in statusPrefix:
                                print"fuck2"
                                didNodeConverge = False
                                didNlsrConverge = False

                    host.cmd("echo " + str(didNodeConverge) + " >
convergence-result &")

            if didNlsrConverge:
                print("NLSR has successfully converged.")
            else:
                print("NLSR has not converged. Exiting...")
                self.net.stop()
                self.sys.exit(1)
            time.sleep(60)

            # time.sleep(120)

        else:
            time.sleep(120)

        for host in self.net.hosts:
            if host.name == "node4":
                self.recoverNode(host)

        time.sleep(20)

CustomExperiment.register("test", test)

Thank you
--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161129/57445fc9/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot from 2016-11-08 03-29-33.png
Type: image/png
Size: 9131 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161129/57445fc9/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Untitled.png
Type: image/png
Size: 57075 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161129/57445fc9/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 2.png
Type: image/png
Size: 87851 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161129/57445fc9/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image(2).png
Type: image/png
Size: 43870 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161129/57445fc9/attachment-0007.png>

From lanwang at memphis.edu  Tue Nov 29 12:54:31 2016
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Tue, 29 Nov 2016 20:54:31 +0000
Subject: [Mini-NDN] convergence time
In-Reply-To: <CAKaOriiYFAtrSKWJEVGRHH0HzDWvw7dRMgAHzcwkopOM6FAJfA@mail.gmail.com>
References: <CAKaOriiYFAtrSKWJEVGRHH0HzDWvw7dRMgAHzcwkopOM6FAJfA@mail.gmail.com>
Message-ID: <B9BCB0F1-2FDF-4157-A6A7-0B31B50085E3@memphis.edu>

The original experiment was done with our first NLSR implementation on CCND.  The codebase has been completely changed for NLSR, NFD and ndn-cxx so it?s difficult to know exactly what part contributed to the difference.  One suggestion I have is to run the experiment longer to see if there?s any switching back to the lower cost path.  My suspicion is something in the best-route strategy that?s preventing the switching back in a timely manner.

Nick: could you repeat the experiment and investigate what might be the problem?  Thanks.

Lan

On Nov 28, 2016, at 6:14 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:

Hello all,
I'm trying to implement the following topology with the information bellow:
<Screenshot from 2016-11-08 03-29-33.png>
<2.png>
and the expected result is:
<Untitled.png>
but when I used the experiment which will be added bellow I got the following result:
<image(2).png>
and I have 2 questions:
(1) why the convergence takes 20 pings while it's expected to take 60 pings while I set ctime=60?
(2)why does the last 20 pings still about 60 ms while they're expected to be about 40 ms like the first 60 pings?

the experiment that caused the figure above is:


class test(CustomExperiment):

    def __init__(self, args):
        self.pctTraffic = float(args["pctTraffic"])
        print "Using %f traffic" % self.pctTraffic
        self.nFaces = int(input())
        print "number of faces is %f" %self.nFaces
        if self.nFaces==0:
            args["nPings"] = 1000
        if self.nFaces==1:
            args["nPings"] = 700
        self.strategy = args["strategy"]
        print self.strategy
        CustomExperiment.__init__(self, args)

    def run(self):
        self.startPctPings("node2","node6")

        time.sleep(60)

        for host in self.net.hosts:
            if host.name<http://host.name/> == "node4":
                self.failNode(host)
                break

        if self.nFaces==1:
            print "Waiting " + str(self.convergenceTime) + " seconds for convergence..."
            time.sleep(self.convergenceTime)
            print "...done"

            # To check whether all the nodes of NLSR have converged
            didNlsrConverge = True

            # Checking for convergence
            for host in self.net.hosts:
                if host.name<http://host.name/>=="node2":
                    statusRouter = host.cmd("nfd-status -b | grep /ndn/edu/%C1.Router/cs/")
                    statusPrefix = host.cmd("nfd-status -b | grep /ndn/edu/")
                    didNodeConverge = True
                    for node in self.nodes.split(","):
                        # print node
                        if node!="node4":
                            if ("/ndn/edu/%C1.Router/cs/" + node) not in statusRouter:
                                print "fuck"
                                didNodeConverge = False
                                didNlsrConverge = False
                            if str(host) != node and ("/ndn/edu/" + node) not in statusPrefix:
                                print"fuck2"
                                didNodeConverge = False
                                didNlsrConverge = False

                    host.cmd("echo " + str(didNodeConverge) + " > convergence-result &")

            if didNlsrConverge:
                print("NLSR has successfully converged.")
            else:
                print("NLSR has not converged. Exiting...")
                self.net.stop()
                self.sys.exit(1)
            time.sleep(60)

            # time.sleep(120)

        else:
            time.sleep(120)

        for host in self.net.hosts:
            if host.name<http://host.name/> == "node4":
                self.recoverNode(host)

        time.sleep(20)

CustomExperiment.register("test", test)

Thank you
--

_______________________________________________
Mini-NDN mailing list
Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn

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

From sepehrabdous1375 at gmail.com  Wed Nov 30 00:17:14 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Wed, 30 Nov 2016 11:47:14 +0330
Subject: [Mini-NDN] convergence time
In-Reply-To: <B9BCB0F1-2FDF-4157-A6A7-0B31B50085E3@memphis.edu>
References: <CAKaOriiYFAtrSKWJEVGRHH0HzDWvw7dRMgAHzcwkopOM6FAJfA@mail.gmail.com>
	<B9BCB0F1-2FDF-4157-A6A7-0B31B50085E3@memphis.edu>
Message-ID: <CAKaOrigyzcu75M572PF2QFRzwL5C6CfCA_W0eA8C0=oEbBiDrw@mail.gmail.com>

Thank you very much for your help
I changed the time to 280 seconds and now the red points at the end become
is OK
[image: Inline image 1]
but I still have got problem with convergence time in red points.
as you can see in the paper it is about 60 pings but for my experiment it's
20.
what can cause this problem?

On Wed, Nov 30, 2016 at 12:24 AM, Lan Wang (lanwang) <lanwang at memphis.edu>
wrote:

> The original experiment was done with our first NLSR implementation on
> CCND.  The codebase has been completely changed for NLSR, NFD and ndn-cxx
> so it?s difficult to know exactly what part contributed to the difference.
> One suggestion I have is to run the experiment longer to see if there?s any
> switching back to the lower cost path.  My suspicion is something in the
> best-route strategy that?s preventing the switching back in a timely
> manner.
>
> Nick: could you repeat the experiment and investigate what might be the
> problem?  Thanks.
>
> Lan
>
> On Nov 28, 2016, at 6:14 PM, sepehr abdous <sepehrabdous1375 at gmail.com>
> wrote:
>
> Hello all,
> I'm trying to implement the following topology with the information bellow:
> <Screenshot from 2016-11-08 03-29-33.png>
> <2.png>
> and the expected result is:
> <Untitled.png>
> but when I used the experiment which will be added bellow I got the
> following result:
> <image(2).png>
> and I have 2 questions:
> (1) why the convergence takes 20 pings while it's expected to take 60
> pings while I set ctime=60?
> (2)why does the last 20 pings still about 60 ms while they're expected to
> be about 40 ms like the first 60 pings?
>
> the experiment that caused the figure above is:
>
>
> class test(CustomExperiment):
>
>     def __init__(self, args):
>         self.pctTraffic = float(args["pctTraffic"])
>         print "Using %f traffic" % self.pctTraffic
>         self.nFaces = int(input())
>         print "number of faces is %f" %self.nFaces
>         if self.nFaces==0:
>             args["nPings"] = 1000
>         if self.nFaces==1:
>             args["nPings"] = 700
>         self.strategy = args["strategy"]
>         print self.strategy
>         CustomExperiment.__init__(self, args)
>
>     def run(self):
>         self.startPctPings("node2","node6")
>
>         time.sleep(60)
>
>         for host in self.net.hosts:
>             if host.name == "node4":
>                 self.failNode(host)
>                 break
>
>         if self.nFaces==1:
>             print "Waiting " + str(self.convergenceTime) + " seconds for
> convergence..."
>             time.sleep(self.convergenceTime)
>             print "...done"
>
>             # To check whether all the nodes of NLSR have converged
>             didNlsrConverge = True
>
>             # Checking for convergence
>             for host in self.net.hosts:
>                 if host.name=="node2":
>                     statusRouter = host.cmd("nfd-status -b | grep
> /ndn/edu/%C1.Router/cs/")
>                     statusPrefix = host.cmd("nfd-status -b | grep
> /ndn/edu/")
>                     didNodeConverge = True
>                     for node in self.nodes.split(","):
>                         # print node
>                         if node!="node4":
>                             if ("/ndn/edu/%C1.Router/cs/" + node) not in
> statusRouter:
>                                 print "fuck"
>                                 didNodeConverge = False
>                                 didNlsrConverge = False
>                             if str(host) != node and ("/ndn/edu/" + node)
> not in statusPrefix:
>                                 print"fuck2"
>                                 didNodeConverge = False
>                                 didNlsrConverge = False
>
>                     host.cmd("echo " + str(didNodeConverge) + " >
> convergence-result &")
>
>             if didNlsrConverge:
>                 print("NLSR has successfully converged.")
>             else:
>                 print("NLSR has not converged. Exiting...")
>                 self.net.stop()
>                 self.sys.exit(1)
>             time.sleep(60)
>
>             # time.sleep(120)
>
>         else:
>             time.sleep(120)
>
>         for host in self.net.hosts:
>             if host.name == "node4":
>                 self.recoverNode(host)
>
>         time.sleep(20)
>
> CustomExperiment.register("test", test)
>
> Thank you
> --
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
>
>


-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161130/7e4fea6a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 42497 bytes
Desc: not available
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161130/7e4fea6a/attachment-0001.png>

From sepehrabdous1375 at gmail.com  Wed Nov 30 15:27:19 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Thu, 1 Dec 2016 02:57:19 +0330
Subject: [Mini-NDN] convergence time
In-Reply-To: <31166f32-0868-89bc-dabd-e8ac5babae0a@memphis.edu>
References: <CAKaOriiYFAtrSKWJEVGRHH0HzDWvw7dRMgAHzcwkopOM6FAJfA@mail.gmail.com>
	<B9BCB0F1-2FDF-4157-A6A7-0B31B50085E3@memphis.edu>
	<CAKaOrigyzcu75M572PF2QFRzwL5C6CfCA_W0eA8C0=oEbBiDrw@mail.gmail.com>
	<31166f32-0868-89bc-dabd-e8ac5babae0a@memphis.edu>
Message-ID: <CAKaOrijwW54JLeOvgxjk86ArgdyGDqzwb2TiAsM0_toNe4ak6w@mail.gmail.com>

Thank you for your response

about (2) as I'm working with mini-ndn, mini-ndn creates nlsr itself based
on the minindn.conf and I do not exactly know how to change minindn.conf so
that in nlsr.conf created by running minindn we have the hello interval of
15 as it's default value is 60.

here is my minindn.conf:

[nodes]
node4: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node4 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node6: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node6 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node1: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node1 site=/edu/site nlsr-log-level=NONE
max-faces-per-prefix=0 nfd-log-level=NONE
node2: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node2 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node5: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node5 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
node3: _ hyperbolic-state=off radius=0.0 angle=0.0 network=/ndn
router=/%C1.Router/cs/node3 site=/edu/site nlsr-log-level=INFO
max-faces-per-prefix=0 nfd-log-level=INFO
[switches]
[links]
node1:node2 delay=10ms
node1:node3 delay=10ms
node3:node5 delay=10ms
node5:node6 delay=10ms
node6:node4 delay=10ms
node4:node2 delay=10ms
node3:node4 delay=10ms
node3:node6 delay=10ms


On Wed, Nov 30, 2016 at 8:45 PM, Nick Gordon <nmgordon at memphis.edu> wrote:

> Here are my thoughts:
>
> 1. Ctime I think does something different than you expect it does. Ctime
> controls how long miniNDN waits at starting before checking for
> convergence. It is not used after this initial phase.
>
> 2. Try changing the hello interval in nlsr.conf and see if that changes
> the gap. That will give us more information. Additionally, try tweaking
> the wait time in mini-ndn between NFD starts. (minindn/ndn/nfd.py).
> Finally, try running the experiments with minindn using a ramdisk as a
> working directory, if you can spare the RAM. A suitable ramdisk for this
> topology could be as small as 1GB.
>
> -Nick
>
>
>


-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161201/1cc17e9c/attachment.html>