From agawande at memphis.edu  Thu Oct  6 08:03:27 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 6 Oct 2016 15:03:27 +0000
Subject: [Mini-NDN] Fw:  mini-ndn RTNETLINK error and ndndump question
In-Reply-To: <BN3PR04MB219686B8016C2E27E5D37526D9C50@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CANc623iguWh=1r88HzCKoa9nDOe30k9t8fznZ+K6M=WsO5mBkQ@mail.gmail.com>
	<BN3PR04MB2196D2E6E05CE15DCF20B5B9D9CE0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CANc623hs1HC2Sd39Tgr2NAuAZm=tJcvZ+eL71jitLR7m_wNTjg@mail.gmail.com>
	<BN3PR04MB219654470F583BB7554ACA35D9C20@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CANc623gahKVpSKn-3+98E+ptWoQaXY1mWsBT0iRs1O2r_6u93g@mail.gmail.com>,
	<BN3PR04MB219686B8016C2E27E5D37526D9C50@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <BN3PR04MB2196D066CAE3D40F24EEB833D9C70@BN3PR04MB2196.namprd04.prod.outlook.com>

Hi all

Just FYI, Mini-NDN does not work with PPAs as of yet. Please use source.

Ashlesh

________________________________
From: Ashlesh Gawande (agawande)
Sent: Tuesday, October 4, 2016 8:46 AM
To: Gaetano Laterza
Subject: Re: [Mini-NDN] mini-ndn RTNETLINK error and ndndump question


>From xterm I think you are connecting to the NFD that is running outside the Mini-NDN nodes. This is because of the bug that xterm does not set $HOME as /tmp/<node-name>. Are you running NFD outside of Mini-NDN?


When you do ps aux | grep nfd it should show you two NFDs, one with config file of a and other with that of b.


But since mininet> a nfd-status does not work I doubt it will show any NFD running.


I have not configured Mini-NDN for use with PPAs - If you install from source it does not require the cert file folder which is giving the FATAL error.


Can you please try to install from source: ndn-cxx, NFD, and NLSR

https://github.com/named-data/ndn-cxx

https://github.com/named-data/NFD

https://github.com/named-data/NLSR
https://github.com/named-data/ndn-tools


(BUT BEFORE THIS MAKE SURE THAT YOU HAVE COMPLETELY REMOVED THE PPA INSTALLS)

Ashlesh

________________________________
From: Gaetano Laterza <g.laterza6 at gmail.com>
Sent: Tuesday, October 4, 2016 2:40:20 AM
To: Ashlesh Gawande (agawande)
Subject: Re: [Mini-NDN] mini-ndn RTNETLINK error and ndndump question

a ping -c 3 1.0.0.2 works, I can normally see packets through tcpdump too.

ndn-cxx:amd64/xenial 0.4.1-ppa1~xenial uptodate
ndn-tools:amd64/xenial 0.3-6-gd230073-ppa1~xenial uptodate
nfd:amd64/xenial 0.4.1-1-g704430c-ppa1~xenial uptodate

I forgot to say that I'm now running
Linux machine 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

About nfd debug logs, I changed my simple.conf file like this:

[nodes]
a: _ nfd-log-level=DEBUG
b: _ nfd-log-level=DEBUG
[links]
a:b

And in /tmp/a/a.log or /tmp/b/b.log I can only see this:

