NFD » Packaging

ndn-autoconfig-client service cannot register any prefix, because its $HOME is set to /nonexistent and therefore cannot access a key chain. Although RIB would accept any signature in the default configuration, it would not accept a registration command with no signature.
Additionally, it’s impossible to use “find home router” stage because there isn’t a key chain to install certificate into.

Environment: Debian Stretch ARMv7, backport of 0.6.1-ppa1~artful.

● ndn-autoconfig-client.service - NDN Autoconfig Client
   Loaded: loaded (/lib/systemd/system/ndn-autoconfig-client.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2018-03-24 03:44:09 UTC; 2min 38s ago
     Docs: man:nfd-autoconfig
 Main PID: 6207 (ndn-autoconfig)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/ndn-autoconfig-client.service
           └─6207 /usr/bin/ndn-autoconfig -d -c /etc/ndn/autoconfig.conf

Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Error 403 when registering hub discovery prefix for face 258 (udp4://224.0.23.170:56363): aut
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Error 403 when registering hub discovery prefix for face 259 (udp6://[ff02::1234%eth0]:56363)
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Stage multicast discovery failed: Cannot register hub discovery prefix for any face
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Starting guess from search domains stage
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Sending DNS query for SRV record for _ndn._udp
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Stage guess from search domains failed: SRV record cannot be parsed
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Starting NDN-FCH stage
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Stage NDN-FCH succeeded with udp://198.111.224.197
Mar 24 03:44:10 beaglebone ndn-autoconfig[6207]: Connected to HUB udp4://198.111.224.197:6363
Mar 24 03:44:11 beaglebone ndn-autoconfig[6207]: Failed to register /: authorization rejected (403)