[Ndn-interest] miniNDN: nack, no route

[Matteo Bertolino]

Good morning NDN community,
I choose miniNDN to begin my experience, but surely for my poor use of  
the tool, I am obtaining unexpected results.
I launched the program already written pingAll in a my personal  
topology composed by two nodes connected by a link.

It is a simple scenario, but I have the same following problem with  
the default topology: all the requests are nacked. For example:
PING /ndn/edu/b
20160906T113355.728806 - nack from /ndn/edu/b: seq=7022016325669868656  
time=25.3841 ms reason=NoRoute
[...]
10 packets transmitted, 0 received, 10 nacked, 0% packet loss, 100%  
nacked, time 0 ms

NLSR converged successfully, and the FIB table of A and B seems ok.  
However I wrote them below.

mininet> a nfd-status -b
FIB:
   /ndn/NLSR/sync nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
   /localhost/nfd/rib nexthops={faceid=256 (cost=0)}
   /ndn/NLSR/LSA nexthops={faceid=260 (cost=10)}
   /ndn/broadcast/KEYS nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
   /ndn/NLSR/LSA/edu/%C1.Router/cs/a nexthops={faceid=257 (cost=0)}
   /ndn/edu/%C1.Router/cs/b nexthops={faceid=260 (cost=10)}
   /localhost/nfd nexthops={faceid=1 (cost=0)}
   /ndn/edu/b nexthops={faceid=260 (cost=10)}
   /localhost/nlsr nexthops={faceid=257 (cost=0)}
   /ndn/edu/%C1.Router/cs/a nexthops={faceid=257 (cost=0)}


mininet> b nfd-status -b
FIB:
   /ndn/NLSR/sync nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
   /localhost/nfd/rib nexthops={faceid=256 (cost=0)}
   /ndn/NLSR/LSA nexthops={faceid=260 (cost=10)}
   /ndn/broadcast/KEYS nexthops={faceid=257 (cost=0), faceid=260 (cost=10)}
   /ndn/edu/%C1.Router/cs/b nexthops={faceid=257 (cost=0)}
   /ndn/edu/a nexthops={faceid=260 (cost=10)}
   /localhost/nfd nexthops={faceid=1 (cost=0)}
   /localhost/nlsr nexthops={faceid=257 (cost=0)}
   /ndn/edu/%C1.Router/cs/a nexthops={faceid=260 (cost=10)}
   /ndn/NLSR/LSA/edu/%C1.Router/cs/b nexthops={faceid=257 (cost=0)}

Any ideas? Thank you very much

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