[Ndn-interest] [jndn] Remote prefix registration (#6)

Thompson, Jeff jefft0 at remap.UCLA.EDU
Wed Feb 25 08:40:30 PST 2015

Junxiao is right. If you are able to run NFD locally, it is better to do this and use nfdc to route to the remote forwarder.
- Jeff T

From: Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>>
Date: Wednesday, February 25, 2015 at 8:37
To: Bassem Labib <bassem.labib at gmail.com<mailto:bassem.labib at gmail.com>>
Cc: "ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>" <ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>>
Subject: Re: [Ndn-interest] [jndn] Remote prefix registration (#6)

Hi Bassem

To create a file transfer app between two laptops without a third router:

1. both laptops need NFD running
2. on laptopA, write a producer app that does local prefix registration
3. on laptopB, use nfdc command line or NFD Management protocol to create a face toward laptopA, and register a prefix using local prefix registration with that face as nexthop
4. on laptopB, write a consumer app that expresses Interests for the prefix

Remote prefix registration isn't needed in this solution.

Yours, Junxiao
From: Bassem Labib<mailto:bassem.labib at gmail.com>
Sent: ?2/?25/?2015 9:27
To: Junxiao Shi<mailto:shijunxiao at email.arizona.edu>
Cc: ndn-interest at lists.cs.ucla.edu<mailto:ndn-interest at lists.cs.ucla.edu>; Jeff Burke<mailto:jburke at remap.ucla.edu>
Subject: Re: [Ndn-interest] [jndn] Remote prefix registration (#6)

Hi Junxiao,

Actually I am surprised when you said: 'jndn currently supports localhost prefix registration only.'

So, how can I implement the clients to do prefix registration and sharing the files between each other?
Is there any solution to let external/non-local machines to make the registration?
On the other hand, does the same happend for express Interest too?

Please advice.

Best Regards,
Bassem Labib

On Wed, Feb 25, 2015 at 5:16 PM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:

Hi Bassem

jndn currently supports localhost prefix registration only.
NFD treats loopback address as localhost. is not a loopback address despite that it's on same machine.
A localhost registration, when sent to a non-local face, will be silently rejected.

It's intentional for NFD to interpret non-loopback address of same machine as non-local, otherwise proxy app for new socket type or wire format won't be able to create a non-local face without requiring a separate machine.

Yours, Junxiao

On Feb 25, 2015 8:06 AM, "Bassem Labib" <bassem.labib at gmail.com<mailto:bassem.labib at gmail.com>> wrote:
Hi Jeff,

While I'm testing the jndn to register a Prefix using TestPublishAsyncNfd.java under test package, It works fine and register the "/testecho" prefix successfully only when using the default host Face or using "localhost" and loop back address "", but when using the IP address assigned to the same machine as "" it didn't work (Timeout) and I notes it registers on NDNx and print out the following:

Register prefix  /testecho
Feb 25, 2015 4:40:45 PM net.named_data.jndn.Node$RegisterResponse onTimeout
INFO: Timeout for NFD register prefix command. Attempting an NDNx command...
Feb 25, 2015 4:40:49 PM net.named_data.jndn.Node$NdndIdFetcher onTimeout
INFO: Register prefix failed: Timeout fetching the NDNx ID
Register failed for prefix /testecho

please help, I need an explain this situation.

Best Regards,
Bassem Labib

Ndn-interest mailing list
Ndn-interest at lists.cs.ucla.edu<mailto:Ndn-interest at lists.cs.ucla.edu>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndn-interest/attachments/20150225/0cf7ba18/attachment.html>

More information about the Ndn-interest mailing list