1475565918.612249 INFO: [StrategyChoice] setDefaultStrategy /localhost/nfd/strategy/best-route/%FD%04
1475565918.612484 INFO: [InternalForwarderTransport] [id=0,local=internal://,remote=internal://] Creating transport
1475565918.612507 DEBUG: [InternalClientTransport] connectToForwarder 0x94c8f0
1475565918.612532 INFO: [FaceTable] Added face id=1 remote=internal:// local=internal://
1475565918.613168 DEBUG: [CommandValidator] generated certfile path: /tmp/a/certs/localhost_daemons_nfd.ndncert
1475565918.613187 WARNING: [CommandValidator] Wildcard identity is intended for demo purpose only and SHOULD NOT be used in production environment
1475565918.613196 INFO: [CommandValidator] Giving privilege "faces" to identity wildcard
1475565918.613206 INFO: [CommandValidator] Giving privilege "strategy-choice" to identity wildcard
1475565918.613274 FATAL: [NFD] Unable to open certificate file /tmp/a/certs/localhost_daemons_nfd.ndncert [from ../daemon/mgmt/command-validator.cpp:208 in void nfd::CommandValidator::onConfig(const ConfigSection&, bool, const string&)]

Ps: I noticed that if I type:

mininet> a nfd-status
ERROR: error while connecting to the forwarder (No such file or directory)

While if I type it on an xterm terminal, it works normally.

And about this:

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

One more thing, you say that:


nfdc register /test/pingserver udp4://1.0.0.2:6363<http://1.0.0.2:6363>

FIB and RIB:

FIB:
  /localhost/nfd/rib nexthops={faceid=259 (cost=0)}
  /test/ndnping nexthops={faceid=262 (cost=0)}
  /localhost/nfd nexthops={faceid=1 (cost=0)}

The FIB should show /test/pingserver and not /test/ndnping (same on node b).

I guess you copied some other output for /test/ndnping?

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


Yes, a just copied another output cause I was trying several times while writing the mail, sorry for that.

2016-10-04 2:07 GMT+02:00 Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>>:

So ndnpingserver and ndnping connects to local NFD via unix socket.


For example ndnpingserver would connect to NFD via unix socket file. So any packets it receives would first come through a UDP/TCP face to NFD and then delivered to ndnpingserver. So it should show on ndndump.


So changing unix socket would not solve the problem. Your problem is that ndndump does not capture any packet on the interface of 'a' because none are sent!


ndnpingserver and ndnping running on different nodes must communicate via either TCP or UDP - you don't have to set it (If they are running on the same node they will use a unix socket).


So when you say only face 264 (a local unix face so that local application can communicate with local NFD) works that means ndnping sends interest to local NFD, but NFD cannot forward it further (since non-local face 262 has 0 outgoing interest). Can you ping normally:


mininet> a ping -c3 1.0.0.2


and see if that works? If it does not work then problem is with Mininet installation. Can you post the output of the command when you install Mininet (sudo ./util/install.sh -nv)?


If the normal ping works can you post the version of ndn-cxx, NFD, and ndn-tools? Also post the output for

       mininet>a ifconfig

and mininet>b ifconfig


And the NFD DEBUG logs.


But from what the problem looks like, face 262 should say:

  faceid=262 remote=udp4://1.0.0.2:6363<http://1.0.0.2:6363> local=udp4://1.0.0.1:6363 counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent point-to-point

and not:
  faceid=262 remote=udp4://1.0.0.2:6363<http://1.0.0.2:6363/> local=udp4://192.168.1.98:6363<http://192.168.1.98:6363/> counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent point-to-point

because this looks like that NFD running on a is not aware that the interface is a-eth0 (1.0.0.1) and not your computer's interface (192.168.1.98).


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

One more thing, you say that:


nfdc register /test/pingserver udp4://1.0.0.2:6363<http://1.0.0.2:6363/>

FIB and RIB:

FIB:
  /localhost/nfd/rib nexthops={faceid=259 (cost=0)}
  /test/ndnping nexthops={faceid=262 (cost=0)}
  /localhost/nfd nexthops={faceid=1 (cost=0)}


The FIB should show /test/pingserver and not /test/ndnping (same on node b).

I guess you copied some other output for /test/ndnping?

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


Ashlesh

________________________________
From: Gaetano Laterza <g.laterza6 at gmail.com<mailto:g.laterza6 at gmail.com>>
Sent: Monday, October 3, 2016 4:12:34 PM
To: Ashlesh Gawande (agawande)
Subject: Re: [Mini-NDN] mini-ndn RTNETLINK error and ndndump question

Hi Ashlesh,
I'm sorry to bother you again. Last week I did an answer to the mini-ndn mailing list about ndndump issue. I can't see the flow of Interest/Data packets with ndndump cause I noticed that the ping packets were sent through unix stream channel and not through udp4 channel. How can I use udp4 channel? I'll explain in short what I do.

simple.conf:

[nodes]
a: _
b: _
[links]
a:b

So I have node a (1.0.0.1) and node b (1.0.0.2).

On node a:

nfdc register /test/pingserver udp4://1.0.0.2:6363<http://1.0.0.2:6363>

FIB and RIB:

FIB:
  /localhost/nfd/rib nexthops={faceid=259 (cost=0)}
  /test/ndnping nexthops={faceid=262 (cost=0)}
  /localhost/nfd nexthops={faceid=1 (cost=0)}

RIB:
  /localhost/nfd/rib route={faceid=259 (origin=0 cost=0 ChildInherit)}
  /test/ndnping route={faceid=262 (origin=255 cost=0 ChildInherit)}

face 262:

  faceid=262 remote=udp4://1.0.0.2:6363<http://1.0.0.2:6363> local=udp4://192.168.1.98:6363<http://192.168.1.98:6363> counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent point-to-point

On node b:

ndnpingserver /test/pingserver

Now, if I check FIB and RIB again, I see:

FIB:
  /localhost/nfd/rib nexthops={faceid=259 (cost=0)}
  /test/ndnping nexthops={faceid=262 (cost=0)}
  /localhost/nfd nexthops={faceid=1 (cost=0)}
  /test/pingserver/ping nexthops={faceid=264 (cost=0)}

RIB:
  /localhost/nfd/rib route={faceid=259 (origin=0 cost=0 ChildInherit)}
  /test/pingserver/ping route={faceid=264 (origin=0 cost=0 ChildInherit)}
  /test/ndnping route={faceid=262 (origin=255 cost=0 ChildInherit)}

with face 264:

  faceid=264 remote=fd://29 local=unix:///run/nfd.sock counters={in={1i 0d 430B} out={0i 1d 806B}} local on-demand point-to-point

When I ping from node a with:

ndnping /test/pingserver

Only face 264 works (I can see this from the counters):

  faceid=262 remote=udp4://1.0.0.2:6363<http://1.0.0.2:6363> local=udp4://192.168.1.98:6363<http://192.168.1.98:6363> counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent point-to-point
  faceid=264 remote=fd://29 local=unix:///run/nfd.sock counters={in={1i 7d 1109B} out={7i 1d 1226B}} local on-demand point-to-point

If I destroy the face with faceid 264, a new face automatically comes up when I send a ping packet.

To avoid the creation of faces on unix stream channel, I tried to comment out unix section in nfd.conf file:

;unix
;  {
;    path /var/run/nfd.sock ; Unix stream listener path
;  }

and I tried to change the transport channel in client.conf file too (default value: "transport=unix:///var/run/nfd.sock").

But in the last case I don't know what proper value I can assign to transport, so if I change it nfd doesn't work anymore (and actually I don't know if it is the right way to solve my problem).

How would you do in my case? If you realize the scenario I described, are you able to send packets through udp4 channel? Am I trying to do anything wrong?

Thank you very much for you help!

Regards,

Gaetano.

2016-09-29 22:02 GMT+02:00 Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>>:

What version of Mininet are you using? They recently fixed the RTNETLINK error on Ubuntu 16.04.

You might want to install from source if you haven't: https://github.com/mininet/mininet

If you did install from source and still got this error, I don't think it should affect in any way since the program does not crash.


I am not sure why ndndump is not working. There is one bug for xterm:

https://redmine.named-data.net/issues/3038


In xterm, can you try export HOME=/tmp/<node-name> before running anything?

That should fix it.


If not, next thing you can try is to paste the following in bin/minindn, line 344:

for host in self.net.hosts:
       for intf in host.intfNames():
              ndnDumpOutputFile = "dump.%s_%s" % (intf, str(host.intf(intf).IP()))
              host.cmd("ndndump  -i %s > %s &" % (intf, ndnDumpOutputFile))


Then try to install and run and see in /tmp/<node-name> whether you have dump files that are populated.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Gaetano Laterza <g.laterza6 at gmail.com<mailto:g.laterza6 at gmail.com>>
Sent: Thursday, September 29, 2016 11:34:26 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] mini-ndn RTNETLINK error and ndndump question

Hi all, I'm starting to learn ndn protocol and mini-ndn tool. In particular I'd like to start mini-ndn with a very simple configuration, here the content of my conf file:

$ cat simple.conf
[nodes]
a: _
b: _
[links]
a:b delay=10ms

In short, I'd like to observe the exchange of Interest / Data packets using ndndump.
First of all, I cannot understand an error occurring during links initialization:

$ sudo minindn simple.conf
Parse of simple.conf done.
*** Creating network
*** Adding controller
*** Adding hosts:
a b
*** Adding switches:

*** Adding links:
(10ms delay) *** Error: RTNETLINK answers: No such file or directory
(10ms delay) *** Error: RTNETLINK answers: No such file or directory
(a, b)
*** Configuring hosts
a b
Setup time: 4
*** Starting controller
c0
*** Starting 0 switches

*** Starting CLI:
mininet>

Any idea about the Error: RTNETINK answers: No such file or directory?
Here my system information:

$ uname -a
Linux machine 4.1.33-nrj-desktop-1rosa-x86_64 #1 SMP PREEMPT Sun Sep 18 20:20:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

So, going back to the packets exchange, through xterm I typed on node a:

$ ndnpingserver /a
PING SERVER /a

Always on node a, I ran ndndump:

$ ndndump -i a-eth0

So I ran from node b the command:

$ ndnping /a
PING /a
content from /a: seq=2172173333986410181 time=2.51873 ms
content from /a: seq=2172173333986410182 time=0.411503 ms
content from /a: seq=2172173333986410183 time=0.381647 ms
content from /a: seq=2172173333986410184 time=0.458184 ms
[...]

And on node a I can see:

interest received: seq=2172173333986410181
interest received: seq=2172173333986410182
interest received: seq=2172173333986410183
interest received: seq=2172173333986410184
[...]

But ndndump doesn't show any packet. Why? I also tried with:

$ tcpdump -i a-eth0 -v

But when I stop it, the result is:

0 packets captured
0 packets received by filter
0 packets dropped by kernel

Thank you in advance for your help!
Regards,
Gaetano.


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

From sepehrabdous at yahoo.com  Wed Oct 12 13:29:04 2016
From: sepehrabdous at yahoo.com (Sepehr Abdous)
Date: Wed, 12 Oct 2016 20:29:04 +0000 (UTC)
Subject: [Mini-NDN] mininet error
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
Message-ID: <385037240.528537.1476304144517@mail.yahoo.com>

Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/mini-ndn/blob/master/INSTALL.md
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use 
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it??Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail: sepehrabdous1375 at gmail.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/20161012/9ffb0134/attachment.html>

From shijunxiao at email.arizona.edu  Wed Oct 12 15:51:27 2016
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Wed, 12 Oct 2016 15:51:27 -0700
Subject: [Mini-NDN] mininet error
In-Reply-To: <385037240.528537.1476304144517@mail.yahoo.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
Message-ID: <CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>

Hi Sepehr

The kernel might be missing some modules. Use Vagrant ubuntu/trusty64
template, which is known to work properly.

Yours, Junxiao

On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous <sepehrabdous at yahoo.com>
wrote:

> Hello All,
> I've tried to install mini-ndn by following steps in
> https://github.com/named-data/mini-ndn/blob/master/INSTALL.md
> and in one aspect, it requires installing mini_net,
> again I follow the exact steps stated but when I try to use
> sudo mn --test pingall
> to see if it works well...
> I encounter this error:
> Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK
> answers: Operation not supported
> do you have any idea how can I handle it?
>
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Gmail: sepehrabdous1375 at gmail.com <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/20161012/d1057fff/attachment.html>

From agawande at memphis.edu  Thu Oct 13 07:48:43 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 13 Oct 2016 14:48:43 +0000
Subject: [Mini-NDN] mininet error
In-Reply-To: <CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>,
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
Message-ID: <BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>

Junxiao is probably correct, can you give your operating system details?


Can you please detail the steps you followed to install Mininet?


Can you also go to the Mininet folder and try:

sudo ./util/install.sh -nv

and see if there are any errors?


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Wednesday, October 12, 2016 5:51:27 PM
To: Sepehr Abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

Hi Sepehr

The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.

Yours, Junxiao

On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous <sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>> wrote:
Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/mini-ndn/blob/master/INSTALL.md
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it?

Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Gmail: sepehrabdous1375 at gmail.com<mailto:sepehrabdous at yahoo.com>
Cellphone:+989194030591<tel:%2B989194030591>
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/20161013/b546ff7e/attachment.html>

From sepehrabdous at yahoo.com  Thu Oct 13 08:17:41 2016
From: sepehrabdous at yahoo.com (Sepehr Abdous)
Date: Thu, 13 Oct 2016 15:17:41 +0000 (UTC)
Subject: [Mini-NDN] mininet error
In-Reply-To: <CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
Message-ID: <1287709919.241788.1476371861426@mail.yahoo.com>

thank?you, btw I was wondering if you could guide me how to fix this problem on my current?version of ubuntu (16.04.1) and kernel version of 4.4.23(do I have to install another version of ubuntu? if so, which version is the best fit?for?minindn?)?Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail: sepehrabdous1375 at gmail.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran 

    On Thursday, October 13, 2016 2:22 AM, Junxiao Shi <shijunxiao at email.arizona.edu> wrote:
 

 Hi Sepehr
The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.
Yours, Junxiao
On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous <sepehrabdous at yahoo.com> wrote:

Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/ mini-ndn/blob/master/INSTALL.m d
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use 
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it??Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail: sepehrabdous1375 at gmail.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/20161013/b88351a0/attachment.html>

From sepehrabdous at yahoo.com  Thu Oct 13 08:22:13 2016
From: sepehrabdous at yahoo.com (Sepehr Abdous)
Date: Thu, 13 Oct 2016 15:22:13 +0000 (UTC)
Subject: [Mini-NDN] mininet error
In-Reply-To: <BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
	<BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <237666377.239340.1476372133887@mail.yahoo.com>

mu ubuntu version is 16.04.1and kernel version 4.4.23
I used steps stated in http://mininet.org/download/#option-3-installation-from-packages option 2
I used the command:sudo ./util/install.sh -nvand no error occured !?Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail: sepehrabdous1375 at gmail.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran 

    On Thursday, October 13, 2016 6:18 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:
 

 #yiv7685248059 #yiv7685248059 -- P {margin-top:0;margin-bottom:0;}#yiv7685248059 Junxiao is probably correct, can you give?your?operating system details?
Can you please detail the steps you followed to install Mininet?
Can you also?go to the Mininet folder and try:sudo ./util/install.sh -nvand see if there are any errors?
AshleshFrom: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Wednesday, October 12, 2016 5:51:27 PM
To: Sepehr Abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error?Hi Sepehr
The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.
Yours, Junxiao
On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous <sepehrabdous at yahoo.com> wrote:

Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/ mini-ndn/blob/master/INSTALL.m d
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use 
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it??Sepehr Abdous
Faculty:abdous at ce.sharif.edu
Gmail:sepehrabdous1375 at gmail.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/20161013/aaaabc53/attachment.html>

From agawande at memphis.edu  Thu Oct 13 08:28:49 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 13 Oct 2016 15:28:49 +0000
Subject: [Mini-NDN] mininet error
In-Reply-To: <237666377.239340.1476372133887@mail.yahoo.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
	<BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<237666377.239340.1476372133887@mail.yahoo.com>
Message-ID: <BN3PR04MB2196A2FDA517E0EE46263BDED9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>

Can you post the complete output of the following:

sudo mn

?


Does "sudo minindn" also fail?


You are using Mininet from github source, right?

(https://github.com/mininet/mininet)


Ashlesh

________________________________
From: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:22:13 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

mu ubuntu version is 16.04.1
and kernel version 4.4.23

I used steps stated in http://mininet.org/download/#option-3-installation-from-packages option 2

I used the command:
sudo ./util/install.sh -nv
and no error occured !

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


On Thursday, October 13, 2016 6:18 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


Junxiao is probably correct, can you give your operating system details?

Can you please detail the steps you followed to install Mininet?

Can you also go to the Mininet folder and try:
sudo ./util/install.sh -nv
and see if there are any errors?

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Wednesday, October 12, 2016 5:51:27 PM
To: Sepehr Abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

Hi Sepehr

The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.

Yours, Junxiao

On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous <sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>> wrote:
Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/ mini-ndn/blob/master/INSTALL.m d<https://github.com/named-data/mini-ndn/blob/master/INSTALL.md>
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it?

Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Gmail: sepehrabdous1375 at gmail.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/20161013/872e3a9c/attachment.html>

From sepehrabdous at yahoo.com  Thu Oct 13 08:41:53 2016
From: sepehrabdous at yahoo.com (Sepehr Abdous)
Date: Thu, 13 Oct 2016 15:41:53 +0000 (UTC)
Subject: [Mini-NDN] mininet error
In-Reply-To: <BN3PR04MB2196A2FDA517E0EE46263BDED9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
	<BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<237666377.239340.1476372133887@mail.yahoo.com>
	<BN3PR04MB2196A2FDA517E0EE46263BDED9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <1867698237.266861.1476373313740@mail.yahoo.com>

when I write sudo mn I get the following error:# mn
Traceback (most recent call last):
? File "/usr/local/bin/mn", line 4, in <module>
??? __import__('pkg_resources').run_script('mininet===2.3.0d1', 'mn')
? 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 1496, in run_script
??? raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'mn'

and when I write sudo minindn, I get the following:
# minindn
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:
Traceback (most recent call last):
? File "/usr/local/bin/minindn", line 4, in <module>
??? __import__('pkg_resources').run_script('Mini-NDN==0.2.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/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 400, in <module>
??? execute(options)
? File "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 282, in execute
??? net = Mininet(topo,host=NdnHost,link=TCLink)
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 172, in __init__
??? self.build()
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 500, in build
??? self.buildFromTopo( self.topo )
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 487, in buildFromTopo
??? self.addLink( **params )
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 398, in addLink
??? link = cls( node1, node2, **options )
? File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 561, in __init__
??? params2=params )
? File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 451, in __init__
??? node1, node2, deleteIntfs=False )
? File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 495, in makeIntfPair
??? deleteIntfs=deleteIntfs )
? File "/home/sepehr/mini-ndn/mininet/mininet/util.py", line 195, in makeIntfPair
??? ( intf1, intf2, cmdOutput ) )
Exception: Error creating interface pair (a-eth0,b-eth0): RTNETLINK answers: Operation not supported

?Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail: sepehrabdous1375 at gmail.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran 

    On Thursday, October 13, 2016 6:58 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:
 

 #yiv1050315554 #yiv1050315554 -- P {margin-top:0;margin-bottom:0;}#yiv1050315554 Can you post the complete output of the following:sudo mn?
Does "sudo minindn" also fail?
You are using Mininet from github source, right?(https://github.com/mininet/mininet)
AshleshFrom: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:22:13 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error?mu ubuntu version is 16.04.1and kernel version 4.4.23
I used steps stated inhttp://mininet.org/download/#option-3-installation-from-packages option 2
I used the command:sudo ./util/install.sh -nvand no error occured !?Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail:sepehrabdous1375 at gmail.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran

On Thursday, October 13, 2016 6:18 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


#yiv1050315554 -- P {margin-top:0;margin-bottom:0;}#yiv1050315554 Junxiao is probably correct, can you give?your?operating system details?
Can you please detail the steps you followed to install Mininet?
Can you also?go to the Mininet folder and try:sudo ./util/install.sh -nvand see if there are any errors?
AshleshFrom: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Wednesday, October 12, 2016 5:51:27 PM
To: Sepehr Abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error?Hi Sepehr
The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.
Yours, Junxiao
On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous<sepehrabdous at yahoo.com> wrote:

Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/ mini-ndn/blob/master/INSTALL.m d
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use 
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it??Sepehr Abdous
Faculty:abdous at ce.sharif.edu
Gmail:sepehrabdous1375 at gmail.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/20161013/d29f3ad2/attachment.html>

From agawande at memphis.edu  Thu Oct 13 08:57:30 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Thu, 13 Oct 2016 15:57:30 +0000
Subject: [Mini-NDN] mininet error
In-Reply-To: <1867698237.266861.1476373313740@mail.yahoo.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
	<BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<237666377.239340.1476372133887@mail.yahoo.com>
	<BN3PR04MB2196A2FDA517E0EE46263BDED9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<1867698237.266861.1476373313740@mail.yahoo.com>
Message-ID: <BN3PR04MB2196CC1CC633A32B9008E4D8D9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>

Can you attach the output for sudo ./util/install.sh -nv?


Don't know why it cannot find mn.


Are you running as root user? May be try non-root and use sudo.


Ashlesh

________________________________
From: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:41:53 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

when I write sudo mn I get the following error:
# mn
Traceback (most recent call last):
  File "/usr/local/bin/mn", line 4, in <module>
    __import__('pkg_resources').run_script('mininet===2.3.0d1', 'mn')
  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 1496, in run_script
    raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'mn'

and when I write sudo minindn, I get the following:
# minindn
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:
Traceback (most recent call last):
  File "/usr/local/bin/minindn", line 4, in <module>
    __import__('pkg_resources').run_script('Mini-NDN==0.2.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/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 400, in <module>
    execute(options)
  File "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 282, in execute
    net = Mininet(topo,host=NdnHost,link=TCLink)
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 172, in __init__
    self.build()
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 500, in build
    self.buildFromTopo( self.topo )
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 487, in buildFromTopo
    self.addLink( **params )
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 398, in addLink
    link = cls( node1, node2, **options )
  File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 561, in __init__
    params2=params )
  File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 451, in __init__
    node1, node2, deleteIntfs=False )
  File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 495, in makeIntfPair
    deleteIntfs=deleteIntfs )
  File "/home/sepehr/mini-ndn/mininet/mininet/util.py", line 195, in makeIntfPair
    ( intf1, intf2, cmdOutput ) )
Exception: Error creating interface pair (a-eth0,b-eth0): RTNETLINK answers: Operation not supported


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


On Thursday, October 13, 2016 6:58 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


Can you post the complete output of the following:
sudo mn
?

Does "sudo minindn" also fail?

You are using Mininet from github source, right?
(https://github.com/mininet/mininet)

Ashlesh
________________________________
From: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:22:13 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

mu ubuntu version is 16.04.1
and kernel version 4.4.23

I used steps stated in http://mininet.org/download/#option-3-installation-from-packages option 2

I used the command:
sudo ./util/install.sh -nv
and no error occured !

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


On Thursday, October 13, 2016 6:18 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


Junxiao is probably correct, can you give your operating system details?

Can you please detail the steps you followed to install Mininet?

Can you also go to the Mininet folder and try:
sudo ./util/install.sh -nv
and see if there are any errors?

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Wednesday, October 12, 2016 5:51:27 PM
To: Sepehr Abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

Hi Sepehr

The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.

Yours, Junxiao

On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous <sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>> wrote:
Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/ mini-ndn/blob/master/INSTALL.m d<https://github.com/named-data/mini-ndn/blob/master/INSTALL.md>
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it?

Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Gmail: sepehrabdous1375 at gmail.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/20161013/6eeeb175/attachment.html>

From sepehrabdous at yahoo.com  Thu Oct 13 09:05:43 2016
From: sepehrabdous at yahoo.com (Sepehr Abdous)
Date: Thu, 13 Oct 2016 16:05:43 +0000 (UTC)
Subject: [Mini-NDN] mininet error
In-Reply-To: <BN3PR04MB2196CC1CC633A32B9008E4D8D9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
	<BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<237666377.239340.1476372133887@mail.yahoo.com>
	<BN3PR04MB2196A2FDA517E0EE46263BDED9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<1867698237.266861.1476373313740@mail.yahoo.com>
	<BN3PR04MB2196CC1CC633A32B9008E4D8D9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <506962800.280550.1476374743276@mail.yahoo.com>

the output is:# mininet/util/install.sh -nv
Detected Linux distribution: Ubuntu 16.04 xenial amd64
Ubuntu
Installing Mininet dependencies
Reading package lists...
Building dependency tree...
Reading state information...
ethtool is already the newest version (1:4.5-1).
gcc is already the newest version (4:5.3.1-1ubuntu1).
iproute is already the newest version (1:4.3.0-1ubuntu3).
make is already the newest version (4.1-6).
psmisc is already the newest version (22.21-2.1build1).
python-setuptools is already the newest version (20.7.0-1).
telnet is already the newest version (0.17-40).
xterm is already the newest version (322-1ubuntu1).
cgroup-bin is already the newest version (0.41-7ubuntu1).
help2man is already the newest version (1.47.3).
iperf is already the newest version (2.0.5+dfsg1-2).
pep8 is already the newest version (1.7.0-2).
pyflakes is already the newest version (1.1.0-2).
pylint is already the newest version (1.5.2-1ubuntu1).
python-pexpect is already the newest version (4.0.1-1).
socat is already the newest version (1.7.3.1-1).
ssh is already the newest version (1:7.2p2-4ubuntu2.1).
The following packages were automatically installed and are no longer required:
? linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic
? linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Installing Mininet core
~/mini-ndn/mininet ~/mini-ndn
install mnexec /usr/bin
install mn.1 mnexec.1 /usr/share/man/man1
python setup.py install
/usr/lib/python2.7/dist-packages/setuptools/dist.py:294: UserWarning: The version specified ('2.3.0d1') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
? "details." % self.metadata.version
running install
running bdist_egg
running egg_info
writing requirements to mininet.egg-info/requires.txt
writing mininet.egg-info/PKG-INFO
writing top-level names to mininet.egg-info/top_level.txt
writing dependency_links to mininet.egg-info/dependency_links.txt
reading manifest file 'mininet.egg-info/SOURCES.txt'
writing manifest file 'mininet.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/topolib.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/moduledeps.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/net.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/node.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/__init__.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/link.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/term.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/cli.py -> build/bdist.linux-x86_64/egg/mininet
creating build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clusterperf.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/emptynet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/controllers.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multilink.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/natnet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/scratchnetuser.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/__init__.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multitest.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/vlanhost.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clusterSanity.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/simpleperf.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multiping.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/cpu.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/linearbandwidth.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/popenpoll.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/numberedports.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/bind.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multipoll.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/nat.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/intfoptions.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/limit.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/treeping64.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/popen.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/mobility.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/sshd.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/tree1024.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/controllers2.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/miniedit.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clustercli.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/controlnet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/scratchnet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/cluster.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/linuxrouter.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/consoles.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/baresshd.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clusterdemo.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/hwintf.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/clean.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/topo.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/nodelib.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/log.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/util.py -> build/bdist.linux-x86_64/egg/mininet
byte-compiling build/bdist.linux-x86_64/egg/mininet/topolib.py to topolib.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/moduledeps.py to moduledeps.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/net.py to net.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/node.py to node.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/link.py to link.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/term.py to term.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/cli.py to cli.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clusterperf.py to clusterperf.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/emptynet.py to emptynet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/controllers.py to controllers.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multilink.py to multilink.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/natnet.py to natnet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/scratchnetuser.py to scratchnetuser.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multitest.py to multitest.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/vlanhost.py to vlanhost.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clusterSanity.py to clusterSanity.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/simpleperf.py to simpleperf.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multiping.py to multiping.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/cpu.py to cpu.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/linearbandwidth.py to linearbandwidth.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/popenpoll.py to popenpoll.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/numberedports.py to numberedports.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/bind.py to bind.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multipoll.py to multipoll.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/nat.py to nat.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/intfoptions.py to intfoptions.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/limit.py to limit.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/treeping64.py to treeping64.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/popen.py to popen.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/mobility.py to mobility.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/sshd.py to sshd.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/tree1024.py to tree1024.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/controllers2.py to controllers2.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/miniedit.py to miniedit.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clustercli.py to clustercli.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/controlnet.py to controlnet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/scratchnet.py to scratchnet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/cluster.py to cluster.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/linuxrouter.py to linuxrouter.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/consoles.py to consoles.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/baresshd.py to baresshd.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clusterdemo.py to clusterdemo.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/hwintf.py to hwintf.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/clean.py to clean.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/topo.py to topo.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/nodelib.py to nodelib.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/log.py to log.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/util.py to util.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
installing scripts to build/bdist.linux-x86_64/egg/EGG-INFO/scripts
running install_scripts
running build_scripts
creating build/bdist.linux-x86_64/egg/EGG-INFO/scripts
copying build/scripts-2.7/mn -> build/bdist.linux-x86_64/egg/EGG-INFO/scripts
changing mode of build/bdist.linux-x86_64/egg/EGG-INFO/scripts/mn to 755
copying mininet.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
creating 'dist/mininet-2.3.0d1-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing mininet-2.3.0d1-py2.7.egg
Removing /usr/local/lib/python2.7/dist-packages/mininet-2.3.0d1-py2.7.egg
Copying mininet-2.3.0d1-py2.7.egg to /usr/local/lib/python2.7/dist-packages
Removing mininet 2.2.1 from easy-install.pth file
Removing mininet 2.3.0d1 from easy-install.pth file
mininet 2.3.0d1 is already the active version in easy-install.pth
Installing mn script to /usr/local/bin

Installed /usr/local/lib/python2.7/dist-packages/mininet-2.3.0d1-py2.7.egg
Processing dependencies for mininet===2.3.0d1
Searching for setuptools==20.7.0
Best match: setuptools 20.7.0
Adding setuptools 20.7.0 to easy-install.pth file
Installing easy_install script to /usr/local/bin

Using /usr/lib/python2.7/dist-packages
Finished processing dependencies for mininet===2.3.0d1
~/mini-ndn
Installing Open vSwitch...
Reading package lists...
Building dependency tree...
Reading state information...
openvswitch-switch is already the newest version (2.5.0-0ubuntu1).
The following packages were automatically installed and are no longer required:
? linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic
? linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package openvswitch-controller
Attempting to install openvswitch-testcontroller
Reading package lists...
Building dependency tree...
Reading state information...
openvswitch-testcontroller is already the newest version (2.5.0-0ubuntu1).
The following packages were automatically installed and are no longer required:
? linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic
? linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Stopped running controller
insserv: warning: current start runlevel(s) (empty) of script `openvswitch-testcontroller' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `openvswitch-testcontroller' overrides LSB defaults (0 1 6).





yeah I'm pretty sure I'm the root user and not using sudo is because I used sudo -s at first.
?Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail: sepehrabdous1375 at gmail.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran 

    On Thursday, October 13, 2016 7:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:
 

 #yiv3077300356 #yiv3077300356 -- P {margin-top:0;margin-bottom:0;}#yiv3077300356 Can you attach the output for sudo ./util/install.sh -nv?
Don't know why it cannot find mn.
Are you running as root user? May be?try non-root and use sudo.
AshleshFrom: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:41:53 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error?when I write sudo mn I get the following error:# mn
Traceback (most recent call last):
? File "/usr/local/bin/mn", line 4, in <module>
??? __import__('pkg_resources').run_script('mininet===2.3.0d1', 'mn')
? 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 1496, in run_script
??? raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'mn'

and when I write sudo minindn, I get the following:
# minindn
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:
Traceback (most recent call last):
? File "/usr/local/bin/minindn", line 4, in <module>
??? __import__('pkg_resources').run_script('Mini-NDN==0.2.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/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 400, in <module>
??? execute(options)
? File "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 282, in execute
??? net = Mininet(topo,host=NdnHost,link=TCLink)
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 172, in __init__
??? self.build()
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 500, in build
??? self.buildFromTopo( self.topo )
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 487, in buildFromTopo
??? self.addLink( **params )
? File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 398, in addLink
??? link = cls( node1, node2, **options )
? File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 561, in __init__
??? params2=params )
? File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 451, in __init__
??? node1, node2, deleteIntfs=False )
? File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 495, in makeIntfPair
??? deleteIntfs=deleteIntfs )
? File "/home/sepehr/mini-ndn/mininet/mininet/util.py", line 195, in makeIntfPair
??? ( intf1, intf2, cmdOutput ) )
Exception: Error creating interface pair (a-eth0,b-eth0): RTNETLINK answers: Operation not supported

