From Matteo.Bertolino at eurecom.fr  Thu Dec  1 01:11:20 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Thu, 01 Dec 2016 10:11:20 +0100
Subject: [Mini-NDN] An advice about stopping mini
Message-ID: <20161201101120.hyu3c2nyg40g48gs@webmail.eurecom.fr>

Good morning,
I suggest to change a bit the minindn script.
In my opinion sometimes it could be confortable stopping an  
application running on mini without stopping mini.
Then, ctrl+c stops both.

I edited the minindn script letting the signal handler managing a  
SIGQUIT instead of a SIGKILL. ( signal.signal(signal.SIGQUIT,  
signal_handler)  )

Then with ctrl+c the application, like the ndnpingserver, is stopped.
With ctrl+\ minindn exit in a clean way.

matteo

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


From lanwang at memphis.edu  Thu Dec  1 07:42:37 2016
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Thu, 1 Dec 2016 15:42:37 +0000
Subject: [Mini-NDN] Fwd:  convergence time
References: <CAKaOrijwW54JLeOvgxjk86ArgdyGDqzwb2TiAsM0_toNe4ak6w@mail.gmail.com>
Message-ID: <89325589-F9EB-470B-B52F-2F01343FC130@memphis.edu>

sending the message again as it was bounced.

Lan

Begin forwarded message:

From: sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Subject: Re: [Mini-NDN] convergence time
Date: November 30, 2016 at 5:27:19 PM CST
To: Nick Gordon <nmgordon at memphis.edu<mailto:nmgordon at memphis.edu>>
Cc: "Lan Wang (lanwang)" <lanwang at memphis.edu<mailto:lanwang at memphis.edu>>, "mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>" <mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>>

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<mailto: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<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/20161201/9f71f23e/attachment-0001.html>

From agawande at memphis.edu  Thu Dec  1 10:53:13 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 1 Dec 2016 18:53:13 +0000
Subject: [Mini-NDN] An advice about stopping mini
In-Reply-To: <20161201101120.hyu3c2nyg40g48gs@webmail.eurecom.fr>
References: <20161201101120.hyu3c2nyg40g48gs@webmail.eurecom.fr>
Message-ID: <BN3PR04MB219679D2F5250B04B53C44DBD98F0@BN3PR04MB2196.namprd04.prod.outlook.com>

Agreed, thanks. I will push a patch.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Thursday, December 1, 2016 3:11:20 AM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] An advice about stopping mini

Good morning,
I suggest to change a bit the minindn script.
In my opinion sometimes it could be confortable stopping an
application running on mini without stopping mini.
Then, ctrl+c stops both.

I edited the minindn script letting the signal handler managing a
SIGQUIT instead of a SIGKILL. ( signal.signal(signal.SIGQUIT,
signal_handler)  )

Then with ctrl+c the application, like the ndnpingserver, is stopped.
With ctrl+\ minindn exit in a clean way.

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/20161201/2c91de95/attachment.html>

From agawande at memphis.edu  Thu Dec  1 11:03:30 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 1 Dec 2016 19:03:30 +0000
Subject: [Mini-NDN] An advice about stopping mini
In-Reply-To: <BN3PR04MB219679D2F5250B04B53C44DBD98F0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <20161201101120.hyu3c2nyg40g48gs@webmail.eurecom.fr>,
	<BN3PR04MB219679D2F5250B04B53C44DBD98F0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <BN3PR04MB21969DA37F78A01235B6A52AD98F0@BN3PR04MB2196.namprd04.prod.outlook.com>

Actually, doesn't doing control + c kills NFD for you, because it does for me?


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu>
Sent: Thursday, December 1, 2016 12:53:13 PM
To: Matteo Bertolino; mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] An advice about stopping mini


Agreed, thanks. I will push a patch.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Thursday, December 1, 2016 3:11:20 AM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] An advice about stopping mini

Good morning,
I suggest to change a bit the minindn script.
In my opinion sometimes it could be confortable stopping an
application running on mini without stopping mini.
Then, ctrl+c stops both.

I edited the minindn script letting the signal handler managing a
SIGQUIT instead of a SIGKILL. ( signal.signal(signal.SIGQUIT,
signal_handler)  )

Then with ctrl+c the application, like the ndnpingserver, is stopped.
With ctrl+\ minindn exit in a clean way.

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/20161201/cb6515ea/attachment.html>

From Matteo.Bertolino at eurecom.fr  Fri Dec  2 04:48:41 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Fri, 02 Dec 2016 13:48:41 +0100
Subject: [Mini-NDN] An advice about stopping mini
In-Reply-To: <BN3PR04MB21969DA37F78A01235B6A52AD98F0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <20161201101120.hyu3c2nyg40g48gs@webmail.eurecom.fr>,
	<BN3PR04MB219679D2F5250B04B53C44DBD98F0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<BN3PR04MB21969DA37F78A01235B6A52AD98F0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <20161202134841.u1b9dql92cg8kggo@webmail.eurecom.fr>

