named-data / mini-ndn Goto Github PK

When I run the pingall.py and any other experiment, it shows that:

root@ubuntu:~/mini-ndn-demo/mini-ndn# sudo python examples/nlsr/pingall.py
Using topology file /usr/local/etc/mini-ndn/default-topology.conf
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
ERROR: No default identity
*** Starting controller
c0
*** Starting 0 switches

Waiting 60 seconds for convergence...
...done
NLSR has converged successfully.
Each node will ping 4 node(s)
Scheduling ping(s) from a to b
Scheduling ping(s) from a to c
Scheduling ping(s) from a to d
Scheduling ping(s) from b to c
Scheduling ping(s) from b to d
Scheduling ping(s) from b to a
Scheduling ping(s) from c to d
Scheduling ping(s) from c to a
Scheduling ping(s) from c to b
Scheduling ping(s) from d to a
Scheduling ping(s) from d to b
Scheduling ping(s) from d to c
*** Starting CLI:
mini-ndn>

So why does it tell me," No default identity”. Is there something I forgot to install?

Due to a recent update of a package dependency, vagrant up now hangs because APT waits for user input to the following question:

Configuring wireshark-common
Dumpcap can be installed in a way that allows members of the "wireshark" system group to capture packets. This is recommended over the alternative of running Wireshark/Tshark directly as root, because less of the code will run with elevated privileges. For more detailed information please see /usr/share/doc/wireshark common/README.Debian. Enabling this feature may be a security risk, so it is disabled by default. If in doubt, it is suggested to leave it disabled. Should non-superusers be able to capture packets?
[Yes] [No]

This question is raised during Open vSwitch setup procedure.

Unfortunately, I am not able to override the APT behaviour. I've tried to use DEBIAN_FRONTEND=noninteractive in both Vagrantfile and install.sh. I've also tried, unsuccessfully, to issue a sudo dpkg-reconfigure debconf -f noninteractive -p critical prior to Vagrant provision.

Is there any way to force a fully unattended installation using Vagrant?

Hi,

recent changes have broken Mini-NDN for people using MiniNet 2.2.1 (e.g., in Ubuntu 16.4.2 and 16.10). The offending line is this:

--8<--
File "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.3.0-py2.7.egg/ndn/remote_ndn_link.py", line 62, in
from mininet.examples.cluster import RemoteLink, RemoteGRELink
ImportError: cannot import name RemoteGRELink
--8<--

RemoteGRELink was added to MiniNet relatively recently. As this seems to be for some optional functionality, would it be possible to use it only if the underlying MiniNet supports it? I.e.: place try/catch clauses around the import and other code to avoid runtime errors like the above?

Cheers,

Alex

Hi,
When NFD works in a wireless network, is there a difference between the wireless network and the wired network on the forwarding mechanism? How do two nodes initially establish a connection at the physical and data link layers? It is based on 802.11 and commuicates by encapsulating the NDN packet into an IP packet in the simulator?
Look forward to your reply!

I want to use this project to implement SD-ICN experiment. Can it support the function by appropriate modification of mini-ndn and the controller?

i installed the minindn successfully but when i try to start it i get this the mininet cli is'nt showing and i get this error
`sudo minindn --experiment=pingall --nPings=50
No results folder specified; experiment results will remain in the working directory
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
*** gave up after 3 retries
`

Hi, Excuseme ... I have a NDN report operation , can you write the details of the operation of NDN like your video "Mini-NDN". I like your video, but I'm trying to understand what you do. Thank you so much!

Hi, i want to know if there is any tool for NLSR in mini-ndn to get some informations about the entire work process of NLSR, such as neighbor finding, route table calculation, lsdb updates and so on. Look forward to your kind reply.

Hi,

I installed mini-ndn but am getting this error in the verification step:

--8<--
vagrant@vagrant-ubuntu-trusty-64:~$ sudo minindn --pingall 50 --ctime 180 ndn_utils/hyperbolic_conf_file/minindn.caida.conf
Usage: minindn [template_file] [ -t | --testbed ]
If no template_file is given, ndn_utils/default-topology.conf (given sample file)
will be used.
If --testbed is used, minindn will run the NDN Project Testbed.

minindn: error: no such option: --pingall
--8<--

It seems the command-line options have changed. Not sure if I should replace --pingall with -nPings?