?Sepehr Abdous
Faculty:abdous at ce.sharif.edu
Gmail:sepehrabdous1375 at gmail.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran

On Thursday, October 13, 2016 6:58 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


#yiv3077300356 -- P {margin-top:0;margin-bottom:0;}#yiv3077300356 Can you post the complete output of the following:sudo mn?
Does "sudo minindn" also fail?
You are using Mininet from github source, right?(https://github.com/mininet/mininet)
AshleshFrom: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:22:13 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error?mu ubuntu version is 16.04.1and kernel version 4.4.23
I used steps stated inhttp://mininet.org/download/#option-3-installation-from-packages option 2
I used the command:sudo ./util/install.sh -nvand no error occured !?Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Gmail:sepehrabdous1375 at gmail.com
Cellphone:+989194030591
School of computer engineering
Sharif University of Technology
Tehran, Iran

On Thursday, October 13, 2016 6:18 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


#yiv3077300356 -- P {margin-top:0;margin-bottom:0;}#yiv3077300356 Junxiao is probably correct, can you give?your?operating system details?
Can you please detail the steps you followed to install Mininet?
Can you also?go to the Mininet folder and try:sudo ./util/install.sh -nvand see if there are any errors?
AshleshFrom: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Wednesday, October 12, 2016 5:51:27 PM
To: Sepehr Abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error?Hi Sepehr
The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.
Yours, Junxiao
On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous<sepehrabdous at yahoo.com> wrote:

Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/ mini-ndn/blob/master/INSTALL.m d
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use 
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it??Sepehr Abdous
Faculty:abdous at ce.sharif.edu
Gmail:sepehrabdous1375 at gmail.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/20161013/5236f657/attachment.html>

From agawande at memphis.edu  Thu Oct 13 19:26:46 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 14 Oct 2016 02:26:46 +0000
Subject: [Mini-NDN] mininet error
In-Reply-To: <506962800.280550.1476374743276@mail.yahoo.com>
References: <385037240.528537.1476304144517.ref@mail.yahoo.com>
	<385037240.528537.1476304144517@mail.yahoo.com>
	<CAOFH+OY-y9BoSNh7y_gBNq1aLRC1bKTScsVeKRaR1Z7JXrO2Kw@mail.gmail.com>
	<BN3PR04MB21969952566187272026D17DD9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<237666377.239340.1476372133887@mail.yahoo.com>
	<BN3PR04MB2196A2FDA517E0EE46263BDED9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>
	<1867698237.266861.1476373313740@mail.yahoo.com>
	<BN3PR04MB2196CC1CC633A32B9008E4D8D9DC0@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<506962800.280550.1476374743276@mail.yahoo.com>
Message-ID: <SN2PR04MB2205A7EEAFFC32BC0E53BC0CD9DF0@SN2PR04MB2205.namprd04.prod.outlook.com>

Hmm that looks correct - thats close to what I get.


But you seem to have Mininet 2.2.1 installed as well, which it tries to remove:

"Removing mininet 2.2.1 from easy-install.pth file"

Maybe it does not remove it successfully if it says that every time you try to install.


Did you install Mininet from apt-get (or ppa)? If so can you try to remove it and then reinstall from source.


Once you run mn successfully, minindn should work.


Also, do you have any special python environment?


Ashlesh

________________________________
From: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 11:05:43 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

the output is:
# mininet/util/install.sh -nv
Detected Linux distribution: Ubuntu 16.04 xenial amd64
Ubuntu
Installing Mininet dependencies
Reading package lists...
Building dependency tree...
Reading state information...
ethtool is already the newest version (1:4.5-1).
gcc is already the newest version (4:5.3.1-1ubuntu1).
iproute is already the newest version (1:4.3.0-1ubuntu3).
make is already the newest version (4.1-6).
psmisc is already the newest version (22.21-2.1build1).
python-setuptools is already the newest version (20.7.0-1).
telnet is already the newest version (0.17-40).
xterm is already the newest version (322-1ubuntu1).
cgroup-bin is already the newest version (0.41-7ubuntu1).
help2man is already the newest version (1.47.3).
iperf is already the newest version (2.0.5+dfsg1-2).
pep8 is already the newest version (1.7.0-2).
pyflakes is already the newest version (1.1.0-2).
pylint is already the newest version (1.5.2-1ubuntu1).
python-pexpect is already the newest version (4.0.1-1).
socat is already the newest version (1.7.3.1-1).
ssh is already the newest version (1:7.2p2-4ubuntu2.1).
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic
  linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Installing Mininet core
~/mini-ndn/mininet ~/mini-ndn
install mnexec /usr/bin
install mn.1 mnexec.1 /usr/share/man/man1
python setup.py install
/usr/lib/python2.7/dist-packages/setuptools/dist.py:294: UserWarning: The version specified ('2.3.0d1') is an invalid version, this may not work as expected with newer versions of setuptools, pip, and PyPI. Please see PEP 440 for more details.
  "details." % self.metadata.version
running install
running bdist_egg
running egg_info
writing requirements to mininet.egg-info/requires.txt
writing mininet.egg-info/PKG-INFO
writing top-level names to mininet.egg-info/top_level.txt
writing dependency_links to mininet.egg-info/dependency_links.txt
reading manifest file 'mininet.egg-info/SOURCES.txt'
writing manifest file 'mininet.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/topolib.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/moduledeps.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/net.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/node.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/__init__.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/link.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/term.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/cli.py -> build/bdist.linux-x86_64/egg/mininet
creating build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clusterperf.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/emptynet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/controllers.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multilink.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/natnet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/scratchnetuser.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/__init__.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multitest.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/vlanhost.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clusterSanity.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/simpleperf.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multiping.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/cpu.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/linearbandwidth.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/popenpoll.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/numberedports.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/bind.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/multipoll.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/nat.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/intfoptions.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/limit.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/treeping64.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/popen.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/mobility.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/sshd.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/tree1024.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/controllers2.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/miniedit.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clustercli.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/controlnet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/scratchnet.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/cluster.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/linuxrouter.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/consoles.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/baresshd.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/clusterdemo.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/examples/hwintf.py -> build/bdist.linux-x86_64/egg/mininet/examples
copying build/lib.linux-x86_64-2.7/mininet/clean.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/topo.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/nodelib.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/log.py -> build/bdist.linux-x86_64/egg/mininet
copying build/lib.linux-x86_64-2.7/mininet/util.py -> build/bdist.linux-x86_64/egg/mininet
byte-compiling build/bdist.linux-x86_64/egg/mininet/topolib.py to topolib.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/moduledeps.py to moduledeps.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/net.py to net.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/node.py to node.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/link.py to link.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/term.py to term.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/cli.py to cli.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clusterperf.py to clusterperf.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/emptynet.py to emptynet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/controllers.py to controllers.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multilink.py to multilink.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/natnet.py to natnet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/scratchnetuser.py to scratchnetuser.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multitest.py to multitest.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/vlanhost.py to vlanhost.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clusterSanity.py to clusterSanity.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/simpleperf.py to simpleperf.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multiping.py to multiping.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/cpu.py to cpu.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/linearbandwidth.py to linearbandwidth.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/popenpoll.py to popenpoll.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/numberedports.py to numberedports.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/bind.py to bind.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/multipoll.py to multipoll.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/nat.py to nat.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/intfoptions.py to intfoptions.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/limit.py to limit.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/treeping64.py to treeping64.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/popen.py to popen.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/mobility.py to mobility.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/sshd.py to sshd.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/tree1024.py to tree1024.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/controllers2.py to controllers2.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/miniedit.py to miniedit.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clustercli.py to clustercli.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/controlnet.py to controlnet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/scratchnet.py to scratchnet.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/cluster.py to cluster.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/linuxrouter.py to linuxrouter.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/consoles.py to consoles.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/baresshd.py to baresshd.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/clusterdemo.py to clusterdemo.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/examples/hwintf.py to hwintf.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/clean.py to clean.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/topo.py to topo.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/nodelib.py to nodelib.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/log.py to log.pyc
byte-compiling build/bdist.linux-x86_64/egg/mininet/util.py to util.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
installing scripts to build/bdist.linux-x86_64/egg/EGG-INFO/scripts
running install_scripts
running build_scripts
creating build/bdist.linux-x86_64/egg/EGG-INFO/scripts
copying build/scripts-2.7/mn -> build/bdist.linux-x86_64/egg/EGG-INFO/scripts
changing mode of build/bdist.linux-x86_64/egg/EGG-INFO/scripts/mn to 755
copying mininet.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying mininet.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
zip_safe flag not set; analyzing archive contents...
creating 'dist/mininet-2.3.0d1-py2.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing mininet-2.3.0d1-py2.7.egg
Removing /usr/local/lib/python2.7/dist-packages/mininet-2.3.0d1-py2.7.egg
Copying mininet-2.3.0d1-py2.7.egg to /usr/local/lib/python2.7/dist-packages
Removing mininet 2.2.1 from easy-install.pth file
Removing mininet 2.3.0d1 from easy-install.pth file
mininet 2.3.0d1 is already the active version in easy-install.pth
Installing mn script to /usr/local/bin

Installed /usr/local/lib/python2.7/dist-packages/mininet-2.3.0d1-py2.7.egg
Processing dependencies for mininet===2.3.0d1
Searching for setuptools==20.7.0
Best match: setuptools 20.7.0
Adding setuptools 20.7.0 to easy-install.pth file
Installing easy_install script to /usr/local/bin

Using /usr/lib/python2.7/dist-packages
Finished processing dependencies for mininet===2.3.0d1
~/mini-ndn
Installing Open vSwitch...
Reading package lists...
Building dependency tree...
Reading state information...
openvswitch-switch is already the newest version (2.5.0-0ubuntu1).
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic
  linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
E: Unable to locate package openvswitch-controller
Attempting to install openvswitch-testcontroller
Reading package lists...
Building dependency tree...
Reading state information...
openvswitch-testcontroller is already the newest version (2.5.0-0ubuntu1).
The following packages were automatically installed and are no longer required:
  linux-headers-4.4.0-31 linux-headers-4.4.0-31-generic
  linux-image-4.4.0-31-generic linux-image-extra-4.4.0-31-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
Stopped running controller
insserv: warning: current start runlevel(s) (empty) of script `openvswitch-testcontroller' overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `openvswitch-testcontroller' overrides LSB defaults (0 1 6).






yeah I'm pretty sure I'm the root user and not using sudo is because I used sudo -s at first.

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


On Thursday, October 13, 2016 7:27 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


Can you attach the output for sudo ./util/install.sh -nv?

Don't know why it cannot find mn.

Are you running as root user? May be try non-root and use sudo.

Ashlesh
________________________________
From: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:41:53 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

when I write sudo mn I get the following error:
# mn
Traceback (most recent call last):
  File "/usr/local/bin/mn", line 4, in <module>
    __import__('pkg_resources').run_script('mininet===2.3.0d1', 'mn')
  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 1496, in run_script
    raise ResolutionError("No script named %r" % script_name)
pkg_resources.ResolutionError: No script named 'mn'

and when I write sudo minindn, I get the following:
# minindn
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:
Traceback (most recent call last):
  File "/usr/local/bin/minindn", line 4, in <module>
    __import__('pkg_resources').run_script('Mini-NDN==0.2.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/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 400, in <module>
    execute(options)
  File "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 282, in execute
    net = Mininet(topo,host=NdnHost,link=TCLink)
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 172, in __init__
    self.build()
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 500, in build
    self.buildFromTopo( self.topo )
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 487, in buildFromTopo
    self.addLink( **params )
  File "/home/sepehr/mini-ndn/mininet/mininet/net.py", line 398, in addLink
    link = cls( node1, node2, **options )
  File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 561, in __init__
    params2=params )
  File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 451, in __init__
    node1, node2, deleteIntfs=False )
  File "/home/sepehr/mini-ndn/mininet/mininet/link.py", line 495, in makeIntfPair
    deleteIntfs=deleteIntfs )
  File "/home/sepehr/mini-ndn/mininet/mininet/util.py", line 195, in makeIntfPair
    ( intf1, intf2, cmdOutput ) )