Dear Ashlesh, actually I don't understand the question.
This is my behaviour:

Without patch:
mininet> node ndnping /prefix
... content from ...
... content from ...
... content from ...
CTRL+C
Exit mininet in a clean way (exit from nfd etc)
user$


With the modification:
mininet> node ndnping /prefix
... content from ...
... content from ...
... content from ...
CTRL+C
mininet> node ndnping /prefix
... content from ...
... content from ...
CTRL + \
Exit mininet in a clean way (exit from nfd etc)
user$

I hope that I answer to your question.

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

> Actually, doesn't doing control + c kills NFD for you, because it   
> does for me?
>
>
> Ashlesh
>
> ________________________________
> From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of   
> Ashlesh Gawande (agawande) <agawande at memphis.edu>
> Sent: Thursday, December 1, 2016 12:53:13 PM
> To: Matteo Bertolino; mini-ndn at lists.cs.ucla.edu
> Subject: Re: [Mini-NDN] An advice about stopping mini
>
>
> Agreed, thanks. I will push a patch.
>
>
> Ashlesh
>
> ________________________________
> From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of   
> Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
> Sent: Thursday, December 1, 2016 3:11:20 AM
> To: mini-ndn at lists.cs.ucla.edu
> Subject: [Mini-NDN] An advice about stopping mini
>
> Good morning,
> I suggest to change a bit the minindn script.
> In my opinion sometimes it could be confortable stopping an
> application running on mini without stopping mini.
> Then, ctrl+c stops both.
>
> I edited the minindn script letting the signal handler managing a
> SIGQUIT instead of a SIGKILL. ( signal.signal(signal.SIGQUIT,
> signal_handler)  )
>
> Then with ctrl+c the application, like the ndnpingserver, is stopped.
> With ctrl+\ minindn exit in a clean way.
>
> 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 agawande at memphis.edu  Fri Dec  2 08:13:29 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 2 Dec 2016 16:13:29 +0000
Subject: [Mini-NDN] [Ndn-interest] Launching several instances of nlsr
In-Reply-To: <DEDC4725-E314-4056-A29E-37BA5294BED6@memphis.edu>
References: <20161202153816.rd41nmdrc48oosgs@webmail.eurecom.fr>
	<CAO9+PG-kb+hc7J=Pu7k8a=fXvM22qSKjO7X95FPCLG5uF+QsOw@mail.gmail.com>
	<20161202164102.1fzq7cbmswo0kw8g@webmail.eurecom.fr>,
	<DEDC4725-E314-4056-A29E-37BA5294BED6@memphis.edu>
Message-ID: <BN3PR04MB2196A92F68E872BF8A088474D98E0@BN3PR04MB2196.namprd04.prod.outlook.com>

Mininet provides virtual ethernet pairs in networked namespaces. So each node provided by Mininet have a network stack. That is why NLSR can be configured with IPs of neighboring nodes.


You can create your own network namespaces, but why not use Mininet?

If you want to anyway - I would suggest to see how exactly Mininet does it.


Do these NLSR have the same log file, what does the neighbor section look like?


Ashlesh

________________________________
From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of Lan Wang (lanwang) <lanwang at memphis.edu>
Sent: Friday, December 2, 2016 9:48:03 AM
To: Matteo Bertolino
Cc: ndn-interest at lists.cs.ucla.edu
Subject: Re: [Ndn-interest] Launching several instances of nlsr

Why do you want to run multiple instances of NLSR on one node without mini-NDN?

Lan