Cheers,

Alex

sudo: minindn: command not found

Does not work on version 0.5.0 but it works on 0.4.0.

How i can run in each host of mini-ndn one NFD?

Scenario: I want to close the NFD just in one host not in the others. Thats is possible?

As per the Mini-NDN Documentation:
Execution
To run Mini-NDN with a topology file, provide the filename as the first argument:
sudo python examples/minindn.py my-topology.conf

I tried running other topologies as mentioned but getting error:
Error reading config file: No section: 'nodes'

How to solve the above issue?
I have attached a screenshot for your reference.

hi..

How I can add a cs entries in nodes?

thank you

I just installed minindn and all its dependencies following the instructions in GitHub. After installing, when I write the command: "sudo minindn" the following error occurs:

Traceback (most recent call last):
File "/usr/local/bin/minindn", line 4, in
import('pkg_resources').run_script('Mini-NDN==0.4.0', 'minindn')
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 658, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python3/dist-packages/pkg_resources/init.py", line 1438, in run_script
exec(code, namespace, namespace)
File "/usr/local/lib/python3.6/dist-packages/Mini_NDN-0.4.0-py3.6.egg/EGG-INFO/scripts/minindn", line 70, in
from ndn import ExperimentManager
File "/usr/local/lib/python3.6/dist-packages/Mini_NDN-0.4.0-py3.6.egg/ndn/init.py", line 24, in
import experiment_manager as ExperimentManager
ModuleNotFoundError: No module named 'experiment_manager'

FYI, my mininet is running properly

Hello Ashlesh Gawande, Can you demo this https://github.com/NDN-Routing/OSPFN3.0 , I'm strying but it's still error..!

hi,

when I do ndnping, the result shows as the following:
PING /ndn/h1-site/h1
nack from /ndn/h1-site/h1: seq=908807860193924757 time=9.50899 ms reason=NoRoute

--- /ndn/h1-site/h1 ping statistics ---
1 packets transmitted, 0 received, 1 nacked, 0% lost, 100% nacked, time 0 ms

My Question:
what does it mean by "nacked" and "NoRoute"

Thanks in advance
Enas Bagies

Error: Cannot unpack waf lib into /home/vagrant/mkb/mini-ndn/ndn-src/ndn-cxx/.waf3-2.0.21-16cd196b0fc7b4eebe195ce20396f3d1
Move waf in a writable directory

This is the error coming up while installing the minindn

Hi,

I was wondering if it would be a good idea to modify the install.sh script to (optionally) use specific versions of MiniNet, NFD etc. instead of the current HEAD in the development repository. For example, for Mininet to be version 2.2.2b2, the following git commands would be run to clone the Mininet repository and choose the specific version:

git clone --depth 1 https://github.com/mininet/mininet
git checkout tags/2.2.2b2

This way, running MiniNDN experiments in a Vagrant box would be truly repeatable. The versions could be defined as HEAD by default and install.sh could, say, include a versions.def file if it exists.

I'll create such a modified install.sh for myself and am happy to turn that into a pull request if anyone else is interested.

Cheers,

Alex

Can you send me file txt of ndn-cxx , NFD , ChornoSync checkout code

I have a problem about demo Mini-NDN. Can I use 2 Ubuntu 16.04 to demo multiple node ping each other. Thank you!

Install.rst instructs users to install mininet. However https://github.com/named-data/mini-ndn/blob/master/docs/install.rst#verification does not work with mininet, instead it requires mininet-wifi.

When you enable the security mode of Minindn/Nlsr (argument --security) the startup process gives the following error (either with or without --work-dir arg)

~/mini-ndn$ sudo python examples/nlsr/pingall.py --security --work-dir /tmp/minindn
Using topology file /usr/local/etc/mini-ndn/default-topology.conf
*** Creating network
*** Adding controller
*** Adding hosts:
a b c d
*** Adding switches:

*** Adding links:
(10ms delay) (10ms delay) (a, b) (10ms delay) (10ms delay) (a, c) (10ms delay) (10ms delay) (b, d)
*** Configuring hosts
a b c d
Dummy key chain patch is installed in ndn-cxx. Security will be disabled.
*** Starting controller
c0
*** Starting 0 switches

