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

[Junxiao Shi]

Hi Peter

You also need to ndnsec delete ndn:/ndn/edu/ucla/remap . I missed that one earilier.
If there’s still problem:
• paste the output of ndnsec list -c
• in nfd.conf of the end host, set AutoPrefixPropagator loglevel to TRACE, and look at NFD logs
• you don’t need to change anything on the router: there’s no useful log over there

Yours, Junxiao

From: Gusev, Peter
Sent: Thursday, June 2, 2016 09:43
To: Junxiao Shi
Cc: <nfd-dev at lists.cs.ucla.edu>
Subject: Re: [ndn] NDN Seminar: Practical Congestion Control for NDN

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
+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> 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
Sent: Thursday, June 2, 2016 09:27
To: Junxiao Shi
Cc: Dehart, John
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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20160602/655c97ad/attachment.html>