> On Dec 2, 2016, at 9:41 AM, Matteo Bertolino <Matteo.Bertolino at eurecom.fr> wrote:
>
> Dear Cesar,
> thanks for the answer. Actually I did it, with linux namespaces.
> I am convinced that nlsr is the problem, because I compared two FIB in this topology: node1, node2 both attached to nodeGW.
>
> FIB of node1 in MINI: (just first line)
> /ndn/NLSR/sync nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
>
> FIB of node1 without MINI: (just first line)
> /ndn/NLSR/sync nexthops={faceid=263 (cost=0), faceid=265 (cost=0), faceid=266 (cost=0), faceid=264 (cost=10), faceid=267 (cost=10), faceid=268 (cost=10)}
>
> 6 entries vs 2. Then the NLSR instances are actually "together"!
>
>
> Quoting "C?sar A. Bernardini" <mesarpe at gmail.com>:
>
>> I don't remember the parameters of nslr . Maybe the thing you could try is
>> to create tap devices in Linux and attach the app to this fake interfaces.
>> I remember I did this three years ago.
>>
>> Bests,
>>
>> On Dec 2, 2016 15:40, "Matteo Bertolino" <Matteo.Bertolino at eurecom.fr>
>> wrote:
>>
>>> Good morning, I need to perform a complicate question.
>>> I would like to launch several NDN nodes in different processes (i.e. 3
>>> processes) on the same machine. Exactly the same behaviour of mini-ndn, but
>>> without.
>>> Then, about the NFD I had no problem:
>>> 1- Open three terminals.
>>> 2- On each terminal, change the HOME environment variable.
>>> 3- Put on the new home a new nfd.conf, changing the socket name (nfd.sock,
>>> nfd1.sock, nfd2.sock), the port numbers, and repeat in the
>>> client.config.sample.
>>> 4- On each terminal, launch nfd --config ~/nfd.conf &
>>>
>>> It works well. The problem arrives with NLSR.
>>> In each HOME, I put a different version of nlsr.conf, where I changed the
>>> names and the ip of the neighborhoods.
>>> Then I run on each node nlsr -d -f  ~/nlsr.conf
>>>
>>> And here I noticed a strange thing: all the output, nlsr related,
>>> converges in one terminal. So I started to think that actually there are
>>> not 3 separated nlsr instances despite the three different processes.
>>> If I try to do nlsrc advertise /prefix , it tells me "success in
>>> advertisement", but no FIBS are actually updated. This demonstrate that the
>>> three instances are actually one.
>>>
>>> But, however, mini obtains a perfect separation. I tried to replicate
>>> exactly the same steps in nlsr.py, but I have no success. In your opinion,
>>> what do I forgot ? Thanks
>>>
>>> ------------------------------------------------------------
>>> -------------------
>>> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>>>
>>>
>>> _______________________________________________
>>> Ndn-interest mailing list
>>> Ndn-interest at lists.cs.ucla.edu
>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>>
>>
>
>
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest


_______________________________________________
Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu
http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161202/c55e6c48/attachment-0001.html>

From sepehrabdous1375 at gmail.com  Fri Dec  2 14:02:23 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sat, 3 Dec 2016 01:32:23 +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: <CAKaOrigsP=8G+vn4d+Fm950q35orucdB6y8tQ-ZoVaS6VpweOA@mail.gmail.com>

I changed nlsr.py file so that the following lines are included in every
nodes nlsr.conf file:

  hello-interval 15
  hello-retries 3
  hello-timeout 4

I ran the experiment but the results stood the same then I tried changing
the numbers but even changing them wasn't helpful

and then I changed the wait time between NFD starts, but the result is
still the same.
can you please tell me how can I us a ramdisk as my directory?

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/20161203/59353f7f/attachment.html>

From nou.mail at gmail.com  Wed Dec 21 12:26:24 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Wed, 21 Dec 2016 21:26:24 +0100
Subject: [Mini-NDN] Richer experiment example
In-Reply-To: <CAJ8opn1jjx6OQjztZPKY6XbjvjVyECP5K4_EGy7iwR33YWG7xQ@mail.gmail.com>
References: <CAJ8opn1jjx6OQjztZPKY6XbjvjVyECP5K4_EGy7iwR33YWG7xQ@mail.gmail.com>
Message-ID: <CAJ8opn0YfpiRm+fim2=Yjak5SCV9GUU0aOj9arTPuzELdh7Z_g@mail.gmail.com>

Dear community

I'm new with mini ndn
Fortunately installation went fine
I would like now to write an experiment with many data flows between my
topology nodes using producers and consumers

Documentation does not really help since only ndnping is showed

Is there any richer experiment example or tutorial ?

My second question is How's to collect metrics once the emulation done ?

Best regards

On Dec 21, 2016 6:45 PM, "Nour El Houda Ben Youssef" <nou.mail at gmail.com>
wrote:

> Dear community
>
> I'm new with mini ndn
> Fortunately installation went fine
> I would like now to write an experiment with many data flows between my
> topology nodes using producers and consumers
>
> Documentation does not really help since only ndnping is showed
>
> Is there any richer experiment example or tutorial ?
>
> My second question is How's to collect metrics once the emulation done ?
>
> Best regards
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161221/97031492/attachment.html>

From agawande at memphis.edu  Wed Dec 21 12:39:09 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Wed, 21 Dec 2016 20:39:09 +0000
Subject: [Mini-NDN] Richer experiment example
In-Reply-To: <CAJ8opn0YfpiRm+fim2=Yjak5SCV9GUU0aOj9arTPuzELdh7Z_g@mail.gmail.com>
References: <CAJ8opn1jjx6OQjztZPKY6XbjvjVyECP5K4_EGy7iwR33YWG7xQ@mail.gmail.com>,
	<CAJ8opn0YfpiRm+fim2=Yjak5SCV9GUU0aOj9arTPuzELdh7Z_g@mail.gmail.com>
