NFD

Bug #2334

Updated by Junxiao Shi almost 10 years ago

When the "transport" field in configuration file "client.conf" is changed to value other than  
 {tcp|udp}://127.0.0.1 or unix:///var/run/nfd.sock 
 then whenever NRD is run it reports the fatal error message 
 "FATAL: [NRD] error while connecting to the forwarder" 

 environment on OS X 10.10.1 
 OSTYPE: darwin14 
 boost: 1.55.0 

 steps to reproduce 

 ``` 
 git clone https://github.com/named-data/ndn-cxx 
 cd ndn-cxx 
 ./waf configure --with-examples 
 ./waf 
 sudo ./waf install 
 git clone --recursive https://github.com/named-data/NFD 
 cd NFD 
 ./waf configure 
 ./waf 
 sudo ./waf install 

 sudo cp /usr/local/etc/ndn/nfd.conf.sample /usr/local/etc/ndn/nfd.conf 
 sudo cp /usr/local/etc/ndn/client.conf.sample /usr/local/etc/ndn/client.conf 

 change the following line in "client.conf" 
 transport=unix:///var/run/nfd.sock 
 to 
 transport=tcp4://172.18.53.106:6363 
 ; another (another computer with the exact same environment, OS, hardware running up an nfd and nrd successfully successfully) 

 ndnsec-keygen /`whoami` | ndnsec-install-cert - 
 sudo mkdir -p /usr/local/etc/ndn/keys/ 
 ndnsec-cert-dump -i /`whoami` >    default.ndncert 
 sudo mv default.ndncert /usr/local/etc/ndn/keys/default.ndncert 

 nfd-start 
 ``` 

  ----> boom! The error occurs 
 " [NRD] error while connecting to the forwarder" 

 By the way on my Fedora 20 with boost 1.54.0 there is no such problem.

Back