Traceback (most recent call last):
  File "examples/nlsr/pingall.py", line 50, in <module>
    logLevel='ndn.*=TRACE:nlsr.*=TRACE')
  File "/home/minindn/mini-ndn/minindn/apps/app_manager.py", line 33, in __init__
    self.startOnNode(host, **appParams)
  File "/home/minindn/mini-ndn/minindn/apps/app_manager.py", line 38, in startOnNode
    app = self.cls(host, **appParams)
  File "/home/minindn/mini-ndn/minindn/apps/nlsr.py", line 93, in __init__
    self.createKeysAndCertificates()
  File "/home/minindn/mini-ndn/minindn/apps/nlsr.py", line 113, in createKeysAndCertificates
    securityDir = '{}/security'.format(self.parameters['workDir'])
KeyError: 'workDir'

The problem seems to be related to the way Nlsr app expects to access the Minindn working dir to create the root keys/certificate (minindn/apps/nlsr.py:113). The current code expects workDir to be part of the node parameter (Line 50: self.parameters = self.node.params['params'] and Line 113: securityDir = '{}/security'.format(self.parameters['workDir'])), however the workDir is actually an global parameter of Minindn and should be available for any app that may need it. Even for distributed experiments, the app copies some files from the Minindn workDir. The nodes will have the homeDir (based on the workDir). Thus, maybe it is better to change Nlsr app to use workDir from Minindn instead from node's attributes.

I would say the same about the resultsDir, but since there is no app using it now, it gives no problem now.

hi,

I need to know what are the default values of links bandwidth, CS and CPU with their units?

Thank an advance,
Enas

Hi,

I have a problem with the build of ndn-tools. The command "./waf configure" ran successfully, but the next command "./waf" doesn't. I have always errors:
zakaria@ubuntu:~/mini-ndn/ndn-tools$ sudo ./waf configure Setting top to : /home/zakaria/mini-ndn/ndn-tools Setting out to : /home/zakaria/mini-ndn/ndn-tools/build Checking for 'g++' (C++ compiler) : /usr/bin/g++ Checking C++ compiler version : 5.4.0 Checking supported CXXFLAGS : -std=c++14 Checking supported LINKFLAGS : -fuse-ld=gold Checking for program 'sphinx-build' : /usr/local/bin/sphinx-build Checking for program 'pkg-config' : /usr/bin/pkg-config Checking for 'libndn-cxx' : yes Checking for program 'dpkg-architecture' : /usr/bin/dpkg-architecture Checking boost includes : 1.58.0 Checking boost libs : boost_system boost_program_options boost_filesystem Checking for boost linkage : ok Checking for 'libpcap' : yes Checking if struct tcphdr has member th_off : yes Checking if struct udphdr has member uh_ulen : yes Checking supported CXXFLAGS : -O2 -g -pedantic -Wall -Wextra -Wnon-virtual-dtor -Wno-unused-parameter -fdiagnostics-color Checking supported LINKFLAGS : -Wl,-O1 Tools to build : peek, dump, dissect, ping, chunks, dissect-wireshark 'configure' finished successfully (1.088s) zakaria@ubuntu:~/mini-ndn/ndn-tools$ sudo ./waf Waf: Entering directory/home/zakaria/mini-ndn/ndn-tools/build'
[ 5/39] Linking build/bin/ndnpeek
[ 8/39] Linking build/bin/ndnpoke
[19/39] Linking build/bin/ndnping
../tools/peek/ndnpeek/ndnpeek.hpp:61: error: undefined reference to 'ndn::scheduler::Scheduler::~Scheduler()'
../tools/peek/ndnpeek/main.cpp:182: error: undefined reference to 'ndn::io::loadBuffer(std::istream&, ndn::io::IoEncoding)'
../tools/peek/ndnpeek/main.cpp:197: error: undefined reference to 'ndn::io::loadBuffer(std::istream&, ndn::io::IoEncoding)'
../tools/peek/ndnpeek/ndnpeek.cpp:38: error: undefined reference to 'ndn::scheduler::Scheduler::Scheduler(boost::asio::io_service&)'
../tools/peek/ndnpeek/ndnpeek.cpp:70: error: undefined reference to 'ndn::Interest::setHopLimit(nonstd::optional_lite::optional)'
../tools/peek/ndnpeek/ndnpeek.cpp:51: error: undefined reference to 'ndn::scheduler::Scheduler::schedule(boost::chrono::duration<long, boost::ratio<1l, 1000000000l> >, std::function<void ()>)'
collect2: error: ld returned 1 exit status