Exception: Error creating interface pair (a-eth0,b-eth0): RTNETLINK answers: Operation not supported


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


On Thursday, October 13, 2016 6:58 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


Can you post the complete output of the following:
sudo mn
?

Does "sudo minindn" also fail?

You are using Mininet from github source, right?
(https://github.com/mininet/mininet)

Ashlesh
________________________________
From: Sepehr Abdous <sepehrabdous at yahoo.com>
Sent: Thursday, October 13, 2016 10:22:13 AM
To: Ashlesh Gawande (agawande); Junxiao Shi
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

mu ubuntu version is 16.04.1
and kernel version 4.4.23

I used steps stated in http://mininet.org/download/#option-3-installation-from-packages option 2

I used the command:
sudo ./util/install.sh -nv
and no error occured !

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


On Thursday, October 13, 2016 6:18 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu> wrote:


Junxiao is probably correct, can you give your operating system details?

Can you please detail the steps you followed to install Mininet?

Can you also go to the Mininet folder and try:
sudo ./util/install.sh -nv
and see if there are any errors?

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Junxiao Shi <shijunxiao at email.arizona.edu>
Sent: Wednesday, October 12, 2016 5:51:27 PM
To: Sepehr Abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] mininet error

Hi Sepehr

The kernel might be missing some modules. Use Vagrant ubuntu/trusty64 template, which is known to work properly.

Yours, Junxiao

On Wed, Oct 12, 2016 at 1:29 PM, Sepehr Abdous <sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>> wrote:
Hello All,
I've tried to install mini-ndn by following steps in https://github.com/named-data/ mini-ndn/blob/master/INSTALL.m d<https://github.com/named-data/mini-ndn/blob/master/INSTALL.md>
and in one aspect, it requires installing mini_net,
again I follow the exact steps stated but when I try to use
sudo mn --test pingall
to see if it works well...
I encounter this error:
Exception: Error creating interface pair (h1-eth0,s1-eth1): RTNETLINK answers: Operation not supported
do you have any idea how can I handle it?

Sepehr Abdous
Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
Gmail: sepehrabdous1375 at gmail.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/20161014/65948ae8/attachment.html>

From sepehrabdous1375 at gmail.com  Fri Oct 21 11:44:40 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Fri, 21 Oct 2016 22:14:40 +0330
Subject: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/> does
 not exist
Message-ID: <CAKaOrig1R2kxWtGRthT-5vcOVuFvnufKCqiswm=JN5624+_9Pg@mail.gmail.com>

Hello,
 I'm kind of new to nlsr and mini-ndn.
I've installed NLSR based on this link:
http://named-data.net/doc/NLSR/current/INSTALL.html
and when I type nlsr in the terminal I get the following error:

Failed to read configuration file: nlsr.conf
Error in configuration file processing! Exiting from NLSR

then I tried this command:
nlsr -f /home/sepehr/NLSR/nlsr.conf

and I got this error:
Provided log directory </var/log/nlsr/> does not exist
Error in configuration file processing! Exiting from NLSR


can you please help me with this problem?

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

From agawande at memphis.edu  Fri Oct 21 11:51:55 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Fri, 21 Oct 2016 18:51:55 +0000
Subject: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/>
 does not exist
In-Reply-To: <CAKaOrig1R2kxWtGRthT-5vcOVuFvnufKCqiswm=JN5624+_9Pg@mail.gmail.com>
References: <CAKaOrig1R2kxWtGRthT-5vcOVuFvnufKCqiswm=JN5624+_9Pg@mail.gmail.com>
Message-ID: <BN3PR04MB21968A80A473B961612869FBD9D40@BN3PR04MB2196.namprd04.prod.outlook.com>

You have to configure nlsr.conf


http://named-data.net/doc/NLSR/current/ROUTER-CONFIG.html


So the folders it uses for logs etc must exist. You can simply change that paths in nlsr.conf


If you run Mini-NDN it will configure for you and you can look in /tmp/<node-name>/nlsr.conf to see how NLSR is configured.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Friday, October 21, 2016 1:44:40 PM
To: mini-ndn at lists.cs.ucla.edu
Subject: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/> does not exist

Hello,
 I'm kind of new to nlsr and mini-ndn.
I've installed NLSR based on this link:
http://named-data.net/doc/NLSR/current/INSTALL.html
and when I type nlsr in the terminal I get the following error:

Failed to read configuration file: nlsr.conf
Error in configuration file processing! Exiting from NLSR

then I tried this command:
nlsr -f /home/sepehr/NLSR/nlsr.conf

and I got this error:
Provided log directory </var/log/nlsr/> does not exist
Error in configuration file processing! Exiting from NLSR


can you please help me with this problem?

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

From sepehrabdous1375 at gmail.com  Fri Oct 21 12:02:27 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Fri, 21 Oct 2016 22:32:27 +0330
Subject: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/>
 does not exist
In-Reply-To: <BN3PR04MB21968A80A473B961612869FBD9D40@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1R2kxWtGRthT-5vcOVuFvnufKCqiswm=JN5624+_9Pg@mail.gmail.com>
	<BN3PR04MB21968A80A473B961612869FBD9D40@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrij-rA+5a4eM8X12ai+rBLkF1uRaa_ARQJWF7O7ZO26-2g@mail.gmail.com>

Thank you for your instant response.
a folder with the name of nlsr.conf exists in the my directory
/home/sepehr/NLSR/
shouldn't I use that one?

