[Mini-NDN] [EXT] NoRoute error

[Nazatul Haque Sultan]

Dear Junxiao Shi,

Thank you for your quick response. It is working now.

Best regards,
Nazatul

On Mon, Aug 3, 2020 at 1:12 PM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Nazatul
>
> NFD does not forward any Interest starting with /localhost to a remote
> node. Try a different name prefix, such as a prefix under the one you used
> in ping server.
>
> Yours, Junxiao
>
> On Sun, Aug 2, 2020 at 22:50 Nazatul Haque Sultan via Mini-NDN <
> mini-ndn at lists.cs.ucla.edu> wrote:
>
>> *External Email*
>> Dear All,
>>
>> I am facing an issue with miniNDN. I was trying to work on a simple
>> topology file, e.g. *a->c->b*, where *a *publishes content *gpl3 * using *"ndnputchunks
>> -p /localhost/demo/gpl3 < /usr/share/common-licenses/GPL-3 | ndndump -v>
>> outA &"* and* b* request for it using "*ndncatchunks
>> /localhost/demo/gpl3 | ndndump -v> outB &*"*. *I have also attached dump
>> files of node a and b.
>>
>> *Issue*: when I used "*a nfdc route list*" and "*b nfdc route list*"
>> commands, I can see that node a has generated 8 chunks. However, node b is
>> showing *NoRoute error* (I am appending its results below). I tried ping
>> commands and was getting successful ping results for the same topology.
>>
>> My questions are:
>>
>> 1. I can see in the dump files some interest and data packets. As per the
>> output of the command " *b nfdc route list*", there is no route between
>> a to b and vice versa. Are the interest and data packets of the dump files
>> related to the actual content *gpl3* or something else?
>>
>> 2. Why does ping is working while the *ndncatchunks* is showing NoRoute
>> error?
>>
>> Can someone please give me any hint on these? Thank you in advance.
>>
>> mini-ndn> a nfdc route list
>> Loading input ...
>>
>> *Created 8 chunks for prefix /localhost/demo/gpl3Data published with
>> name: /localhost/demo/gpl3/%FD%00%00%01s%B1%E4%9A%BE*
>> ndndump: listening on a-eth0, link-type EN10MB (Ethernet)
>> ndndump: using pcap filter: (ether proto 0x8624) or (tcp port 6363) or
>> (udp port 6363) or (udp port 56363)
>> prefix=/ndn/a-site/KEY nexthop=262 origin=app cost=0 flags=capture
>> expires=never
>> prefix=/ndn/a-site/KEY nexthop=266 origin=app cost=0 flags=capture
>> expires=never
>> prefix=/ndn/a-site/%C1.Router/cs/a/KEY nexthop=262 origin=app cost=0
>> flags=capture expires=never
>> prefix=/ndn/a-site/%C1.Router/cs/a/KEY nexthop=266 origin=app cost=0
>> flags=capture expires=never
>>
>> mini-ndn> b nfdc route list
>> *ERROR: Could not retrieve data for /localhost/demo/gpl3/32=metadata,
>> reason: NoRoute*
>> ndndump: listening on b-eth0, link-type EN10MB (Ethernet)
>> ndndump: using pcap filter: (ether proto 0x8624) or (tcp port 6363) or
>> (udp port 6363) or (udp port 56363)
>> prefix=/ndn/a-site/a nexthop=261 origin=nlsr cost=20 flags=capture
>> expires=3528s
>> prefix=/ndn/a-site/%C1.Router/cs/a nexthop=261 origin=nlsr cost=20
>> flags=capture expires=3528s
>> prefix=/ndn/b-site/KEY nexthop=262 origin=app cost=0 flags=capture
>> expires=never
>> prefix=/ndn/b-site/KEY nexthop=266 origin=app cost=0 flags=capture
>> expires=never
>> prefix=/ndn/b-site/%C1.Router/cs/b/KEY nexthop=262 origin=app cost=0
>> flags=capture expires=never
>>
>> Regards,
>> Nazatul
>> _______________________________________________
>> 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/20200803/2bba8a7b/attachment.html>