../tools/peek/ndnpoke/ndnpoke.hpp:56: error: undefined reference to 'ndn::scheduler::Scheduler::~Scheduler()'
../tools/peek/ndnpoke/ndnpoke.cpp:114: error: undefined reference to 'ndn::scheduler::Scheduler::schedule(boost::chrono::duration<long, boost::ratio<1l, 1000000000l> >, std::function<void ()>)'
../tools/peek/ndnpoke/ndnpoke.cpp:41: error: undefined reference to 'ndn::scheduler::Scheduler::Scheduler(boost::asio::io_service&)'
collect2: error: ld returned 1 exit status

../tools/ping/client/ping.hpp:54: error: undefined reference to 'ndn::scheduler::Scheduler::~Scheduler()'
../tools/ping/client/ping.cpp:77: error: undefined reference to 'ndn::scheduler::Scheduler::schedule(boost::chrono::duration<long, boost::ratio<1l, 1000000000l> >, std::function<void ()>)'
../tools/ping/client/ping.cpp:37: error: undefined reference to 'ndn::scheduler::Scheduler::Scheduler(boost::asio::io_service&)'
../tools/ping/client/ping.cpp:37: error: undefined reference to 'ndn::scheduler::Scheduler::~Scheduler()'
collect2: error: ld returned 1 exit status

Waf: Leaving directory /home/zakaria/mini-ndn/ndn-tools/build' Build failed -> task in 'ndnpeek' failed with exit status 1 (run with -v to display more information) -> task in 'ndnpoke' failed with exit status 1 (run with -v to display more information) -> task in 'ndnping' failed with exit status 1 (run with -v to display more information)

Could you help me, please?
Thanks in advance.

Hello everyone!

If I have three nodes A---B---C, how can I know node A communicate with node C must throught node B

Thank you.!

Hello,
I've been using mini-ndn for a couple of days, and it's awesome. I guess my question is: how does mini-ndn virtualize nodes? Do nodes share memory and storage? Because whenever I try to modify the NFD configuration on one node, I discover that the changes are reflected in all other nodes.

Thanks,
Azzam

Hi,
Does NLSR sends/receives packets to/from NFD by unix domain socket? How does NFD handle these packets when it receives packets from NLSR or other applications. It still put them in forwarding pipelines as usual? And how does NFD handle these packets when it receives interest/data produced by neighbor's NLSR?
Look forward to your reply.

Hi, I installed mini-ndn using the script. I also installed all dependencies using the script. However, I had one remaining issue on Ubuntu 14.04. When I ran nlsrc it failed because it did not find libChronoSys.so. While it was installed, it was not picked up until I ran ldconfig. You might want to add this command to the install script after libChronoSys is installed.

This script fails with the following error

Traceback (most recent call last):
  File "examples/nlsr/pingall.py", line 56, in <module>
    Experiment.startPctPings(ndn.net, args.nPings, args.pctTraffic)
  File "/home/mmlab/mini-ndn/minindn/helpers/experiment.py", line 98, in startPctPings
    NDNPingClient.ping(host, other, nPings)
  File "/home/mmlab/mini-ndn/minindn/helpers/ndnpingclient.py", line 45, in ping
    str.replace(prefix[1:], "/", "-")

line #98 of mini-ndn/minindn/helpers/experiment.py should be replaced from NDNPingClient.ping(host, other, nPings) to NDNPingClient.ping(host, other.name, nPings)

My team has developed a new cache replacement policy and we want to simulate it in mini-ndn using the new cache replacement policy instead of the default policy. Does anybody have any idea how to simulate it and find the metrics? We want to use the ndn-grid.cpp scenario for this purpose.

Hi,
When NFD works in a wireless network, is there a difference between the wireless network and the wired network on the forwarding mechanism? How do two nodes initially establish a connection at the physical and data link layers? It is based on 802.11 and commuicates by encapsulating the NDN packet into an IP packet in the simulato?
Look forward to your reply!

When typing the following command:
sudo minindnedit
to open the GUI program Mini-NDN Edit, It says:
sudo: minindnedit: command not found

