[Ndn-interest] miniNDN: nack, no route

[Matteo Bertolino]

First of all, thank you very much Junxiao.
I'm shaming about my future question but I have to do it, sorry.

I launch the program from my console in this way:
sudo minindn --experiment=pingall --nPings=10 ./ndn_utils/topologies/try1.conf
I understand that the pingserver is necessary on B, but in which way I  
can execute this command? If I start the console and I execute your  
command, I have not more the possibility of executing the experiment  
pingall.

Moreover, I am following the following tutorial, in the Installation section:

You can use these steps to verify your installation:

Issue the command: sudo minindn --experiment=pingall --nPings=50
When the mininet> CLI prompt appears, the experiment has finished. On  
the Mini-NDN CLI, issue the command exit to exit the experiment.
Issue the command: grep -c content /tmp/*/ping-data/*.txt. Each file  
should report a count of 50.
Issue the command: grep -c timeout /tmp/*/ping-data/*.txt. Each file  
should report a count of 0.

I understood why my scenario does not work, but I do not understand  
how to run the pingserver on node B and launch the pre-built  
experiment in the meantime. Thank you .
Yours Matteo

Quoting Junxiao Shi <shijunxiao at email.arizona.edu>:

> Hi Matteo
>
> ndnpingserver needs to be running on node B. Otherwise, NFD on node   
> B will return Nack-NoRoute because /ndn/edu/b/ping doesn't match any  
>  FIB entry.
>
> Start ndnpingserver with this command:
> b ndnpingserver /ndn/edu/b &
>
> Yours, Junxiao
>
> -----Original Message-----
> From: "Matteo Bertolino" <Matteo.Bertolino at eurecom.fr>
> Sent: ?9/?6/?2016 4:49
> To: "ndn-interest at lists.cs.ucla.edu" <ndn-interest at lists.cs.ucla.edu>
> Subject: [Ndn-interest] miniNDN: nack, no route
>
> 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
>
>
> _______________________________________________
> Ndn-interest mailing list
> Ndn-interest at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>



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