[Nfd-dev] NDN certificate & auto prefix propagation

[Junxiao Shi]

Hi Jongdeog

You never tell the P that F is a testbed router by registering a /localhop/nfd route.
See Let the World Reach Your NFD <https://yoursunny.com/t/2016/nfd-prefix/> “how to trigger a propagation” section.

Yours, Junxiao

> On Jan 19, 2017, at 4:32 PM, Lee, Jongdeog <jlee700 at illinois.edu> wrote:
> 
> Dear all,
> 
>   Hope all of you are doing good. I have a question for NDN certificates & auto prefix propagation issue. 
> 
>   Suppose that we have three machines: producer (P), consumer (C), and forwarder (F).
> 
>   What I did are followings:
> 
> 1. P: the valid certificate is installed (/ndn/edu/illinois/jlee700). 
>     (check here: https://ndncert.named-data.net/cert/list/html <https://ndncert.named-data.net/cert/list/html>)
> 2. P: nfdc register /ndn/edu/illinois/jlee700 tcp://forwarder's <tcp://forwarder's> IP.
> 3. P: ndnpingserver /ndn/edu/illinois/jlee700/test
> 4. C: nfdc register /ndn/edu/illinois/jlee700 tcp://forwarder's <tcp://forwarder's> IP.
> 5. C: ndnping /ndn/edu/illinois/jlee700/test  (NOT WORKING)
> 
>   The problem is /ndn/edu/illinois/jlee700 is not registered on F's fib.
>   This worked before (3 months ago), but now is not working. 
>   Any helps would be appreciated.
> 
> Best wishes,
> Jongdeog Lee (JD)
> 
> ------------------------------------------------
> Ph.D. Student
> Department of Computer Science
> University of Illinois at Urbana-Champaign
> _______________________________________________
> Nfd-dev mailing list
> Nfd-dev at lists.cs.ucla.edu <mailto:Nfd-dev at lists.cs.ucla.edu>
> http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev <http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20170120/25c2bf2d/attachment-0001.html>