/install.sh -i
Reading package lists... Done
Building dependency tree
Reading state information... Done
libigraph0-dev is already the newest version (0.7.1-4build1).
tshark is already the newest version (3.2.3-1).
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
Requirement already satisfied: python-igraph in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 1)) (0.8.2)
Requirement already satisfied: setuptools in /usr/local/lib/python3.6/site-packages (from -r requirements.txt (line 2)) (28.8.0)
Requirement already satisfied: texttable>=1.6.2 in /usr/local/lib/python3.6/site-packages (from python-igraph->-r requirements.txt (line 1)) (1.6.3)
Could not build wheels for python-igraph, since package 'wheel' is not installed.
Could not build wheels for setuptools, since package 'wheel' is not installed.
Could not build wheels for texttable, since package 'wheel' is not installed.
WARNING: You are using pip version 20.1; however, version 20.2.3 is available.
You should consider upgrading via the '/usr/local/bin/python3.6 -m pip install --upgrade pip' command.
Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease
Ign:2 http://ppa.launchpad.net/named-data/ppa/ubuntu 20.04.1 InRelease
Hit:3 http://archive.canonical.com/ubuntu focal InRelease
Hit:4 http://archive.ubuntu.com/ubuntu focal-updates InRelease
Hit:5 http://dl.google.com/linux/chrome/deb stable InRelease
Hit:6 https://dl.yarnpkg.com/debian stable InRelease
Hit:8 http://archive.ubuntu.com/ubuntu focal-backports InRelease
Ign:9 http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu focal InRelease
Hit:7 https://cli-assets.heroku.com/apt ./ InRelease
Hit:10 https://packages.microsoft.com/ubuntu/18.04/mssql-server-2019 bionic InRelease
Hit:11 http://archive.ubuntu.com/ubuntu focal-security InRelease
Hit:12 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease
Hit:13 http://ppa.launchpad.net/kaihengfeng/fix-lp1869819/ubuntu focal InRelease
Ign:14 http://ppa.launchpad.net/named-data/ppa/ubuntu focal InRelease
Hit:15 http://ppa.launchpad.net/teejee2008/ppa/ubuntu focal InRelease
Ign:16 http://ppa.launchpad.net/webupd8team/java/ubuntu focal InRelease
Err:17 http://ppa.launchpad.net/named-data/ppa/ubuntu 20.04.1 Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Err:18 http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu focal Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Err:19 http://ppa.launchpad.net/named-data/ppa/ubuntu focal Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Err:20 http://ppa.launchpad.net/webupd8team/java/ubuntu focal Release
404 Not Found [IP: 2001:67c:1560:8008::15 80]
Reading package lists... Done
E: The repository 'http://ppa.launchpad.net/named-data/ppa/ubuntu 20.04.1 Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/gwibber-daily/ppa/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/named-data/ppa/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: The repository 'http://ppa.launchpad.net/webupd8team/java/ubuntu focal Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Reading package lists... Done
Building dependency tree
Reading state information... Done
python-setuptools is already the newest version (44.0.0-2).
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
cp: cannot stat 'topologies/minindn.testbed.conf': No such file or directory
cp: cannot stat 'topologies/current-testbed.conf': No such file or directory
Traceback (most recent call last):
File "setup.py", line 3, in
from setuptools import setup, find_packages
File "/usr/lib/python3/dist-packages/setuptools/init.py", line 5, in
import distutils.core
ModuleNotFoundError: No module named 'distutils.core'

Hi,
After the installation of mini-ndn, in the verification step using this command:
sudo minindn --experiment=pingall --nPings=50
I got the following error:
Traceback (most recent call last):
File "/usr/local/bin/minindn", line 5, in
pkg_resources.run_script('Mini-NDN==0.3.0', 'minindn')
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 528, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1394, in run_script
execfile(script_filename, namespace, namespace)
File "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.3.0-py2.7.egg/EGG-INFO/scripts/minindn", line 67, in
from mininet.examples.cluster import MininetCluster, RoundRobinPlacer, ClusterCleanup
ImportError: No module named cluster

Thank you in advance.

Imen

When I want to complie NLSR with the order below：
mini-ndn/ndn-src/NLSR$ sudo -E -u root ./waf
it shows ：