On Fri, Oct 21, 2016 at 10:21 PM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> You have to configure nlsr.conf
>
>
> http://named-data.net/doc/NLSR/current/ROUTER-CONFIG.html
>
>
> So the folders it uses for logs etc must exist. You can simply change that
> paths in nlsr.conf
>
>
> If you run Mini-NDN it will configure for you and you can look in
> /tmp/<node-name>/nlsr.conf to see how NLSR is configured.
>
>
> Ashlesh
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr
> abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Friday, October 21, 2016 1:44:40 PM
> *To:* mini-ndn at lists.cs.ucla.edu
> *Subject:* [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/>
> does not exist
>
> Hello,
>  I'm kind of new to nlsr and mini-ndn.
> I've installed NLSR based on this link:
> http://named-data.net/doc/NLSR/current/INSTALL.html
> and when I type nlsr in the terminal I get the following error:
>
> Failed to read configuration file: nlsr.conf
> Error in configuration file processing! Exiting from NLSR
>
> then I tried this command:
> nlsr -f /home/sepehr/NLSR/nlsr.conf
>
> and I got this error:
> Provided log directory </var/log/nlsr/> does not exist
> Error in configuration file processing! Exiting from NLSR
>
>
> can you please help me with this problem?
>
> Thank you
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



-- 
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/20161021/d23050ee/attachment.html>

From sepehrabdous1375 at gmail.com  Sun Oct 23 13:13:53 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Sun, 23 Oct 2016 23:43:53 +0330
Subject: [Mini-NDN] shutting down controller
Message-ID: <CAKaOrijPFbCXc-V3zkW1E6yUg-s+-fttS5tEBO3qUm0OySg++A@mail.gmail.com>

hi I'm new to mini-ndn and when I try to run it I get the following error:

# minindn
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
Traceback (most recent call last):
  File "/usr/local/bin/minindn", line 4, in <module>
    __import__('pkg_resources').run_script('Mini-NDN==0.2.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/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn",
line 400, in <module>
    execute(options)
  File
"/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn",
line 282, in execute
    net = Mininet(topo,host=NdnHost,link=TCLink)
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 172, in __init__
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 500, in build
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 467, in
buildFromTopo
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 283, in
addController
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1554, in
DefaultController
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1376, in
__init__
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1394, in
checkListening
Exception: Please shut down the controller which is running on port 6653:
Active Internet connections (servers and established)
tcp        0      0 0.0.0.0:6653            0.0.0.0:*
LISTEN      1262/ovs-testcontro
tcp        0      0 127.0.0.1:57358         127.0.0.1:6653
TIME_WAIT   -
tcp        0      0 127.0.0.1:57360         127.0.0.1:6653
TIME_WAIT

can you tell me how can I shutdown controller which is running on port 6653

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

From agawande at memphis.edu  Sun Oct 23 13:36:20 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Sun, 23 Oct 2016 20:36:20 +0000
Subject: [Mini-NDN] shutting down controller
Message-ID: <BN3PR04MB21960359DF1238080E9D7856D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>

Can you try sudo mn --clean?

Ashlesh

On Oct 23, 2016 3:14 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
hi I'm new to mini-ndn and when I try to run it I get the following error:

# minindn
Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
*** Creating network
*** Adding controller
Traceback (most recent call last):
  File "/usr/local/bin/minindn", line 4, in <module>
    __import__('pkg_resources').run_script('Mini-NDN==0.2.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/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 400, in <module>
    execute(options)
  File "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 282, in execute
    net = Mininet(topo,host=NdnHost,link=TCLink)
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 172, in __init__
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 500, in build
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 467, in buildFromTopo
  File "build/bdist.linux-x86_64/egg/mininet/net.py", line 283, in addController
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1554, in DefaultController
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1376, in __init__
  File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1394, in checkListening
Exception: Please shut down the controller which is running on port 6653:
Active Internet connections (servers and established)
tcp        0      0 0.0.0.0:6653<http://0.0.0.0:6653>            0.0.0.0:*               LISTEN      1262/ovs-testcontro
tcp        0      0 127.0.0.1:57358<http://127.0.0.1:57358>         127.0.0.1:6653<http://127.0.0.1:6653>          TIME_WAIT   -
tcp        0      0 127.0.0.1:57360<http://127.0.0.1:57360>         127.0.0.1:6653<http://127.0.0.1:6653>          TIME_WAIT

can you tell me how can I shutdown controller which is running on port 6653

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

From sepehrabdous1375 at gmail.com  Sun Oct 23 16:33:51 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Mon, 24 Oct 2016 03:03:51 +0330
Subject: [Mini-NDN] directory </var/log/nlsr/> does not exist
Message-ID: <CAKaOrigm47qmE-GY2t7pH4mxhz-gftJwsVM=mae=9zBH8gHjPw@mail.gmail.com>

Hello,
I'm trying to run nlsr, but when I type nlsr in command line I get the
following error:

Provided log directory </var/log/nlsr/> does not exist
Error in configuration file processing! Exiting from NLSR

can you help me with this error please?
thank you


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

From agawande at memphis.edu  Sun Oct 23 16:36:03 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Sun, 23 Oct 2016 23:36:03 +0000
Subject: [Mini-NDN] directory </var/log/nlsr/> does not exist
Message-ID: <BN3PR04MB2196C3BF38141231467FFC27D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>

You will need to configure nlsr.conf with log directories that exist and neighbors.

Ashlesh

On Oct 23, 2016 6:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
Hello,
I'm trying to run nlsr, but when I type nlsr in command line I get the following error:

Provided log directory </var/log/nlsr/> does not exist
Error in configuration file processing! Exiting from NLSR

can you help me with this error please?
thank you


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

From Matteo.Bertolino at eurecom.fr  Mon Oct 24 00:42:54 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Mon, 24 Oct 2016 09:42:54 +0200
Subject: [Mini-NDN] shutting down controller
In-Reply-To: <BN3PR04MB21960359DF1238080E9D7856D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <BN3PR04MB21960359DF1238080E9D7856D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <20161024094254.jbuq44o8u8o48ggs@webmail.eurecom.fr>

sudo tcpkill -9 port 6633
For 30 seconds at least. If it does not work, re-run 2-3 times until it runs.

This error is explored in my guide. For other similar errors :  
https://github.com/MatteoBertolino92/NDN-matteo/blob/master/ndncxx_miniNDN_someUseCases:%20nacks%2C%20certificates%2C%20interest%20verification.pdf

Yours, Matteo

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

> Can you try sudo mn --clean?
>
> Ashlesh
>
> On Oct 23, 2016 3:14 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
> hi I'm new to mini-ndn and when I try to run it I get the following error:
>
> # minindn
> Parse of /usr/local/etc/mini-ndn/default-topology.conf done.
> *** Creating network
> *** Adding controller
> Traceback (most recent call last):
>   File "/usr/local/bin/minindn", line 4, in <module>
>     __import__('pkg_resources').run_script('Mini-NDN==0.2.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/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 400, in   
> <module>
>     execute(options)
>   File   
> "/usr/local/lib/python2.7/dist-packages/Mini_NDN-0.2.0-py2.7.egg/EGG-INFO/scripts/minindn", line 282, in   
> execute
>     net = Mininet(topo,host=NdnHost,link=TCLink)
>   File "build/bdist.linux-x86_64/egg/mininet/net.py", line 172, in __init__
>   File "build/bdist.linux-x86_64/egg/mininet/net.py", line 500, in build
>   File "build/bdist.linux-x86_64/egg/mininet/net.py", line 467, in   
> buildFromTopo
>   File "build/bdist.linux-x86_64/egg/mininet/net.py", line 283, in   
> addController
>   File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1554, in  
>  DefaultController
>   File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1376, in __init__
>   File "build/bdist.linux-x86_64/egg/mininet/node.py", line 1394, in  
>  checkListening
> Exception: Please shut down the controller which is running on port 6653:
> Active Internet connections (servers and established)
> tcp        0      0 0.0.0.0:6653<http://0.0.0.0:6653>              
> 0.0.0.0:*               LISTEN      1262/ovs-testcontro
> tcp        0      0 127.0.0.1:57358<http://127.0.0.1:57358>           
> 127.0.0.1:6653<http://127.0.0.1:6653>          TIME_WAIT   -
> tcp        0      0 127.0.0.1:57360<http://127.0.0.1:57360>           
> 127.0.0.1:6653<http://127.0.0.1:6653>          TIME_WAIT
>
> can you tell me how can I shutdown controller which is running on port 6653
>
> Thank you
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu<mailto:abdous at ce.sharif.edu>
> Yahoo mail: sepehrabdous at yahoo.com<mailto:sepehrabdous at yahoo.com>
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



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




From sepehrabdous1375 at gmail.com  Mon Oct 24 13:59:07 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Tue, 25 Oct 2016 00:29:07 +0330
Subject: [Mini-NDN] directory </var/log/nlsr/> does not exist
In-Reply-To: <BN3PR04MB2196C3BF38141231467FFC27D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <BN3PR04MB2196C3BF38141231467FFC27D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOriivU_a3A7FXZHJUZ7vu9mc4gTs9pbxvHo1KpFYWFfQAmg@mail.gmail.com>

sorry as I'm new to nlsr
can you be more specific about what I have to do?
what do you mean by log directories that exist in neighbors...?
Thank you

On Mon, Oct 24, 2016 at 3:06 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> You will need to configure nlsr.conf with log directories that exist and
> neighbors.
>
> Ashlesh
> On Oct 23, 2016 6:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com> wrote:
>
> Hello,
> I'm trying to run nlsr, but when I type nlsr in command line I get the
> following error:
>
> Provided log directory </var/log/nlsr/> does not exist
> Error in configuration file processing! Exiting from NLSR
>
> can you help me with this error please?
> thank you
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>
>


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

From agawande at memphis.edu  Mon Oct 24 14:06:04 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 24 Oct 2016 21:06:04 +0000
Subject: [Mini-NDN] directory </var/log/nlsr/> does not exist
In-Reply-To: <CAKaOriivU_a3A7FXZHJUZ7vu9mc4gTs9pbxvHo1KpFYWFfQAmg@mail.gmail.com>
References: <BN3PR04MB2196C3BF38141231467FFC27D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOriivU_a3A7FXZHJUZ7vu9mc4gTs9pbxvHo1KpFYWFfQAmg@mail.gmail.com>
Message-ID: <BN3PR04MB2196BED461DA94B20B551BA4D9A90@BN3PR04MB2196.namprd04.prod.outlook.com>

Have you run Mini-NDN? When you run it (sudo minindn), go and look into /tmp/a/nlsr.conf

and you will find that the log directory is /tmp/a/log/ which exists (check by cd /tmp/a/log).


In /tmp/a/nlsr.conf you will also find the neighbors of 'a' configured in the neighbors section.

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L44


Also look at the router name of 'a' in /tmp/a/nlsr.conf

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L9


If you open /tmp/b/nlsr.conf and look at the neighbors you would find the router name of 'a' configured there.


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

Now when you want to run NLSR independently of Mini-NDN you need to do these changes yourself (manually).

Suppose you have two machines a and b.


Make a new directory where you would want to store the log file of NLSR. Example:

/home/a/NLSR/logs.


Then put this path at:

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L37

and at

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L38


Change "pollux" in https://github.com/named-data/NLSR/blob/master/nlsr.conf#L9

to "a"


And in the neighbors section configure the neighbor b by putting its name and IP and link-cost.


Repeat the same for machine b.


Then you can run NLSR on both the machines who have each others as neighbors.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Monday, October 24, 2016 3:59:07 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] directory </var/log/nlsr/> does not exist

sorry as I'm new to nlsr
can you be more specific about what I have to do?
what do you mean by log directories that exist in neighbors...?
Thank you

On Mon, Oct 24, 2016 at 3:06 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You will need to configure nlsr.conf with log directories that exist and neighbors.

Ashlesh

On Oct 23, 2016 6:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
Hello,
I'm trying to run nlsr, but when I type nlsr in command line I get the following error:

Provided log directory </var/log/nlsr/> does not exist
Error in configuration file processing! Exiting from NLSR

can you help me with this error please?
thank you


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



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

From agawande at memphis.edu  Mon Oct 24 14:10:02 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Mon, 24 Oct 2016 21:10:02 +0000
Subject: [Mini-NDN] directory </var/log/nlsr/> does not exist
In-Reply-To: <BN3PR04MB2196BED461DA94B20B551BA4D9A90@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <BN3PR04MB2196C3BF38141231467FFC27D9D60@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOriivU_a3A7FXZHJUZ7vu9mc4gTs9pbxvHo1KpFYWFfQAmg@mail.gmail.com>,
	<BN3PR04MB2196BED461DA94B20B551BA4D9A90@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <BN3PR04MB21969ACA3574E677F4CFD9C0D9A90@BN3PR04MB2196.namprd04.prod.outlook.com>

You can see a detailed example here:

https://github.com/named-data/NLSR/blob/master/docs/ROUTER-CONFIG.rst


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Ashlesh Gawande (agawande) <agawande at memphis.edu>
Sent: Monday, October 24, 2016 4:06:04 PM
To: sepehr abdous
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] directory </var/log/nlsr/> does not exist


Have you run Mini-NDN? When you run it (sudo minindn), go and look into /tmp/a/nlsr.conf

and you will find that the log directory is /tmp/a/log/ which exists (check by cd /tmp/a/log).


In /tmp/a/nlsr.conf you will also find the neighbors of 'a' configured in the neighbors section.

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L44


Also look at the router name of 'a' in /tmp/a/nlsr.conf

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L9


If you open /tmp/b/nlsr.conf and look at the neighbors you would find the router name of 'a' configured there.


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

Now when you want to run NLSR independently of Mini-NDN you need to do these changes yourself (manually).

Suppose you have two machines a and b.


Make a new directory where you would want to store the log file of NLSR. Example:

/home/a/NLSR/logs.


Then put this path at:

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L37

and at

https://github.com/named-data/NLSR/blob/master/nlsr.conf#L38


Change "pollux" in https://github.com/named-data/NLSR/blob/master/nlsr.conf#L9

to "a"


And in the neighbors section configure the neighbor b by putting its name and IP and link-cost.


Repeat the same for machine b.


Then you can run NLSR on both the machines who have each others as neighbors.


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Monday, October 24, 2016 3:59:07 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] directory </var/log/nlsr/> does not exist

sorry as I'm new to nlsr
can you be more specific about what I have to do?
what do you mean by log directories that exist in neighbors...?
Thank you

On Mon, Oct 24, 2016 at 3:06 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You will need to configure nlsr.conf with log directories that exist and neighbors.

Ashlesh

On Oct 23, 2016 6:34 PM, sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>> wrote:
Hello,
I'm trying to run nlsr, but when I type nlsr in command line I get the following error:

Provided log directory </var/log/nlsr/> does not exist
Error in configuration file processing! Exiting from NLSR

can you help me with this error please?
thank you


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



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

From Matteo.Bertolino at eurecom.fr  Tue Oct 25 07:53:13 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Tue, 25 Oct 2016 16:53:13 +0200
Subject: [Mini-NDN] Mininet: connection refused
Message-ID: <20161025165313.965m178rtw480g4g@webmail.eurecom.fr>

Good morning,
I've to run an NDN node on miniNDN, but this ndn node at a certain  
time should perform a network operation like an http connection, a  
wget, a ping etc.
I obtain two kind of error:
1- Connection refused (when I try to connect the special ndn node to  
an http server)
2- Network unreachable (for example, when I try a wget or to ping the  
other node).

Do you have a solution?
Thanks,
Matteo

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



From agawande at memphis.edu  Tue Oct 25 08:09:26 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Tue, 25 Oct 2016 15:09:26 +0000
Subject: [Mini-NDN] Mininet: connection refused
In-Reply-To: <20161025165313.965m178rtw480g4g@webmail.eurecom.fr>
References: <20161025165313.965m178rtw480g4g@webmail.eurecom.fr>
Message-ID: <BN3PR04MB219672DA7FD31B40CB8D44E9D9A80@BN3PR04MB2196.namprd04.prod.outlook.com>

For reaching the Internet:

https://github.com/mininet/mininet/wiki/FAQ#NAT

You will have to experiment how to integrate NAT with Mini-NDN.


In Mini-NDN you can't ping non-neighbors because there is no routing.

Need to use route command to set it up.

https://redmine.named-data.net/issues/3054


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Tuesday, October 25, 2016 9:53:13 AM
To: mini-ndn at lists.cs.ucla.edu
Cc: ndn-interest at lists.cs.ucla.edu
Subject: [Mini-NDN] Mininet: connection refused

Good morning,
I've to run an NDN node on miniNDN, but this ndn node at a certain
time should perform a network operation like an http connection, a
wget, a ping etc.
I obtain two kind of error:
1- Connection refused (when I try to connect the special ndn node to
an http server)
2- Network unreachable (for example, when I try a wget or to ping the
other node).

Do you have a solution?
Thanks,
Matteo

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

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

From lanwang at memphis.edu  Tue Oct 25 08:30:06 2016
From: lanwang at memphis.edu (Lan Wang (lanwang))
Date: Tue, 25 Oct 2016 15:30:06 +0000
Subject: [Mini-NDN] Mininet: connection refused
In-Reply-To: <BN3PR04MB219672DA7FD31B40CB8D44E9D9A80@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <20161025165313.965m178rtw480g4g@webmail.eurecom.fr>
	<BN3PR04MB219672DA7FD31B40CB8D44E9D9A80@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <69C9B954-99A6-4806-85D8-8E90BFF1AD3F@memphis.edu>



On Oct 25, 2016, at 10:09 AM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

For reaching the Internet:
https://github.com/mininet/mininet/wiki/FAQ#NAT
You will have to experiment how to integrate NAT with Mini-NDN.


In Mini-NDN you can't ping non-neighbors because there is no routing.

Just want to clarify that this is because *IP* routing is not running in Mini-NDN.  If you run some form of IP routing (eg RIP or OSPF) then you can ping non-neighbors.

We do run NLSR in Mini-NDN so you can do ndnping.

Need to use route command to set it up.
https://redmine.named-data.net/issues/3054

Ashlesh
________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Matteo Bertolino <Matteo.Bertolino at eurecom.fr<mailto:Matteo.Bertolino at eurecom.fr>>
Sent: Tuesday, October 25, 2016 9:53:13 AM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Cc: ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>
Subject: [Mini-NDN] Mininet: connection refused

Good morning,
I've to run an NDN node on miniNDN, but this ndn node at a certain
time should perform a network operation like an http connection, a
wget, a ping etc.
I obtain two kind of error:
1- Connection refused (when I try to connect the special ndn node to
an http server)
2- Network unreachable (for example, when I try a wget or to ping the
other node).

Do you have a solution?
Thanks,
Matteo

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

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

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

From Matteo.Bertolino at eurecom.fr  Tue Oct 25 09:33:32 2016
From: Matteo.Bertolino at eurecom.fr (Matteo Bertolino)
Date: Tue, 25 Oct 2016 18:33:32 +0200
Subject: [Mini-NDN] Mininet: connection refused
In-Reply-To: <69C9B954-99A6-4806-85D8-8E90BFF1AD3F@memphis.edu>
References: <20161025165313.965m178rtw480g4g@webmail.eurecom.fr>
	<BN3PR04MB219672DA7FD31B40CB8D44E9D9A80@BN3PR04MB2196.namprd04.prod.outlook.com>
	<69C9B954-99A6-4806-85D8-8E90BFF1AD3F@memphis.edu>
Message-ID: <20161025183332.f58x2on38k00kgos@webmail.eurecom.fr>

Dears,
thank you for the interest. I have still some questions unsolved.

1- The sentence:
> You will have to experiment how to integrate NAT with Mini-NDN.
Does it mean that this feature is not available now? I have no idea  
how to integrate miniNDN with nat. In mininet I see --nat option, but  
here it does not work.

2- However, also writing mn --nat , the command h1 ping google.fr fails.

3- The sentence:
> If you run some form of IP routing (eg RIP or OSPF) then you can  
> ping non-neighbors.
Can you explain me how can I perform it?

4- (Final): My purpose is putting a little http server in the ndn  
network. To do it,I am confused about what can I do.

Thank you,
Matteo

Quoting "Lan Wang (lanwang)" <lanwang at memphis.edu>:

>
>
> On Oct 25, 2016, at 10:09 AM, Ashlesh Gawande (agawande)   
> <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:
>
> For reaching the Internet:
> https://github.com/mininet/mininet/wiki/FAQ#NAT
> You will have to experiment how to integrate NAT with Mini-NDN.
>
>
> In Mini-NDN you can't ping non-neighbors because there is no routing.
>
> Just want to clarify that this is because *IP* routing is not   
> running in Mini-NDN.  If you run some form of IP routing (eg RIP or   
> OSPF) then you can ping non-neighbors.
>
> We do run NLSR in Mini-NDN so you can do ndnping.
>
> Need to use route command to set it up.
> https://redmine.named-data.net/issues/3054
>
> Ashlesh
> ________________________________
> From: Mini-NDN   
> <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Matteo Bertolino   
> <Matteo.Bertolino at eurecom.fr<mailto:Matteo.Bertolino at eurecom.fr>>
> Sent: Tuesday, October 25, 2016 9:53:13 AM
> To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
> Cc: ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>
> Subject: [Mini-NDN] Mininet: connection refused
>
> Good morning,
> I've to run an NDN node on miniNDN, but this ndn node at a certain
> time should perform a network operation like an http connection, a
> wget, a ping etc.
> I obtain two kind of error:
> 1- Connection refused (when I try to connect the special ndn node to
> an http server)
> 2- Network unreachable (for example, when I try a wget or to ping the
> other node).
>
> Do you have a solution?
> Thanks,
> Matteo
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail:   
> http://webmail.eurecom.fr<http://webmail.eurecom.fr/>
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
>



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




From agawande at memphis.edu  Tue Oct 25 13:47:29 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Tue, 25 Oct 2016 20:47:29 +0000
Subject: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/>
 does not exist
In-Reply-To: <CAKaOrij-rA+5a4eM8X12ai+rBLkF1uRaa_ARQJWF7O7ZO26-2g@mail.gmail.com>
References: <CAKaOrig1R2kxWtGRthT-5vcOVuFvnufKCqiswm=JN5624+_9Pg@mail.gmail.com>
	<BN3PR04MB21968A80A473B961612869FBD9D40@BN3PR04MB2196.namprd04.prod.outlook.com>,
	<CAKaOrij-rA+5a4eM8X12ai+rBLkF1uRaa_ARQJWF7O7ZO26-2g@mail.gmail.com>
Message-ID: <BN3PR04MB21962DAB3744F700F3A04E4AD9A80@BN3PR04MB2196.namprd04.prod.outlook.com>

You can use any desired directory.

And the other email (http://www.lists.cs.ucla.edu/pipermail/mini-ndn/2016-October/000150.html)

cleared how to configure nlsr.conf, right?


Ashlesh

________________________________
From: sepehr abdous <sepehrabdous1375 at gmail.com>
Sent: Friday, October 21, 2016 2:02:27 PM
To: Ashlesh Gawande (agawande)
Cc: mini-ndn at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/> does not exist

Thank you for your instant response.
a folder with the name of nlsr.conf exists in the my directory /home/sepehr/NLSR/
shouldn't I use that one?

On Fri, Oct 21, 2016 at 10:21 PM, Ashlesh Gawande (agawande) <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:

You have to configure nlsr.conf


http://named-data.net/doc/NLSR/current/ROUTER-CONFIG.html


So the folders it uses for logs etc must exist. You can simply change that paths in nlsr.conf


If you run Mini-NDN it will configure for you and you can look in /tmp/<node-name>/nlsr.conf to see how NLSR is configured.


Ashlesh

________________________________
From: Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of sepehr abdous <sepehrabdous1375 at gmail.com<mailto:sepehrabdous1375 at gmail.com>>
Sent: Friday, October 21, 2016 1:44:40 PM
To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
Subject: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/> does not exist

Hello,
 I'm kind of new to nlsr and mini-ndn.
I've installed NLSR based on this link:
http://named-data.net/doc/NLSR/current/INSTALL.html
and when I type nlsr in the terminal I get the following error:

Failed to read configuration file: nlsr.conf
Error in configuration file processing! Exiting from NLSR

then I tried this command:
nlsr -f /home/sepehr/NLSR/nlsr.conf

and I got this error:
Provided log directory </var/log/nlsr/> does not exist
Error in configuration file processing! Exiting from NLSR


can you please help me with this problem?

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



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

From sepehrabdous1375 at gmail.com  Tue Oct 25 14:44:11 2016
From: sepehrabdous1375 at gmail.com (sepehr abdous)
Date: Wed, 26 Oct 2016 01:14:11 +0330
Subject: [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/>
 does not exist
In-Reply-To: <BN3PR04MB21962DAB3744F700F3A04E4AD9A80@BN3PR04MB2196.namprd04.prod.outlook.com>
References: <CAKaOrig1R2kxWtGRthT-5vcOVuFvnufKCqiswm=JN5624+_9Pg@mail.gmail.com>
	<BN3PR04MB21968A80A473B961612869FBD9D40@BN3PR04MB2196.namprd04.prod.outlook.com>
	<CAKaOrij-rA+5a4eM8X12ai+rBLkF1uRaa_ARQJWF7O7ZO26-2g@mail.gmail.com>
	<BN3PR04MB21962DAB3744F700F3A04E4AD9A80@BN3PR04MB2196.namprd04.prod.outlook.com>
Message-ID: <CAKaOrihqgpPQ=7DEjXb5yu2v3Jv_nGMSD0XkMwu9MkNGKW4KPQ@mail.gmail.com>

yeah thank you very much

On Wed, Oct 26, 2016 at 12:17 AM, Ashlesh Gawande (agawande) <
agawande at memphis.edu> wrote:

> You can use any desired directory.
>
> And the other email (http://www.lists.cs.ucla.edu/pipermail/mini-ndn/2016-
> October/000150.html)
>
> cleared how to configure nlsr.conf, right?
>
>
> Ashlesh
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Friday, October 21, 2016 2:02:27 PM
> *To:* Ashlesh Gawande (agawande)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] NLSR error:Provided log directory
> </var/log/nlsr/> does not exist
>
> Thank you for your instant response.
> a folder with the name of nlsr.conf exists in the my directory
> /home/sepehr/NLSR/
> shouldn't I use that one?
>
> On Fri, Oct 21, 2016 at 10:21 PM, Ashlesh Gawande (agawande) <
> agawande at memphis.edu> wrote:
>
>> You have to configure nlsr.conf
>>
>>
>> http://named-data.net/doc/NLSR/current/ROUTER-CONFIG.html
>>
>>
>> So the folders it uses for logs etc must exist. You can simply change
>> that paths in nlsr.conf
>>
>>
>> If you run Mini-NDN it will configure for you and you can look in
>> /tmp/<node-name>/nlsr.conf to see how NLSR is configured.
>>
>>
>> Ashlesh
>> ------------------------------
>> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
>> sepehr abdous <sepehrabdous1375 at gmail.com>
>> *Sent:* Friday, October 21, 2016 1:44:40 PM
>> *To:* mini-ndn at lists.cs.ucla.edu
>> *Subject:* [Mini-NDN] NLSR error:Provided log directory </var/log/nlsr/>
>> does not exist
>>
>> Hello,
>>  I'm kind of new to nlsr and mini-ndn.
>> I've installed NLSR based on this link:
>> http://named-data.net/doc/NLSR/current/INSTALL.html
>> and when I type nlsr in the terminal I get the following error:
>>
>> Failed to read configuration file: nlsr.conf
>> Error in configuration file processing! Exiting from NLSR
>>
>> then I tried this command:
>> nlsr -f /home/sepehr/NLSR/nlsr.conf
>>
>> and I got this error:
>> Provided log directory </var/log/nlsr/> does not exist
>> Error in configuration file processing! Exiting from NLSR
>>
>>
>> can you please help me with this problem?
>>
>> Thank you
>> --
>> Sepehr Abdous
>> Faculty: abdous at ce.sharif.edu
>> Yahoo mail: sepehrabdous at yahoo.com
>> Cellphone:+989194030591
>> School of computer engineering
>> Sharif University of Technology
>> Tehran, Iran
>>
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989194030591
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>



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

From agawande at memphis.edu  Wed Oct 26 11:28:43 2016
From: agawande at memphis.edu (Ashlesh Gawande (agawande))
Date: Wed, 26 Oct 2016 18:28:43 +0000
Subject: [Mini-NDN] Mininet: connection refused
In-Reply-To: <20161025183332.f58x2on38k00kgos@webmail.eurecom.fr>
References: <20161025165313.965m178rtw480g4g@webmail.eurecom.fr>
	<BN3PR04MB219672DA7FD31B40CB8D44E9D9A80@BN3PR04MB2196.namprd04.prod.outlook.com>
	<69C9B954-99A6-4806-85D8-8E90BFF1AD3F@memphis.edu>,
	<20161025183332.f58x2on38k00kgos@webmail.eurecom.fr>
Message-ID: <BN3PR04MB219649A918E13A8F42012054D9AB0@BN3PR04MB2196.namprd04.prod.outlook.com>

The mn --nat option attaches the nat to s1 (See: s1 ifconfig)


If you try s1 ping google.com that should work.


If you want h1 to reach google, I think this will help:

https://techandtrains.com/2013/11/24/mininet-host-talking-to-internet/


Can also study the nat example:

https://github.com/mininet/mininet/blob/master/examples/natnet.py


For routes to reach non-neighbors I don't remember how to set it up but you can try to use "route" or "ip route" command to add static routes to non neighbors.

Can also look into switches: https://github.com/mininet/openflow-tutorial/wiki/Router-Exercise

(Mini-NDN conf parser does handle switches if you want to insert them, but I have not tested it).

You will have to experiment with this as I don't know the exact steps for the setup. I will try to find them.


Can you describe the topology, where do you want to put the Http server?


Ashlesh

________________________________
From: Matteo Bertolino <Matteo.Bertolino at eurecom.fr>
Sent: Tuesday, October 25, 2016 11:33:32 AM
To: Lan Wang (lanwang)
Cc: Ashlesh Gawande (agawande); mini-ndn at lists.cs.ucla.edu; ndn-interest at lists.cs.ucla.edu
Subject: Re: [Mini-NDN] Mininet: connection refused

Dears,
thank you for the interest. I have still some questions unsolved.

1- The sentence:
> You will have to experiment how to integrate NAT with Mini-NDN.
Does it mean that this feature is not available now? I have no idea
how to integrate miniNDN with nat. In mininet I see --nat option, but
here it does not work.

2- However, also writing mn --nat , the command h1 ping google.fr fails.

3- The sentence:
> If you run some form of IP routing (eg RIP or OSPF) then you can
> ping non-neighbors.
Can you explain me how can I perform it?

4- (Final): My purpose is putting a little http server in the ndn
network. To do it,I am confused about what can I do.

Thank you,
Matteo

Quoting "Lan Wang (lanwang)" <lanwang at memphis.edu>:

>
>
> On Oct 25, 2016, at 10:09 AM, Ashlesh Gawande (agawande)
> <agawande at memphis.edu<mailto:agawande at memphis.edu>> wrote:
>
> For reaching the Internet:
> https://github.com/mininet/mininet/wiki/FAQ#NAT
> You will have to experiment how to integrate NAT with Mini-NDN.
>
>
> In Mini-NDN you can't ping non-neighbors because there is no routing.
>
> Just want to clarify that this is because *IP* routing is not
> running in Mini-NDN.  If you run some form of IP routing (eg RIP or
> OSPF) then you can ping non-neighbors.
>
> We do run NLSR in Mini-NDN so you can do ndnping.
>
> Need to use route command to set it up.
> https://redmine.named-data.net/issues/3054
>
> Ashlesh
> ________________________________
> From: Mini-NDN
> <mini-ndn-bounces at lists.cs.ucla.edu<mailto:mini-ndn-bounces at lists.cs.ucla.edu>> on behalf of Matteo Bertolino
> <Matteo.Bertolino at eurecom.fr<mailto:Matteo.Bertolino at eurecom.fr>>
> Sent: Tuesday, October 25, 2016 9:53:13 AM
> To: mini-ndn at lists.cs.ucla.edu<mailto:mini-ndn at lists.cs.ucla.edu>
> Cc: ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>
> Subject: [Mini-NDN] Mininet: connection refused
>
> Good morning,
> I've to run an NDN node on miniNDN, but this ndn node at a certain
> time should perform a network operation like an http connection, a
> wget, a ping etc.
> I obtain two kind of error:
> 1- Connection refused (when I try to connect the special ndn node to
> an http server)
> 2- Network unreachable (for example, when I try a wget or to ping the
> other node).
>
> Do you have a solution?
> Thanks,
> Matteo
>
> -------------------------------------------------------------------------------
> This message was sent using EURECOM Webmail:
> http://webmail.eurecom.fr<http://webmail.eurecom.fr/>
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu<mailto:Mini-NDN at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
>



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

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