Message-ID: <BN3PR04MB2196A36732F25F9B2F7C68A3D9930@BN3PR04MB2196.namprd04.prod.outlook.com>

You can issue any command available in the system on a node.

If you have your own application that is not installed in the system you can give the whole path to the application,


For example:


for node in net.hosts:

    if node.name == "nodename":

        node.cmd("/path/to/myapp options > /dev/null &")


Metric collection can be done by redirecting output of applications.

If you want metric collection from NFD or NLSR you will have to turn on logging (modules can be specified in

the nfd.conf file at /usr/local/etc/ndn/nfd.conf or if this is not present at: /usr/local/etc/ndn/nfd.conf.sample).


Or collect ndndump such as:

for host in net.hosts:
    for intf in host.intfNames():
          ndnDumpOutputFile = "dump.%s" % intf
          host.cmd("sudo ndndump -i %s > %s &" % (intf, ndnDumpOutputFile))  # can specify any  filter with -f option


Emulation is in the sense that multiple instances of NFD and NLSR are being run in real time.


Currently richer documentation is not available but Mini-NDN is based on Mininet which has a good documentation for the python API: https://github.com/mininet/mininet/wiki/Documentation


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Nour El Houda Ben Youssef <nou.mail at gmail.com>
Sent: Wednesday, December 21, 2016 2:26:24 PM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] Richer experiment example


Dear community

I'm new with mini ndn
Fortunately installation went fine
I would like now to write an experiment with many data flows between my topology nodes using producers and consumers

Documentation does not really help since only ndnping is showed

Is there any richer experiment example or tutorial ?

My second question is How's to collect metrics once the emulation done ?

Best regards

On Dec 21, 2016 6:45 PM, "Nour El Houda Ben Youssef" <nou.mail at gmail.com<mailto:nou.mail at gmail.com>> wrote:

Dear community

I'm new with mini ndn
Fortunately installation went fine
I would like now to write an experiment with many data flows between my topology nodes using producers and consumers

Documentation does not really help since only ndnping is showed

Is there any richer experiment example or tutorial ?

My second question is How's to collect metrics once the emulation done ?

Best regards
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161221/79782c0e/attachment.html>

From Matteo.Bertolino at eurecom.fr  Thu Dec 22 05:55:50 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Thu, 22 Dec 2016 14:55:50 +0100
Subject: [Mini-NDN] Richer experiment example
In-Reply-To: <CAJ8opn0YfpiRm+fim2=Yjak5SCV9GUU0aOj9arTPuzELdh7Z_g@mail.gmail.com>
References: <CAJ8opn1jjx6OQjztZPKY6XbjvjVyECP5K4_EGy7iwR33YWG7xQ@mail.gmail.com>
	<CAJ8opn0YfpiRm+fim2=Yjak5SCV9GUU0aOj9arTPuzELdh7Z_g@mail.gmail.com>
Message-ID: <20161222145550.41gm4mpxs8cos8w0@webmail.eurecom.fr>

Here there are some of my experiments with NACK, repo-ng, signature  
verification
https://github.com/MatteoBertolino92/NDN-matteo/blob/master/ndncxx_miniNDN_someUseCases_nacks__certificates__interest_verification.pdf

Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:

> Dear community
>
> I'm new with mini ndn
> Fortunately installation went fine
> I would like now to write an experiment with many data flows between my
> topology nodes using producers and consumers
>
> Documentation does not really help since only ndnping is showed
>
> Is there any richer experiment example or tutorial ?
>
> My second question is How's to collect metrics once the emulation done ?
>
> Best regards
>
> On Dec 21, 2016 6:45 PM, "Nour El Houda Ben Youssef" <nou.mail at gmail.com>
> wrote:
>
>> Dear community
>>
>> I'm new with mini ndn
>> Fortunately installation went fine
>> I would like now to write an experiment with many data flows between my
>> topology nodes using producers and consumers
>>
>> Documentation does not really help since only ndnping is showed
>>
>> Is there any richer experiment example or tutorial ?
>>
>> My second question is How's to collect metrics once the emulation done ?
>>
>> Best regards
>>
>



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



From nou.mail at gmail.com  Mon Dec 26 00:12:58 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Mon, 26 Dec 2016 09:12:58 +0100
Subject: [Mini-NDN] Mini-ndn experimentation
Message-ID: <CAJ8opn37sWaCE67FBk0wsrVcf_Xd_63Bef2MquU7_GvHd=VS=w@mail.gmail.com>

Dear community

I would like to ask
what is the difference between the setup and the run sections in an
experiment python file ?

best regards