Waf: Entering directory `/home/wwz/mini-ndn-demo/mini-ndn/ndn-src/NLSR/build'
[ 8/42] Compiling src/hello-protocol.cpp
../src/hello-protocol.cpp: In member function ‘void nlsr::HelloProtocol::onContent(const ndn::Interest&, const ndn::Data&)’:
../src/hello-protocol.cpp:191:25: warning: ‘ndn::Signature ndn::Data::getSignature() const’ is deprecated: use getSignatureInfo and getSignatureValue [-Wdeprecated-declarations]
if (data.getSignature().hasKeyLocator() &&
^
In file included from /usr/local/include/ndn-cxx/face.hpp:25:0,
from ../src/adjacent.hpp:25,
from ../src/adjacency-list.hpp:25,
from ../src/conf-parameter.hpp:28,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
/usr/local/include/ndn-cxx/data.hpp:217:3: note: declared here
getSignature() const;
^~~~~~~~~~~~
../src/hello-protocol.cpp:191:25: error: invalid use of incomplete type ‘class ndn::Signature’
if (data.getSignature().hasKeyLocator() &&
^
In file included from /usr/local/include/ndn-cxx/face.hpp:25:0,
from ../src/adjacent.hpp:25,
from ../src/adjacency-list.hpp:25,
from ../src/conf-parameter.hpp:28,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
/usr/local/include/ndn-cxx/data.hpp:33:7: note: forward declaration of ‘class ndn::Signature’
class Signature;
^~~~~~~~~
../src/hello-protocol.cpp:192:25: warning: ‘ndn::Signature ndn::Data::getSignature() const’ is deprecated: use getSignatureInfo and getSignatureValue [-Wdeprecated-declarations]
data.getSignature().getKeyLocator().getType() == ndn::tlv::Name) {
^
In file included from /usr/local/include/ndn-cxx/face.hpp:25:0,
from ../src/adjacent.hpp:25,
from ../src/adjacency-list.hpp:25,
from ../src/conf-parameter.hpp:28,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
/usr/local/include/ndn-cxx/data.hpp:217:3: note: declared here
getSignature() const;
^~~~~~~~~~~~
../src/hello-protocol.cpp:192:25: error: invalid use of incomplete type ‘class ndn::Signature’
data.getSignature().getKeyLocator().getType() == ndn::tlv::Name) {
^
In file included from /usr/local/include/ndn-cxx/face.hpp:25:0,
from ../src/adjacent.hpp:25,
from ../src/adjacency-list.hpp:25,
from ../src/conf-parameter.hpp:28,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
/usr/local/include/ndn-cxx/data.hpp:33:7: note: forward declaration of ‘class ndn::Signature’
class Signature;
^~~~~~~~~
In file included from ../src/logger.hpp:33:0,
from ../src/conf-parameter.hpp:26,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
../src/hello-protocol.cpp:193:62: warning: ‘ndn::Signature ndn::Data::getSignature() const’ is deprecated: use getSignatureInfo and getSignatureValue [-Wdeprecated-declarations]
NLSR_LOG_DEBUG("Data signed with: " << data.getSignature().getKeyLocator().getName());
^
../src/hello-protocol.cpp:193:5: note: in expansion of macro ‘NLSR_LOG_DEBUG’
NLSR_LOG_DEBUG("Data signed with: " << data.getSignature().getKeyLocator().getName());
^
In file included from /usr/local/include/ndn-cxx/face.hpp:25:0,
from ../src/adjacent.hpp:25,
from ../src/adjacency-list.hpp:25,
from ../src/conf-parameter.hpp:28,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
/usr/local/include/ndn-cxx/data.hpp:217:3: note: declared here
getSignature() const;
^~~~~~~~~~~~
In file included from ../src/logger.hpp:33:0,
from ../src/conf-parameter.hpp:26,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
../src/hello-protocol.cpp:193:62: error: invalid use of incomplete type ‘class ndn::Signature’
NLSR_LOG_DEBUG("Data signed with: " << data.getSignature().getKeyLocator().getName());
^
../src/hello-protocol.cpp:193:5: note: in expansion of macro ‘NLSR_LOG_DEBUG’
NLSR_LOG_DEBUG("Data signed with: " << data.getSignature().getKeyLocator().getName());
^
In file included from /usr/local/include/ndn-cxx/face.hpp:25:0,
from ../src/adjacent.hpp:25,
from ../src/adjacency-list.hpp:25,
from ../src/conf-parameter.hpp:28,
from ../src/hello-protocol.hpp:27,
from ../src/hello-protocol.cpp:21:
/usr/local/include/ndn-cxx/data.hpp:33:7: note: forward declaration of ‘class ndn::Signature’
class Signature;
^~~~~~~~~

Waf: Leaving directory `/home/wwz/mini-ndn-demo/mini-ndn/ndn-src/NLSR/build'
Build failed
-> task in 'nlsr-objects' failed with exit status 1 (run with -v to display more information)

