[Mini-NDN] namespace scope

[sepehr abdous]

I looked into nfd.log in 3 levels(INFO, DEBUG, TRACE) but I could not find
log messages like you mentioned.
my topology was a -- b -- c -- d
and I used the following commands:

a nfdc cs config admit off
b nfdc cs config admit off
c nfdc cs config admit off
d nfdc cs config admit off
a echo "sepehr sepehr" > sepehr
a ndnputchunks ndn:/sepehr < sepehr &
a nlsrc advertise /sepehr
d ndncatchunks -d iterative ndn:/sepehr
quit

is there any specific info that I am missing?

Best,
Sepehr

On Wed, Nov 14, 2018 at 3:05 AM Muktadir R Chowdhury (mrchwdhr) <
mrchwdhr at memphis.edu> wrote:

> If you have 4 nodes and you know which one is sending the Interest, then
> you need to look into other three nodes' nfd.log. In one of the node's,
> which is actually serving the file, nfd.log you should be able to see
> something like "received Interest /a" and  "sending data for interest /a".
> Look for these log messages.
>
>
> -Muktadir
> ------------------------------
> *From:* sepehr abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Wednesday, November 14, 2018 4:29:26 AM
> *To:* Muktadir R Chowdhury (mrchwdhr)
> *Cc:* mini-ndn at lists.cs.ucla.edu
> *Subject:* Re: [Mini-NDN] namespace scope
>
> Thank you for your guide about advertise.
>
> I still need to know the source of file in my simulation. In other words
> if for instance 4 nodes have the file f, I need to know which one is
> sending me the f.
>
> I looked into nfd.log and nlsr.log but nothing seemed to be useful for me?
> when I use ndncatchunks in node c, nothing written in nlsr.log and nfd.log
> can be used to find the source of file?
>
> any ideas?
>
> Best,
> Sepehr
>
> On Mon, Nov 12, 2018 at 1:29 AM Muktadir R Chowdhury (mrchwdhr) <
> mrchwdhr at memphis.edu> wrote:
>
>
> what namespace should I use so that d be able to fetch f1 from a and I
> don't encounter noRoute error when I am using ndncatchunks in d?
>
> Whatever name prefix you used to put the data in "a" using ndnpuchunks.
> You need to add route
> <http://named-data.net/doc/NFD/current/manpages/nfdc-route.html> for that
> name prefix so that NFD knows where to forward Interest for this prefix. If
> "a" has the data, then need to add route from "b" to "a", "c" to "b", and
> "d" to "c".
>
> Alternatively, if you are using NLSR then you can just add the name prefix
> in "a" using nlsrc advertise
> <https://named-data.net/doc/NLSR/0.4.0/manpages/nlsrc.html>. Then nlsr
> will take care of the rest. If you have a large topology then this is what
> you should do.
>
>
> Also is there any way to understand which node is actually sending you the
> datapacket?
>
> I don't think there is an easy way, other than to inspect the nfd.log on
> each node, since NDN is server agnostic.
>
> -Muktadir
>
>
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of sepehr
> abdous <sepehrabdous1375 at gmail.com>
> *Sent:* Sunday, November 11, 2018 2:19:53 PM
> *To:* mini-ndn at lists.cs.ucla.edu
> *Subject:* [Mini-NDN] namespace scope
>
> Hello all
> I have a topology a -- b -- c -- d.
> I put f1 in a using ndnputchunks.
> what namespace should I use so that d be able to fetch f1 from a and I
> don't encounter noRoute error when I am using ndncatchunks in d?
>
> Also is there any way to understand which node is actually sending you the
> datapacket? lets say we have a large topology and multiple nodes have
> cached f1 and d is requesting f1, Is there any way to know which node is
> sending you the f1?
>
> Best,
> Sepehr
>
>
>
> --
> Sepehr Abdous
> Faculty: abdous at ce.sharif.edu
> Yahoo mail: sepehrabdous at yahoo.com
> Cellphone:+989129751873
> School of computer engineering
> Sharif University of Technology
> Tehran, Iran
>


-- 
Sepehr Abdous
Faculty: abdous at ce.sharif.edu
Yahoo mail: sepehrabdous at yahoo.com
Cellphone:+989129751873
School of computer engineering
Sharif University of Technology
Tehran, Iran
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20181115/6f0c5b8f/attachment.html>