-- 
Nour El Houda Ben Youssef Koub?a
PhD student Mobidoc - WEVIOO/SAGE/ENSI
Master degree New Generation of Information Systems - FST
Software Engineer - INSAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161226/7a323cac/attachment-0001.html>

From nou.mail at gmail.com  Mon Dec 26 01:04:27 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Mon, 26 Dec 2016 10:04:27 +0100
Subject: [Mini-NDN] Interest advertisment
Message-ID: <CAJ8opn2TL6jmRZeAVwcpr1PsQS=Os95o9eWJ0yhj+jgNjS3gnA@mail.gmail.com>

Dear community

I built a complex topology in mini-ndn

I would like know to schedule a particular data traffic exchanged between
the nodes of my topology

I used then experiment class to run producers and consumers on my
topology's nodes
I used it also redirection of logging results in order to observe what
happens in my topology


I know that I shoudl advertise interests so ndn become able to satisfy
requests

should I do it in the experiment file ?

Best regards


-- 
Nour El Houda Ben Youssef Koub?a
PhD student Mobidoc - WEVIOO/SAGE/ENSI
Master degree New Generation of Information Systems - FST
Software Engineer - INSAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161226/15a6ea0c/attachment.html>

From Matteo.Bertolino at eurecom.fr  Mon Dec 26 01:05:45 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Mon, 26 Dec 2016 10:05:45 +0100
Subject: [Mini-NDN] Mini-ndn experimentation
In-Reply-To: <CAJ8opn37sWaCE67FBk0wsrVcf_Xd_63Bef2MquU7_GvHd=VS=w@mail.gmail.com>
References: <CAJ8opn37sWaCE67FBk0wsrVcf_Xd_63Bef2MquU7_GvHd=VS=w@mail.gmail.com>
Message-ID: <20161226100545.4ysjntzjeo0ccwk8@webmail.eurecom.fr>

Hi,
the setup section logically contains how the code should be initialized.
The run code section how the code should behave.

Let's comment the example on the git. I would like to verify the  
packet exchange receiving ping packets. Then my experiment will have  
"run ndnpingserver" in the setup, and "print debug information" in the  
run part. Logically, running ndnpingserver should be done before the  
real experiments.

Bests,
Matteo

Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:

> Dear community
>
> I would like to ask
> what is the difference between the setup and the run sections in an
> experiment python file ?
>
> best regards
>
> --
> Nour El Houda Ben Youssef Koub?a
> PhD student Mobidoc - WEVIOO/SAGE/ENSI
> Master degree New Generation of Information Systems - FST
> Software Engineer - INSAT
>



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



From Matteo.Bertolino at eurecom.fr  Mon Dec 26 01:09:10 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Mon, 26 Dec 2016 10:09:10 +0100
Subject: [Mini-NDN] Interest advertisment
In-Reply-To: <CAJ8opn2TL6jmRZeAVwcpr1PsQS=Os95o9eWJ0yhj+jgNjS3gnA@mail.gmail.com>
References: <CAJ8opn2TL6jmRZeAVwcpr1PsQS=Os95o9eWJ0yhj+jgNjS3gnA@mail.gmail.com>
Message-ID: <20161226100910.3688sklxiscwk00g@webmail.eurecom.fr>

Actually I never used the experiments, but I suppose something of similar:
host.cmd("nlsrc advertise /abc/abd") (or self.cmd(...)
Bests, matteo :)

Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:

> Dear community
>
> I built a complex topology in mini-ndn
>
> I would like know to schedule a particular data traffic exchanged between
> the nodes of my topology
>
> I used then experiment class to run producers and consumers on my
> topology's nodes
> I used it also redirection of logging results in order to observe what
> happens in my topology
>
>
> I know that I shoudl advertise interests so ndn become able to satisfy
> requests
>
> should I do it in the experiment file ?
>
> Best regards
>
>
> --
> Nour El Houda Ben Youssef Koub?a
> PhD student Mobidoc - WEVIOO/SAGE/ENSI
> Master degree New Generation of Information Systems - FST
> Software Engineer - INSAT
>



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



From nou.mail at gmail.com  Mon Dec 26 01:12:01 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Mon, 26 Dec 2016 10:12:01 +0100
Subject: [Mini-NDN] Interest advertisment
In-Reply-To: <20161226100910.3688sklxiscwk00g@webmail.eurecom.fr>
References: <CAJ8opn2TL6jmRZeAVwcpr1PsQS=Os95o9eWJ0yhj+jgNjS3gnA@mail.gmail.com>
	<20161226100910.3688sklxiscwk00g@webmail.eurecom.fr>
Message-ID: <CAJ8opn2Ge_4wqTLAz+hCyp96EjEM3TcnNOaSKOPCteP=JOpbEQ@mail.gmail.com>

Thank you

