[Mini-NDN] mini-ndn RTNETLINK error and ndndump question

Fri Sep 30 02:53:43 PDT 2016

Thanks a lot for your answer!
Ok I just tried to install it from source but the RNETLINK error persist
(before I had 2.2.1 version, installed through urpmi). For now I think I'll
skip this error.

Then I discovered that if I open ndndump before running anything, I can see
sync packets like these:

1475226664.873842 From: 1.0.0.2, To: 1.0.0.1, Tunnel Type: UDP, INTEREST:
/ndn/NLSR/sync/342bf7a38a87e1cc9f608d6be1cae441483795ab9d637ba4d3cd2683cf43c582?ndn.MustBeFresh=1&ndn.Nonce=1682376082
1475226665.118037 From: 1.0.0.1, To: 1.0.0.2, Tunnel Type: UDP, INTEREST:
/ndn/NLSR/sync/342bf7a38a87e1cc9f608d6be1cae441483795ab9d637ba4d3cd2683cf43c582?ndn.MustBeFresh=1&ndn.Nonce=297741341
1475226669.107222 From: 1.0.0.2, To: 1.0.0.1, Tunnel Type: UDP, INTEREST:
/ndn/NLSR/sync/342bf7a38a87e1cc9f608d6be1cae441483795ab9d637ba4d3cd2683cf43c582?ndn.MustBeFresh=1&ndn.Nonce=1917123353
1475226669.473420 From: 1.0.0.1, To: 1.0.0.2, Tunnel Type: UDP, INTEREST:
/ndn/NLSR/sync/342bf7a38a87e1cc9f608d6be1cae441483795ab9d637ba4d3cd2683cf43c582?ndn.MustBeFresh=1&ndn.Nonce=2448858119
1475226673.416786 From: 1.0.0.2, To: 1.0.0.1, Tunnel Type: UDP, INTEREST:
/ndn/NLSR/sync/342bf7a38a87e1cc9f608d6be1cae441483795ab9d637ba4d3cd2683cf43c582?ndn.MustBeFresh=1&ndn.Nonce=1585898652
[...]

But if I start ndnpingserver and try to ping from the other node, I can't
see ping packets, but it continues capturing only sync packets.
I didn't notice it before because if I close minindn and reopen it, ndndump
doesn't show anything. I have to restart nfd to have ndndump capturing the
sync packets again.

I tried both your suggestions, but the behavior is exactly the same and the
dump files are unpopulated.

I'm starting to think I should simply switch to another os and try.

Thank you again.

Gaetano

2016-09-29 22:02 GMT+02:00 Ashlesh Gawande (agawande) <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> on behalf of
> Gaetano Laterza <g.laterza6 at gmail.com>
> *Sent:* Thursday, September 29, 2016 11:34:26 AM
> *To:* 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/20160930/e8d96f4c/attachment.html>