How to solve it ?

Hi,
It occurs some error when i start minindn-wifi and minindn works well. Please help me.

ysy@ysy-ubuntu:/home/minindn-wifi$ sudo minindn --wifi --adhoc
Parse of /usr/local/etc/mini-ndn/wifi/adhoc-topology.conf done.
*** Creating adhoc network
*** Adding controller
c0
*** Adding hosts and stations:
sta1 sta2 sta3 sta4
*** Configuring propagation model...

*** Configuring wifi nodes...
Traceback (most recent call last):
File "/usr/local/bin/minindn", line 4, in
import('pkg_resources').run_script('MiniNDN-WiFi==0.1.0', 'minindn')
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 719, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 1504, in run_script
exec(code, namespace, namespace)
File "/usr/local/lib/python2.7/dist-packages/MiniNDN_WiFi-0.1.0-py2.7.egg/EGG-INFO/scripts/minindn", line 616, in
execute(options)
File "/usr/local/lib/python2.7/dist-packages/MiniNDN_WiFi-0.1.0-py2.7.egg/EGG-INFO/scripts/minindn", line 464, in execute
options.ctime, options.nPings, options.pctTraffic, options.experimentName, options.nlsrSecurity)
File "/usr/local/lib/python2.7/dist-packages/MiniNDN_WiFi-0.1.0-py2.7.egg/ndnwifi/ndnadhoc.py", line 119, in build_adhocnet
adhocnet.configureWifiNodes()
File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.2.0d1-py2.7.egg/mininet/net.py", line 788, in configureWifiNodes
self.stations, self.aps = mininetWiFi.configureWifiNodes(self)
File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.2.0d1-py2.7.egg/mininet/wifiNet.py", line 1063, in configureWifiNodes
cls.configureWirelessLink(mininet.stations, mininet.aps, mininet.cars)
File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.2.0d1-py2.7.egg/mininet/wifiNet.py", line 875, in configureWirelessLink
cls.configureMacAddr(node)
File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.2.0d1-py2.7.egg/mininet/wifiNet.py", line 1037, in configureMacAddr
node.params['mac'][wlan] = node.getMAC(iface)
File "/usr/local/lib/python2.7/dist-packages/mininet_wifi-2.2.0d1-py2.7.egg/mininet/node.py", line 276, in getMAC
debug('%s\n' % mac[0])
IndexError: list index out of range

hi,

There is an experiment which work many times but some time it stop and printing this error:
invalid literal for int() with base 10: 'error while connecting to the forwarder (No such file or directory) ...

I need help to understand this error message.

Thanks in advance,,
Enas

Dear devs,
I have realized that the default value for NFD's log-level is set to NONE (source file nfd.py). I wonder if this is a good choice. In fact, I would have expected to have sth logged (INFO level) at least.
In addition to that, I would indicate in the docs/CONFIG.md that the log-level can be changed in the Configuration file with the attribute "nfd-log-level" in the [nodes] section. Otherwise, users may need some time to figure out if such an attribute/parameter exists.

As always, thank you for your commitment,
Salvatore

P.S. I haven't filled a Pull request, since the changes are minimal.

There are some errors when i use minindn by ndntools. It does not support the command of ndnpoke/ndnpeek. It displays "bash: not found this command". And when i build ndntools by waf, it dispalys some error and building fails.

As I didn’t have the dependencies to install Mini NDN, the used following command to install them from source along with Mini-NDN.
./install.sh -a

Everything installed correctly but In the end, I received one Info stating:
~/mini-ndn
python3: can't open file './testbed_topo_generator.py': [Errno 2] No such file or directory

I have also attached the screenshot of the terminal for reference.
How to solve this error? Where can I find the mentioned file?

I am trying to start nfd from a host in mini-ndn but i am getting an error about a certificate not found

