[Mini-NDN] beginner in mini-ndn

Mon Sep 28 11:16:09 PDT 2020

________________________________
From: marwa kareem <m.kareem1305 at coeng.uobaghdad.edu.iq>
Sent: Friday, September 25, 2020 8:19 AM
To: Saurab Dulal (sdulal) <sdulal at memphis.edu>
Subject: Re: beginner in mini-ndn

Hi Saurab,
Thank you for your detailed answer,

1- I didn't realize that I should run the app from the /build/examples/producer so I go to the folder and run ./consumer and the app is working , so thank you very much for your help.

2-So do you mean that the [ndn router] in the attachment image is the [nodes] section in mini-ndn, so if I want to do the same network in the image I need 8 nodes (1 for consumer, 1 for producer and 6 for ndn router)?

- Yes, you need to have 8 nodes. But all these nodes should run nfd, even for the nodes running consumer and producer, as they communicate with local nfd to send and receive packets. To put it simply, a node in Mini-NDN can technically run anything, forwarder, daemons, and so on. Just look at some of the examples and you should be able to figure out more.

A real host I mean not virtual node in mini-ndn machine but  a real one (a host run on a virtual machine or a physical one ) so if I request a real content from another machine (producer) the content will be transmitted to my machine (consumer), is there a way to do that?

- Yes, definitely you can transfer content between machines (physical), that's what ndn testbed is doing right now (http://ndndemo.arl.wustl.edu/). You need to install forwarder (nfd), set up routes, and you will be able to transfer packets. For more information, you can refer https://named-data.net/doc/NFD/current/INSTALL.html. Also, the named-data website is a great place to learn more about this stuff.

- Mini-NDN is an emulator tool, every node has its own container, and runs real ndn packages. So, it's a close approximation to a real environment.

3-so if the nodes can act as (an ndn router)  in mini-ndn because the nfd is running on each node and each node has a cs and fib tables, what is the benefit of the switch in this case?
sorry if I understand this in a wrong way but can you correct my idea about this subject because I'm really confused about that.

- The switches in Mini-NDN are inherited from mininet, they are just the regular IP switches. Having said that, the switches provide the same functionally as IP switches and so they are there in the conf section and they are not ndn-switches.

4- I attached a paper and mark the sentence in it,  so if there is no ndn-switches what about the [switches] section in the .conf file in mini-ndn, doesn't it consider an ndn-switches? or do you mean there is no real ndn-switches?

- NDN works at layer 3 and works with names. The layer-2 switches work with physical addresses. They are different and yes, you will still need switches. For example, AP in the wireless setup is a switch.

- The paper you have attached is taking about layer-3 switch and yes layer-3 switches have the capability of both the router and switch, and sometimes are referred to as the same. For the NDN case, I would still call them routers rather than switch even though paper calls them the same, just to avoid confusion.

5- can students or researchers have access to these real ndn-routers to implement experiments?

- Yes, you can experiment with ndn-routers. NDN testbed (http://ndndemo.arl.wustl.edu/) is for that very purpose. For more details see this page: https://named-data.net/ndn-testbed/policies-connecting-nodes-ndn-testbed/

Regards,
Saurab Dulal

best regard, marwa

On Thu, Sep 24, 2020 at 9:05 PM Saurab Dulal (sdulal) <sdulal at memphis.edu<mailto:sdulal at memphis.edu>> wrote:
Hi Marwa,

Please see the inline answers.

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Lan Wang (lanwang) <lanwang at memphis.edu<mailto:lanwang at memphis.edu>>
Sent: Thursday, September 24, 2020 9:03 AM
To: Junxiao Shi via Mini-NDN <mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>>
Subject: [Mini-NDN] beginner in mini-ndn

Begin forwarded message:

The attached message has been automatically discarded.
From: marwa kareem <m.kareem1305 at coeng.uobaghdad.edu.iq<mailto:m.kareem1305 at coeng.uobaghdad.edu.iq>>
Subject: beginner in mini-ndn
Date: September 24, 2020 at 6:54:33 AM CDT
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>

Hello mini-ndn team

I'm still a beginner in mini-ndn , I read the documentation and implemented the ping stuff in the command line, but now I'm stuck in the next step, so could you please help me.

1-I want to implement a consumer/producer scenario however I don't know how to begin with that, there is consumer/producer program files in the ndn-cxx folder but i don't know how to use them, I try to run ./build/examples/producer.cpp but it don't work.
I don't understand what do you mean by "it didn't work". If you want to test how the consumer/producer in the example folder of ndn-cxx works, you must compile ndn-cxx with examples i.e. ./waf configure --with-examples && ./waf build && sudo ./waf install. This will create a consumer/producer app in ./build/examples/ folder. Now you can simply run the producer app first and then consumer app to see the basic interest data exchange. Remember to run nfd before testing consumer/producer. Just wanted to make you clear that this has nothing to do with Mini-NDN. In Mini-NDN, you can use any app/tools or whatever and can run it from a node. Say, you have a consumer app installed in your system. Now, you can simply run <node> consumer from Mini-NDN CLI or do the same from the experiment. Please look at: ndn-tools (https://github.com/named-data/ndn-tools), ndn-cxx/examples etc. All of these can run easily from Mini-NDN. Also, refer to mini-ndn<https://github.com/named-data/mini-ndn>/examples/ for some example experiments.

2- what is the meaning of  [nodes] section in the default-topology.conf file in mini-ndn, is it a host? If I want to make it a real host/node, how can I do that?
[nodes] section represents all the nodes in a network topology. Yes, it is a host/node. In the topology you have attached below, [nodes] will be all the NDN-Router. See the examples/mnndn.py. It is using default-topology which has 4 nodes and 3 links. When you run the example, all the nodes (a, b...) act as a real ndn node and runs the nfd. Let me know if mean anything else by "real host/node".
3- how can I add a switch to the default-topology file ?
There are multiple ways to add switches i) via conf file (topology file). Just add a section [switches] like [nodes] and add switches there ii) via the experiment https://github.com/mininet/mininet/blob/master/mininet/net.py#L249. You need to connect a node and a switch with a link. We will add an example for the switch sometime later. Also, you are most welcome to add one once you figure out 🙂.

