[Ndn-interest] Producer not receiving Interest, when starts a new thread.

Wed May 13 14:57:24 PDT 2015

Hello Steve,

The code snippet is here:
https://gist.github.com/anilj1/ebd1dbb6cf7d9a2582c9

To debug further, I just isolated the thread (not invoking it), still see
the same behavior. I have the following call flow.

   1. P --> sends Interests to --> C
   2. C --> sends Data to --> P (this is being received)
   3. C --> sends a new Interests to --> C (I can see this Interest on
   ndndump running on C)
      1. But I do not see the Interest reaching application on P.

What I meant to say when I mentioned "looks like it is not being picked up
by NFD", that I can see the Interest (#3) on ndndump, so it is for sure
reaching the host, but not NFD (I guess so). Below is the ndndump output; I
have marked the log number with the above call flow sequence number.

#1 --> 1431551430.759917 From: 133.164.60.154, To: 133.164.60.158, Tunnel
Type: UDP, INTEREST:
/ndn/A/R2.router/nsr/2/access/2/DATA/%24cname%3D/ndn/temp/s/2%2Crname%3D/ndn/A/R1.router/nsr/1/access/1%24?ndn.MustBeFresh=1&ndn.InterestLifetime=3000&ndn.Nonce=4128987363
#2 --> 1431551430.767940 From: 133.164.60.158, To: 133.164.60.154, Tunnel
Type: UDP, DATA:
/ndn/A/R2.router/nsr/2/access/2/DATA/%24cname%3D/ndn/temp/s/2%2Crname%3D/ndn/A/R1.router/nsr/1/access/1%24/testApp/%FD%00%00%01MR%19Q%C5
#3 --> 1431551430.768142 From: 133.164.60.158, To: 133.164.60.154, Tunnel
Type: UDP, INTEREST:
/ndn/A/R1.router/nsr/1/access/1/ndn/temp/s/2?ndn.MustBeFresh=1&ndn.InterestLifetime=1000&ndn.Nonce=2531323018

Producer logs shows this

20150513141030759 DEBUG: [Producer] WAITING FOR Events
20150513141030768 DEBUG: [Producer] Received the Data: Name:
/ndn/A/R2.router/nsr/2/access/2/DATA/%24cname%3D/ndn/temp/s/2%2Crname%3D/ndn/
A/R1.router/nsr/1/access/1%24/testApp/%FD%00%00%01MR%19Q%C5
MetaInfo: ContentType: 0, FreshnessPeriod: 10000 milliseconds
Content: (size: 11)
Signature: (type: 1, value_length: 256)

Below is the FACE and FIB status on the NFD, which is in question.

nfd-status -f
Faces:
  faceid=1 remote=internal:// local=internal:// counters={in={0i 409d 0B}
out={1642i 0d 0B}} local persistent point-to-point
  faceid=254 remote=contentstore:// local=contentstore:// counters={in={0i
0d 0B} out={0i 0d 0B}} local persistent point-to-point
  faceid=255 remote=null:// local=null:// counters={in={0i 0d 0B} out={0i
0d 0B}} local persistent point-to-point
  faceid=256 remote=udp4://224.0.23.170:56363 local=udp4://10.0.3.1:56363
counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent multi-access
  faceid=257 remote=udp4://224.0.23.170:56363 local=udp4://
133.164.60.154:56363 counters={in={0i 0d 0B} out={0i 0d 0B}} non-local
persistent multi-access
  faceid=258 remote=ether://[01:00:5e:00:17:aa] local=dev://lxcbr0
counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent multi-access
  faceid=259 remote=ether://[01:00:5e:00:17:aa] local=dev://eth0
counters={in={0i 0d 0B} out={0i 0d 0B}} non-local persistent multi-access
  faceid=260 remote=fd://27 local=unix:///run/nfd.sock counters={in={1609i
25d 120560B} out={25i 369d 325684B}} local on-demand point-to-point
  faceid=267 remote=udp4://133.164.60.158:6363 local=udp4://
133.164.60.154:6363 counters={in={13i 12d 7384B} out={15i 3d 3812B}}
non-local persistent point-to-point
  faceid=291 remote=fd://28 local=unix:///run/nfd.sock counters={in={2i 0d
579B} out={0i 2d 1280B}} local on-demand point-to-point
  faceid=293 remote=fd://32 local=unix:///run/nfd.sock counters={in={1i 0d
46B} out={0i 0d 0B}} local on-demand point-to-point

nfd-status -b
FIB:
  /localhost/nfd nexthops={faceid=1 (cost=0)}
  /ndn/A/R2.router/nsr/2 nexthops={faceid=267 (cost=0), faceid=291 (cost=0)}
  /localhost/nfd/rib nexthops={faceid=260 (cost=0), faceid=291 (cost=0)}
  / nexthops={faceid=291 (cost=0)}

/anil.

On Wed, May 13, 2015 at 2:21 PM, Steve DiBenedetto <
dibenede at cs.colostate.edu> wrote:

> Could you please share your code via https://gist.github.com (or
> something else?).
>
> What do you mean by the Interest is not picked up by NFD? Is the
> Interesting coming into NFD, but not sent do the application's face? If you
> aren't already, debug-level logs are useful for this time of problem.
>
> -Steve
>
> On Wed, May 13, 2015 at 1:46 PM, Anil Jangam <anilj.mailing at gmail.com>
> wrote:
>
>> In the producer example code (see below link), I have added a new thread
>> to process some other input device.
>> https://github.com/named-data/ndn-cxx/blob/master/examples/producer.cpp
>>
>> So, I am doing the following just before calling m_face.processEvents()
>> function.
>>
>>     m_stopDataTracker = true;
>>     m_dataThread = boost::thread(&Producer::trackData, this);
>>
>> Now, my situation is that this producer application is not able to
>> receive any incoming Interests for some reason. I have done the following
>> checks so far:
>>
>>    - m_face.setInterestFilter("/",...),I am registering for "/" just to
>>    ensureproducer receives ALL the traffic.
>>    - I have registered (into NFD) the name prefix in the remote node
>>    (where consumer is running) pointing to the host where producer is running.
>>    - I have also tested this setup using stand-alone producer and
>>    consumer apps, ensuring that NFD configuration is fine.
>>
>> I am curious to know if this addition of application (producer) thread is
>> causing anything here. I can see the Interest reaching on 'ndndump', but
>> looks like it is not being picked up by NFD and hence not reaching the
>> application.
>>
>> Is there any problem in my setup or this thread design?
>>
>> /anil.
>>
>>
>>
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150513/587124d3/attachment.html>