[Mini-NDN] [Ndn-interest] Run an arbitrary program on miniNDN
Ashlesh Gawande (agawande)
agawande at memphis.edu
Wed Sep 7 08:28:11 PDT 2016
Sorry for the delay, I have approved your request to Mini-NDN list.
Yes that is the reason - you need an entry on the node b to node a. You can do a few things:
1) Use /ndn/edu/a in your producer-consumer example as they are already registered in FIB by NLSR.
2) Register prefix via nfdc register:
mininet> b nfdc register /example/testApp/ udp://1.0.0.1
1.0.0.1 would be the IP of a, you can check:
mininet> a ifconfig
This method won't work if you are trying to register for more than one hop since nodes cannot reach non-neighbors in Mini-NDN - you can use NLSR for routing as in step 3:
3) Use nlsrc:
mininet> a nlsrc advertise /example/testApp
So b will automatically get the entry via NLSR.
This would be the easiest I think.
Ashlesh
________________________________
From: Ndn-interest <ndn-interest-bounces at lists.cs.ucla.edu> on behalf of bertolin at eurecom.fr <bertolin at eurecom.fr>
Sent: Wednesday, September 7, 2016 10:11:55 AM
To: ndn-interest at lists.cs.ucla.edu
Subject: [Ndn-interest] Run an arbitrary program on miniNDN
Good morning to all,
Waiting for my request in miniNDN list, I need to ask an advice to the
community, using this mailing list.
I successfully installed and tried the ndnPing / ndnPingserver
commands with miniNDN, and all works. Now, next step. I would like to
run my personal program in the environment, byt I am having some
troubles and my poor knowledge does not help me.
I wrote a simple topology composed by two nodes, a and b, connected by
a link. I've already used this topology for the ping experiment so I
assume that it is correct.
Now I would like to put in a node the program "producer" already
written in the section "examples" of ndn-cxx package availaible on the
git, and the "consumer" on b node.
Both programs are here:
https://github.com/named-data/ndn-cxx/tree/master/examples
I generated the executable and I was trying to run them into a and b.
The consumer start, it express its interest for the prefix
/example/testApp/randomData , but after few time the timeout expires.
Making some little changing in the producer, I noticed that it
successfully enter into Run() function, but it does not enter neither
in onInterest callback and onRegisterFailed callback.
My suspicious is that the prefix /example/testApp is not registered
anywhere, because I do not see it into the tables. Indeed:
The FIB table of a is:
/ndn/NLSR/sync nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
/localhost/nfd/rib nexthops={faceid=256 (cost=0)}
/ndn/NLSR/LSA nexthops={faceid=260 (cost=10)}
/ndn/broadcast/KEYS nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
/ndn/NLSR/LSA/edu/%C1.Router/cs/a nexthops={faceid=257 (cost=0)}
/ndn/edu/%C1.Router/cs/b nexthops={faceid=260 (cost=10)}
/localhost/nfd nexthops={faceid=1 (cost=0)}
/localhost/nlsr nexthops={faceid=257 (cost=0)}
/ndn/edu/%C1.Router/cs/a nexthops={faceid=257 (cost=0)}
The FIB table of b is:
/ndn/NLSR/sync nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
/localhost/nfd/rib nexthops={faceid=256 (cost=0)}
/ndn/NLSR/LSA nexthops={faceid=260 (cost=10)}
/ndn/broadcast/KEYS nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
/ndn/edu/%C1.Router/cs/b nexthops={faceid=257 (cost=0)}
/ndn/edu/a nexthops={faceid=260 (cost=10)}
/localhost/nfd nexthops={faceid=1 (cost=0)}
/localhost/nlsr nexthops={faceid=257 (cost=0)}
/ndn/edu/%C1.Router/cs/a nexthops={faceid=260 (cost=10)}
/ndn/NLSR/LSA/edu/%C1.Router/cs/b nexthops={faceid=257 (cost=0)}
So I am getting wrong something I think... any advice ?
Thanks to all,
Matteo
-------------------------------------------------------------------------------
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20160907/80ee180c/attachment.html>
More information about the Mini-NDN
mailing list