[Nfd-dev] [ndn] NDN Seminar: Practical Congestion Control for NDN

Gusev, Peter peter at remap.ucla.edu
Thu Jun 2 09:43:07 PDT 2016


hi Junxiao,

I deleted this identity, restarted nfd, ndn-autoconfig and ndncon. Do you see me now?

$ grep AutoPrefix /tmp/nfd.log
1464885670.282895 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section
1464885670.283290 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section
1464885670.400656 INFO: [AutoPrefixPropagator] local registration only for /localhost/nfd/rib
1464885680.576684 INFO: [AutoPrefixPropagator] no signing identity available for: /localhop/ndn-autoconf/hub
1464885685.094809 INFO: [AutoPrefixPropagator] no signing identity available for: /ndn
1464885685.173265 INFO: [AutoPrefixPropagator] this is a prefix registered by some hub: /localhop/nfd
1464885685.173435 INFO: [AutoPrefixPropagator] redo 0 propagations when new Hub connectivity is built.
1464885691.396367 INFO: [AutoPrefixPropagator] no signing identity available for: /ndn/broadcast/ndnrtc/chatrooms
1464885691.502863 INFO: [AutoPrefixPropagator] no signing identity available for: /ndn/broadcast/ndnrtc/users


Thanks,

--
Peter Gusev

peter at remap.ucla.edu<mailto:peter at remap.ucla.edu>
+1 213 5872748
peetonn_ (skype)

Software Engineer/Programmer Analyst @ REMAP UCLA

Video streaming/ICN networks/Creative Development

On Jun 2, 2016, at 9:37 AM, Junxiao Shi <shijunxiao at email.arizona.edu<mailto:shijunxiao at email.arizona.edu>> wrote:

Hi Peter

NFD-RIB prefers the shortest identity available, because it can register the largest possible namespace toward the end host. This has nothing to do with which identity is the default.
Your KeyChain contains an identity named ndn:/, so that NFD-RIB is trying to register ndn:/ toward your end host, with the certificate associated with this identity. That certificate is almost certainly not trusted by the testbed, thus you won’t get a successful registration.
If you change NFD-RIB loglevel to TRACE, you should be able to see the error.

You need to execute ndnsec delete ndn:/ and then restart NFD.
If necessary, you can backup the private key and certificates of that identity before deleting it.

Yours, Junxiao

From: Gusev, Peter<mailto:peter at remap.ucla.edu>
Sent: Thursday, June 2, 2016 09:27
To: Junxiao Shi<mailto:shijunxiao at email.arizona.edu>
Cc: Dehart, John<mailto:jdd at wustl.edu>
Subject: Re: [ndn] NDN Seminar: Practical Congestion Control for NDN

hi Junxiao,

We weren’t able to make me discoverable on ndncon while connected to REMAP hub.
Can you please give any advices on troubleshooting this? It seems that we tried everything we could…

My NFD is v0.4.0 build from sources. Certificate installed is default:

$ ndnsec list
* /ndn/edu/ucla/remap/peter
  /
  /peetonn
  /ndn/edu/ucla/remap
  /ndn/edu/ucla/remap/zhehao
  /ndn/edu/ucla/remap/peter/ndncon

I ran ndn-autoconfig and here’s the grep from NFD log:

$ grep AutoPrefix /tmp/nfd.log
1464817688.388236 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section
1464817688.388581 INFO: [AutoPrefixPropagator] Load auto_prefix_propagate section in rib section
1464817688.507553 INFO: [AutoPrefixPropagator] local registration only for /localhost/nfd/rib
1464817696.807139 INFO: [AutoPrefixPropagator] no hub connected to propagate /
1464817701.880132 INFO: [AutoPrefixPropagator] prefix has already been propagated: /
1464817701.957961 INFO: [AutoPrefixPropagator] this is a prefix registered by some hub: /localhop/nfd
1464817701.958131 INFO: [AutoPrefixPropagator] redo 1 propagations when new Hub connectivity is built.
1464817708.727323 INFO: [AutoPrefixPropagator] prefix has already been propagated: /
1464817708.834888 INFO: [AutoPrefixPropagator] prefix has already been propagated: /
1464817709.189442 INFO: [AutoPrefixPropagator] prefix has already been propagated: /
1464817727.020028 INFO: [AutoPrefixPropagator] should be kept for another RIB entry: /ndn

Thanks,

--
Peter Gusev

peter at remap.ucla.edu<mailto:peter at remap.ucla.edu>
+1 213 5872748
peetonn_ (skype)

Software Engineer/Programmer Analyst @ REMAP UCLA

Video streaming/ICN networks/Creative Development

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160602/41dca2c7/attachment.html>


More information about the Nfd-dev mailing list