<div dir="ltr">Thanks a lot for your answer!<div>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.</div><div><br></div><div>Then I discovered that if I open ndndump before running anything, I can see sync packets like these:</div><div><br></div><div><div>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</div><div>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</div><div>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</div><div>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</div><div>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</div></div><div>[...]</div><div><br></div><div>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.</div><div>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.</div><div><br></div><div>I tried both your suggestions, but the behavior is exactly the same and the dump files are unpopulated.</div><div><br></div><div>I'm starting to think I should simply switch to another os and try.</div><div><br></div><div>Thank you again.</div><div><br></div><div>Gaetano</div></div><div class="gmail_extra"><br><div class="gmail_quote">2016-09-29 22:02 GMT+02:00 Ashlesh Gawande (agawande) <span dir="ltr"><<a href="mailto:agawande@memphis.edu" target="_blank">agawande@memphis.edu</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div id="m_7285828140594180150divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif">
<p>What version of Mininet are you using? They recently fixed the <span>RTNETLINK error on Ubuntu 16.04.</span></p>
<p>You might want to install from source if you haven't: <a href="https://github.com/mininet/mininet" class="m_7285828140594180150OWAAutoLink" id="m_7285828140594180150LPlnk238530" target="_blank">https://github.com/<wbr>mininet/mininet</a></p>
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.
<div>
<p><span><br>
</span></p>
<p><span>I am not sure why ndndump is not working. There is one bug for xterm:</span></p>
<p><span><a href="https://redmine.named-data.net/issues/3038" class="m_7285828140594180150OWAAutoLink" id="m_7285828140594180150LPlnk928011" target="_blank">https://redmine.named-data.<wbr>net/issues/3038</a><br>
</span></p>
<p><br>
</p>
<p>In xterm, can you try export HOME=/tmp/<node-name> before running anything?</p>
<p>That should fix it.</p>
<p><br>
</p>
<p>If not, next thing you can try is to paste the following in bin/minindn, line 344:</p>
<p></p>
<div>for host in self.net.hosts:<br>
for intf in host.intfNames():<br>
ndnDumpOutputFile = "dump.%s_%s" % (intf, str(host.intf(intf).IP(<wbr>)))<br>
host.cmd("ndndump -i %s > %s &" % (intf, ndnDumpOutputFile))</div>
<p></p>
<p><br>
</p>
<p>Then try to install and run and see in /tmp/<node-name> whether you have dump files that are populated.</p>
<p><br>
</p>
<p>Ashlesh</p>
</div>
</div>
<hr style="display:inline-block;width:98%">
<div id="m_7285828140594180150divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Mini-NDN <<a href="mailto:mini-ndn-bounces@lists.cs.ucla.edu" target="_blank">mini-ndn-bounces@lists.cs.<wbr>ucla.edu</a>> on behalf of Gaetano Laterza <<a href="mailto:g.laterza6@gmail.com" target="_blank">g.laterza6@gmail.com</a>><br>
<b>Sent:</b> Thursday, September 29, 2016 11:34:26 AM<br>
<b>To:</b> <a href="mailto:mini-ndn@lists.cs.ucla.edu" target="_blank">mini-ndn@lists.cs.ucla.edu</a><br>
<b>Subject:</b> [Mini-NDN] mini-ndn RTNETLINK error and ndndump question</font>
<div> </div>
</div><div><div class="h5">
<div>
<div dir="ltr">
<div>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:</div>
<div><br>
</div>
<div>$ cat simple.conf</div>
<div>[nodes]</div>
<div>a: _</div>
<div>b: _</div>
<div>[links]</div>
<div>a:b delay=10ms</div>
<div><br>
</div>
<div>In short, I'd like to observe the exchange of Interest / Data packets using ndndump. </div>
<div>First of all, I cannot understand an error occurring during links initialization:</div>
<div><br>
</div>
<div>$ sudo minindn simple.conf</div>
<div>Parse of simple.conf done.</div>
<div>*** Creating network</div>
<div>*** Adding controller</div>
<div>*** Adding hosts:</div>
<div>a b </div>
<div>*** Adding switches:</div>
<div><br>
</div>
<div>*** Adding links:</div>
<div>(10ms delay) *** Error: RTNETLINK answers: No such file or directory</div>
<div>(10ms delay) *** Error: RTNETLINK answers: No such file or directory</div>
<div>(a, b) </div>
<div>*** Configuring hosts</div>
<div>a b </div>
<div>Setup time: 4</div>
<div>*** Starting controller</div>
<div>c0 </div>
<div>*** Starting 0 switches</div>
<div><br>
</div>
<div>*** Starting CLI:</div>
<div>mininet> </div>
<div><br>
</div>
<div>Any idea about the Error: RTNETINK answers: No such file or directory?</div>
<div>Here my system information:</div>
<div><br>
</div>
<div>$ uname -a</div>
<div>Linux machine 4.1.33-nrj-desktop-1rosa-x86_6<wbr>4 #1 SMP PREEMPT Sun Sep 18 20:20:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux</div>
<div><br>
</div>
<div>So, going back to the packets exchange, through xterm I typed on node a:</div>
<div><br>
</div>
<div>$ ndnpingserver /a</div>
<div>PING SERVER /a</div>
<div><br>
</div>
<div>Always on node a, I ran ndndump:</div>
<div><br>
</div>
<div>$ ndndump -i a-eth0</div>
<div><br>
</div>
<div>So I ran from node b the command:</div>
<div><br>
</div>
<div>$ ndnping /a</div>
<div>PING /a</div>
<div>content from /a: seq=2172173333986410181 time=2.51873 ms</div>
<div>content from /a: seq=2172173333986410182 time=0.411503 ms</div>
<div>content from /a: seq=2172173333986410183 time=0.381647 ms</div>
<div>content from /a: seq=2172173333986410184 time=0.458184 ms</div>
<div>[...]</div>
<div><br>
</div>
<div>And on node a I can see:</div>
<div><br>
</div>
<div>interest received: seq=2172173333986410181</div>
<div>interest received: seq=2172173333986410182</div>
<div>interest received: seq=2172173333986410183</div>
<div>interest received: seq=2172173333986410184</div>
<div>[...]</div>
<div><br>
</div>
<div>But ndndump doesn't show any packet. Why? I also tried with:</div>
<div><br>
</div>
<div>$ tcpdump -i a-eth0 -v</div>
<div><br>
</div>
<div>But when I stop it, the result is:</div>
<div><br>
</div>
<div>0 packets captured</div>
<div>0 packets received by filter</div>
<div>0 packets dropped by kernel</div>
<div><br>
</div>
<div>Thank you in advance for your help!</div>
<div>Regards,</div>
<div>Gaetano.</div>
</div>
</div>
</div></div></div>
</blockquote></div><br></div>