On Mon, Dec 26, 2016 at 10:09 AM, Matteo Bertolino <
Matteo.Bertolino at eurecom.fr> wrote:

> Actually I never used the experiments, but I suppose something of similar:
> host.cmd("nlsrc advertise /abc/abd") (or self.cmd(...)
> Bests, matteo :)
>
>
> Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:
>
> Dear community
>>
>> I built a complex topology in mini-ndn
>>
>> I would like know to schedule a particular data traffic exchanged between
>> the nodes of my topology
>>
>> I used then experiment class to run producers and consumers on my
>> topology's nodes
>> I used it also redirection of logging results in order to observe what
>> happens in my topology
>>
>>
>> I know that I shoudl advertise interests so ndn become able to satisfy
>> requests
>>
>> should I do it in the experiment file ?
>>
>> Best regards
>>
>>
>> --
>> Nour El Houda Ben Youssef Koub?a
>> PhD student Mobidoc - WEVIOO/SAGE/ENSI
>> Master degree New Generation of Information Systems - FST
>> Software Engineer - INSAT
>>
>>
>
>
> ------------------------------------------------------------
> -------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
>


-- 
Nour El Houda Ben Youssef Koub?a
PhD student Mobidoc - WEVIOO/SAGE/ENSI
Master degree New Generation of Information Systems - FST
Software Engineer - INSAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161226/32e38673/attachment.html>

From nou.mail at gmail.com  Mon Dec 26 01:30:48 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Mon, 26 Dec 2016 10:30:48 +0100
Subject: [Mini-NDN] Mini-ndn experimentation
In-Reply-To: <20161226100545.4ysjntzjeo0ccwk8@webmail.eurecom.fr>
References: <CAJ8opn37sWaCE67FBk0wsrVcf_Xd_63Bef2MquU7_GvHd=VS=w@mail.gmail.com>
	<20161226100545.4ysjntzjeo0ccwk8@webmail.eurecom.fr>
Message-ID: <CAJ8opn2-acQQf+_2HmJ+1gqf6uZ8-dtNLpDK9WfBnprujBxL7Q@mail.gmail.com>

thank you

So if I want to schedule a data traffic it would be by putting in the setup:

 node.cmd("/ndn-cxx/example/producer  options > /Myfile &"):  producer on
node a
 self.cmd("a nlsrc advertise /abc/abd")
 node.cmd("/ndn-cxx/examples/consumer-with-timer options > /Myfile &") :
consumer on node b



then if I want to analyse what happend during the experiment
I would put this block in the run section:

for host in net.hosts:
    for intf in host.intfNames():
          ndnDumpOutputFile = "dump.%s" % intf
          host.cmd("sudo ndndump -i %s > %s &" % (intf, ndnDumpOutputFile))
 # can specify any  filter with -f option

best regards



On Mon, Dec 26, 2016 at 10:05 AM, Matteo Bertolino <
Matteo.Bertolino at eurecom.fr> wrote:

> Hi,
> the setup section logically contains how the code should be initialized.
> The run code section how the code should behave.
>
> Let's comment the example on the git. I would like to verify the packet
> exchange receiving ping packets. Then my experiment will have "run
> ndnpingserver" in the setup, and "print debug information" in the run part.
> Logically, running ndnpingserver should be done before the real experiments.
>
> Bests,
> Matteo
>
>
> Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:
>
> Dear community
>>
>> I would like to ask
>> what is the difference between the setup and the run sections in an
>> experiment python file ?
>>
>> best regards
>>
>> --
>> Nour El Houda Ben Youssef Koub?a
>> PhD student Mobidoc - WEVIOO/SAGE/ENSI
>> Master degree New Generation of Information Systems - FST
>> Software Engineer - INSAT
>>
>>
>
>
> ------------------------------------------------------------
> -------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
>


-- 
Nour El Houda Ben Youssef Koub?a
PhD student Mobidoc - WEVIOO/SAGE/ENSI
Master degree New Generation of Information Systems - FST
Software Engineer - INSAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161226/077b98e3/attachment.html>

From Matteo.Bertolino at eurecom.fr  Mon Dec 26 02:15:12 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Mon, 26 Dec 2016 11:15:12 +0100
Subject: [Mini-NDN] Mini-ndn experimentation
In-Reply-To: <CAJ8opn2-acQQf+_2HmJ+1gqf6uZ8-dtNLpDK9WfBnprujBxL7Q@mail.gmail.com>
References: <CAJ8opn37sWaCE67FBk0wsrVcf_Xd_63Bef2MquU7_GvHd=VS=w@mail.gmail.com>
	<20161226100545.4ysjntzjeo0ccwk8@webmail.eurecom.fr>
	<CAJ8opn2-acQQf+_2HmJ+1gqf6uZ8-dtNLpDK9WfBnprujBxL7Q@mail.gmail.com>