1476225300.296038 FATAL: [NFD] cannot load certfile /tmp/h1/certs/localhost_daemons_nfd.ndncert for authorize[0] [from ../daemon/mgmt/command-authenticator.cpp:105 in void nfd::CommandAuthenticator::processConfig(const ConfigSection&, bool, const string&)] 1476225637.804749 FATAL: [NFD] cannot load certfile /tmp/h1/certs/localhost_daemons_nfd.ndncert for authorize[0] [from ../daemon/mgmt/command-authenticator.cpp:105 in void nfd::CommandAuthenticator::processConfig(const ConfigSection&, bool, const string&)]

my step is as follows:
(1) git clone -b v0.1.1 https://github.com/named-data/mini-ndn/ ,I need to install the version 0.1.1
(2)cd mini-ndn
(3)sudo ./install.sh -mrfti

when i do the third step,some error occur:

cp: can't get"ndn_utils/client.conf.sample" file status(stat): no such file or directory
cp: can't get"ndn_utils/nlsr.conf" file status(stat): no such file or directory
cp: can't get"ndn_utils/topologies/default-topology.conf" file status(stat): no such file or directory
cp: can't get "ndn_utils/topologies/minindn.testbed.conf" file status(stat): no such file or directory
python: can't open file 'setup.py': [Errno 2] No such file or directory

please help me fix this problem,thank you.

Hi again,

When I run minindn with the default topology, a pings c successfully. However, when c pings a, I see the following:

mininet> c ping a
connect: Network is unreachable

But when I use a's IP address, c can reach it:
mininet> c ping 1.0.0.5 -c 1
PING 1.0.0.5 (1.0.0.5) 56(84) bytes of data.
64 bytes from 1.0.0.5: icmp_seq=1 ttl=64 time=20.2 ms

--- 1.0.0.5 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 20.242/20.242/20.242/0.000 ms

Here is the ifconfig output of a and c:
mininet> a ifconfig
a-eth0 Link encap:Ethernet HWaddr 06:3e:95:aa:d7:da
inet addr:1.0.0.1 Bcast:1.0.0.3 Mask:255.255.255.252
inet6 addr: fe80::43e:95ff:feaa:d7da/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2644 (2.6 KB) TX bytes:2816 (2.8 KB)

a-eth1 Link encap:Ethernet HWaddr 8e:ad:ee:03:5e:34
inet addr:1.0.0.5 Bcast:1.0.0.7 Mask:255.255.255.252
inet6 addr: fe80::8cad:eeff:fe03:5e34/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:37 errors:0 dropped:0 overruns:0 frame:0
TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3066 (3.0 KB) TX bytes:2878 (2.8 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:785 errors:0 dropped:0 overruns:0 frame:0
TX packets:785 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3282928 (3.2 MB) TX bytes:3282928 (3.2 MB)

mininet> c ifconfig
c-eth0 Link encap:Ethernet HWaddr b2:71:c0:dc:c5:bf
inet addr:1.0.0.6 Bcast:1.0.0.7 Mask:255.255.255.252
inet6 addr: fe80::b071:c0ff:fedc:c5bf/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33 errors:0 dropped:0 overruns:0 frame:0
TX packets:37 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2878 (2.8 KB) TX bytes:3066 (3.0 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:2062 errors:0 dropped:0 overruns:0 frame:0
TX packets:2062 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3610736 (3.6 MB) TX bytes:3610736 (3.6 MB)

This is affecting my work such that some nlsr updates do not reach other nodes. I'm guessing it has to do with DNS resolution, but I'm unable to find a way around it.

When you type ..../mini-ndn$ nano ndn_utils/topologies/default-topology.conf
You already delete node c,d . How can I add node c,d like original. Thank you!

i don't see any python api for dev to simulate experiments~~
thanks a lot~

Why I can't use ndnping /ndn/a-site/a

Hi Ashlesh,
Good morning!
Could you tell me where this problem may come from?

i know this is not the right place to post such a request but i didnt got help elsewhere. I am new to NDN and I am planning to get started with Ndn . i have an idea of a protocole for ndn archetecture and i dont know the best way to use the tools provided from the community to implement it and possibly compare it with other protocoles. plzz help

Hello everyone.

Can you help me how to traceroute in Mini-NDN, thank you!