4- why the switch, the router, is the same in icn/ndn? is it because it deal with names instead of the ip adresses so it doesn't matter if it is a switch or a router?
I am not sure how to answer this. I don't know if there is anything called NDN-switches and I doubt they are same. Can you point me where you read them being the same?
4- in the attachment image, what is the "ndn router" , Is it the forwarder(nfd) that runs in the node? or is it a real router? a general purpose router? or it is a specific ndn software?
Yes, ndn-router is a real router and yes it runs the forwarder. You can read this paper to get started: https://named-data.net/wp-content/uploads/2014/10/named_data_networking_ccr.pdf. You can also find more resources here: https://named-data.net/publications/

Thank you,
Saurab Dulal
best regards, marwa
[https://attachments.office.net/owa/sdulal%40memphis.edu/service.svc/s/GetAttachmentThumbnail?id=AAMkAGJkNGZmYTNjLWE4NGUtNDQxOC04ODg3LWE5N2UxNWQ2NjM2ZgBGAAAAAAAHlE7e7X5nSJXV0NC54Am2BwC4r6cG%2B%2BgVSrhBuKWNdaZSAAAAAAEPAAC4r6cG%2B%2BgVSrhBuKWNdaZSAAMx5HsDAAABEgAQAGpiOByv1w5NhziU18Nja74%3D&thumbnailType=2&owa=outlook.office.com&scriptVer=20200921004.05&X-OWA-CANARY=yUtEsfY2Q0aPUxSq_ANRY4CXXQvZY9gYPSdmzAS4lJ4kOBHuU9e7vIGGHpXcmhOR86WXzhYQRvI.&token=eyJhbGciOiJSUzI1NiIsImtpZCI6IjU2MzU4ODUyMzRCOTI1MkRERTAwNTc2NkQ5RDlGMjc2NTY1RjYzRTIiLCJ0eXAiOiJKV1QiLCJ4NXQiOiJWaldJVWpTNUpTM2VBRmRtMmRueWRsWmZZLUkifQ.eyJvcmlnaW4iOiJodHRwczovL291dGxvb2sub2ZmaWNlLmNvbSIsInVjIjoiZWExMmRjMWY4ZmY3NGQ3ZmI0Yzk4NDE5YmVkMWQxMzkiLCJzaWduaW5fc3RhdGUiOiJbXCJrbXNpXCJdIiwidmVyIjoiRXhjaGFuZ2UuQ2FsbGJhY2suVjEiLCJhcHBjdHhzZW5kZXIiOiJPd2FEb3dubG9hZEBhZTE0NWFlYS1jZGIyLTQ0NmEtYjA1YS03ODU4ZGRlNWRkYmEiLCJpc3NyaW5nIjoiV1ciLCJhcHBjdHgiOiJ7XCJtc2V4Y2hwcm90XCI6XCJvd2FcIixcInByaW1hcnlzaWRcIjpcIlMtMS01LTIxLTEyMTczNjM2NzMtNDA1ODg3MzM0NC05NDEwNTQ2MjgtMTA2MDY2ODlcIixcInB1aWRcIjpcIjExNTM4MzYyOTY2ODAwMjAwNzBcIixcIm9pZFwiOlwiNTcyMThhYzYtNTI3Mi00ZGIxLThjOWMtMzcxNzhmZjFhY2NmXCIsXCJzY29wZVwiOlwiT3dhRG93bmxvYWRcIn0iLCJuYmYiOjE2MDEzMTYxODEsImV4cCI6MTYwMTMxNjc4MSwiaXNzIjoiMDAwMDAwMDItMDAwMC0wZmYxLWNlMDAtMDAwMDAwMDAwMDAwQGFlMTQ1YWVhLWNkYjItNDQ2YS1iMDVhLTc4NThkZGU1ZGRiYSIsImF1ZCI6IjAwMDAwMDAyLTAwMDAtMGZmMS1jZTAwLTAwMDAwMDAwMDAwMC9hdHRhY2htZW50cy5vZmZpY2UubmV0QGFlMTQ1YWVhLWNkYjItNDQ2YS1iMDVhLTc4NThkZGU1ZGRiYSIsImhhcHAiOiJvd2EifQ.HPxQbuenkaCyYKYK9UTrarEUmY7lBUPSTfH0RetCEuEXsGcoooTVNoPx9d8WAdibwwEz3g8FazNO9olO8jF8ghtK3JiQP6aovZljPnO2O640AIwfeceV7IOTXSkBW69Is3y1cnSZfWrF7PS_rO8y8iy5MT9Th6f0yaXYT1MuGsj5zItSCC2WCRQcApK-LW_JaZI84S-YoJIcplmz5-1IKAHWxbDsCRTiNY-2j-XBwJ9FUNvGQvJzM2KUOa9gMYHjwmiksS5HW7PGLc70ZYm4MFp9N9ffIcLZsVh6J1rhOOwFVjMBdwQKqirfvpYaoAEfW9voRATuMvuWBB9B-fGJaw&animation=true]

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