Message-ID: <20161226111512.8y2c6l23kksoow4w@webmail.eurecom.fr>

The reasoning is correct, the syntax probably is correct too but I did  
not verified :)
Matteo

Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:

> thank you
>
> So if I want to schedule a data traffic it would be by putting in the setup:
>
>  node.cmd("/ndn-cxx/example/producer  options > /Myfile &"):  producer on
> node a
>  self.cmd("a nlsrc advertise /abc/abd")
>  node.cmd("/ndn-cxx/examples/consumer-with-timer options > /Myfile &") :
> consumer on node b
>
>
>
> then if I want to analyse what happend during the experiment
> I would put this block in the run section:
>
> for host in net.hosts:
>     for intf in host.intfNames():
>           ndnDumpOutputFile = "dump.%s" % intf
>           host.cmd("sudo ndndump -i %s > %s &" % (intf, ndnDumpOutputFile))
>  # can specify any  filter with -f option
>
> best regards
>
>
>
> On Mon, Dec 26, 2016 at 10:05 AM, Matteo Bertolino <
> Matteo.Bertolino at eurecom.fr> wrote:
>
>> Hi,
>> the setup section logically contains how the code should be initialized.
>> The run code section how the code should behave.
>>
>> Let's comment the example on the git. I would like to verify the packet
>> exchange receiving ping packets. Then my experiment will have "run
>> ndnpingserver" in the setup, and "print debug information" in the run part.
>> Logically, running ndnpingserver should be done before the real experiments.
>>
>> Bests,
>> Matteo
>>
>>
>> Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:
>>
>> Dear community
>>>
>>> I would like to ask
>>> what is the difference between the setup and the run sections in an
>>> experiment python file ?
>>>
>>> best regards
>>>
>>> --
>>> Nour El Houda Ben Youssef Koub?a
>>> PhD student Mobidoc - WEVIOO/SAGE/ENSI
>>> Master degree New Generation of Information Systems - FST
>>> Software Engineer - INSAT
>>>
>>>
>>
>>
>> ------------------------------------------------------------
>> -------------------
>> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>>
>>
>
>
> --
> Nour El Houda Ben Youssef Koub?a
> PhD student Mobidoc - WEVIOO/SAGE/ENSI
> Master degree New Generation of Information Systems - FST
> Software Engineer - INSAT
>



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



From nou.mail at gmail.com  Mon Dec 26 02:45:55 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Mon, 26 Dec 2016 11:45:55 +0100
Subject: [Mini-NDN] Mini-ndn experimentation
In-Reply-To: <20161226111512.8y2c6l23kksoow4w@webmail.eurecom.fr>
References: <CAJ8opn37sWaCE67FBk0wsrVcf_Xd_63Bef2MquU7_GvHd=VS=w@mail.gmail.com>
	<20161226100545.4ysjntzjeo0ccwk8@webmail.eurecom.fr>
	<CAJ8opn2-acQQf+_2HmJ+1gqf6uZ8-dtNLpDK9WfBnprujBxL7Q@mail.gmail.com>
	<20161226111512.8y2c6l23kksoow4w@webmail.eurecom.fr>
Message-ID: <CAJ8opn2yh6rj7y3kfnwYVU6g-=c22hxAKMLkEZroqad9rQMZZg@mail.gmail.com>

Thanks

I hope it's correct ;)

On Mon, Dec 26, 2016 at 11:15 AM, Matteo Bertolino <
Matteo.Bertolino at eurecom.fr> wrote:

> The reasoning is correct, the syntax probably is correct too but I did not
> verified :)
>
> Matteo
>
> Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:
>
> thank you
>>
>> So if I want to schedule a data traffic it would be by putting in the
>> setup:
>>
>>  node.cmd("/ndn-cxx/example/producer  options > /Myfile &"):  producer on
>> node a
>>  self.cmd("a nlsrc advertise /abc/abd")
>>  node.cmd("/ndn-cxx/examples/consumer-with-timer options > /Myfile &") :
>> consumer on node b
>>
>>
>>
>> then if I want to analyse what happend during the experiment
>> I would put this block in the run section:
>>
>> for host in net.hosts:
>>     for intf in host.intfNames():
>>           ndnDumpOutputFile = "dump.%s" % intf
>>           host.cmd("sudo ndndump -i %s > %s &" % (intf,
>> ndnDumpOutputFile))
>>  # can specify any  filter with -f option
>>
>> best regards
>>
>>
>>
>> On Mon, Dec 26, 2016 at 10:05 AM, Matteo Bertolino <
>> Matteo.Bertolino at eurecom.fr> wrote:
>>
>> Hi,
>>> the setup section logically contains how the code should be initialized.
>>> The run code section how the code should behave.
>>>
>>> Let's comment the example on the git. I would like to verify the packet
>>> exchange receiving ping packets. Then my experiment will have "run
>>> ndnpingserver" in the setup, and "print debug information" in the run
>>> part.
>>> Logically, running ndnpingserver should be done before the real
>>> experiments.
>>>
>>> Bests,
>>> Matteo
>>>
>>>
>>> Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:
>>>
>>> Dear community
>>>
>>>>
>>>> I would like to ask
>>>> what is the difference between the setup and the run sections in an
>>>> experiment python file ?
>>>>
>>>> best regards
>>>>
>>>> --
>>>> Nour El Houda Ben Youssef Koub?a
>>>> PhD student Mobidoc - WEVIOO/SAGE/ENSI
>>>> Master degree New Generation of Information Systems - FST
>>>> Software Engineer - INSAT
>>>>
>>>>
>>>>
>>>
>>> ------------------------------------------------------------
>>> -------------------
>>> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>>>
>>>
>>>
>>
>> --
>> Nour El Houda Ben Youssef Koub?a
>> PhD student Mobidoc - WEVIOO/SAGE/ENSI
>> Master degree New Generation of Information Systems - FST
>> Software Engineer - INSAT
>>
>>
>
>
> ------------------------------------------------------------
> -------------------
> This message was sent using EURECOM Webmail: http://webmail.eurecom.fr
>
>


-- 
Nour El Houda Ben Youssef Koub?a
PhD student Mobidoc - WEVIOO/SAGE/ENSI
Master degree New Generation of Information Systems - FST
Software Engineer - INSAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161226/ce2b7098/attachment.html>

From nou.mail at gmail.com  Wed Dec 28 00:30:04 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Wed, 28 Dec 2016 09:30:04 +0100
Subject: [Mini-NDN] No route
Message-ID: <CAJ8opn1g2eCEpPURqKkKC4n6TFR=8+m-Uv=AWvZPTgRGw5KP=A@mail.gmail.com>

Dear community

I successfully build a customized topology in mini ndn

I would like to ask if I dont declare a router, does it mean that ndn will
not be able to route interests and data ?

I read in the documentation that with minindn,  each node has an instance
of NFD and nlsr runing  then why would someone need to declare a switch or
a router while building its topology ?

best regards



-- 
Nour El Houda Ben Youssef Koub?a
PhD student Mobidoc - WEVIOO/SAGE/ENSI
Master degree New Generation of Information Systems - FST
Software Engineer - INSAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161228/3f8e7b62/attachment.html>

From nou.mail at gmail.com  Wed Dec 28 00:55:03 2016
From: nou.mail at gmail.com (Nour El Houda Ben Youssef)
Date: Wed, 28 Dec 2016 09:55:03 +0100
Subject: [Mini-NDN] no data received
Message-ID: <CAJ8opn3EtrPdTTg4SnMpRsiKRGPozJTh8uYzS+hJ5k=kmJOXcA@mail.gmail.com>

Dear community

I have a producer on a node a
I advertised an interest using the following command

a nlsrc advertise /interest1

on the other hand I have a consumer emetting the interest /interest1

althought I find /interest1 in its FIB, I'm receiving a nack 150 (no route
) for each interest

what could be the reason ?

-- 
Nour El Houda Ben Youssef Koub?a
PhD student Mobidoc - WEVIOO/SAGE/ENSI
Master degree New Generation of Information Systems - FST
Software Engineer - INSAT
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20161228/caafc099/attachment.html>

From Matteo.Bertolino at eurecom.fr  Wed Dec 28 01:21:42 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Wed, 28 Dec 2016 10:21:42 +0100
Subject: [Mini-NDN] no data received
In-Reply-To: <CAJ8opn3EtrPdTTg4SnMpRsiKRGPozJTh8uYzS+hJ5k=kmJOXcA@mail.gmail.com>
References: <CAJ8opn3EtrPdTTg4SnMpRsiKRGPozJTh8uYzS+hJ5k=kmJOXcA@mail.gmail.com>
Message-ID: <20161228102142.ek9m35ku84g8sc08@webmail.eurecom.fr>

Please attach your producer code :)
matteo

Quoting Nour El Houda Ben Youssef <nou.mail at gmail.com>:

> Dear community
>
> I have a producer on a node a
> I advertised an interest using the following command
>
> a nlsrc advertise /interest1
>
> on the other hand I have a consumer emetting the interest /interest1
>
> althought I find /interest1 in its FIB, I'm receiving a nack 150 (no route
> ) for each interest
>
> what could be the reason ?
>
> --
> Nour El Houda Ben Youssef Koub?a
> PhD student Mobidoc - WEVIOO/SAGE/ENSI
> Master degree New Generation of Information Systems - FST
> Software Engineer - INSAT
>



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