commit | e25b0f093b50879d89ab231503cb77307c9a01f2 | [log] [tgz] |
---|---|---|
author | Chengyu Fan <chengy.fan@gmail.com> | Sat Apr 05 21:42:40 2014 -0600 |
committer | Alexander Afanasyev <alexander.afanasyev@ucla.edu> | Mon Apr 07 09:18:20 2014 -0700 |
tree | 77999f385da29086ea9d544b3bf80d32df4dea1a | |
parent | 4d43a4587139f0a0ab21ae07cbf067bd82f0357b [diff] |
tools: support IPv6 in nfd-status-http-server Change-Id: I40866b0caf25315123f0da5a3136b576ece19027 Refs: #1445
This README uses SYSCONFDIR
when referring to the default locations of various NFD configuration files. By default, SYSCONFDIR
is set to /usr/local/etc
. If you override PREFIX
, then SYSCONFDIR
will default to PREFIX/etc
.
You may override SYSCONFDIR
and PREFIX
by specifying their corresponding options during installation:
./waf install --prefix <path/for/prefix> --sysconfdir <some/other/path>
NFD's runtime settings may be modified via configuration file. After installation, a working sample configuration is provided at SYSCONFDIR/ndn/nfd.conf.sample
. At startup, NFD will attempt to read the default configuration file location: SYSCONFDIR/ndn/nfd.conf
.
You may also specify an alternative configuration file location by running NFD with:
nfd --config </path/to/nfd.conf>
Once again, note that you may simply copy or rename the provided sample configuration and have an almost fully configured NFD. However, this NFD will be unable to add FIB entries or perform other typical operation tasks until you authorize an NDN certificate with the appropriate privileges.
Many NFD management protocols require signed commands to be processed (e.g. FIB modification, Face creation/destructions, etc.). You will need an NDN certificate to use any application that issues signed commands.
If you do not already have NDN certificate, you can generate one with the following commands:
Generate and install a self-signed identity certificate:
ndnsec-keygen /`whoami` | ndnsec-install-cert -
Note that the argument to ndnsec-key will be the identity name of the new key (in this case, /your-username
). Identity names are hierarchical NDN names and may have multiple components (e.g. /ndn/ucla/edu/alice
). You may create additional keys and identities as you see fit.
Dump the NDN certificate to a file:
The following commands assume that you have not modified PREFIX
or SYSCONFDIR
If you have, please substitute /usr/local/etc
for the appropriate value (the overriden SYSCONFDIR
or PREFIX/etc
if you changed PREFIX
).
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
The ether configuration file section contains settings for Ethernet faces and channels. These settings will NOT work without root or setting the appropriate permissions:
sudo setcap cap_net_raw,cap_net_admin=eip /full/path/nfd
You may need to install a package to use setcap:
Ubuntu:
sudo apt-get install libcap2-bin
Mac OS X:
curl https://bugs.wireshark.org/bugzilla/attachment.cgi?id=3373 -o ChmodBPF.tar.gz tar zxvf ChmodBPF.tar.gz open ChmodBPF/Install\ ChmodBPF.app
or manually:
sudo chgrp admin /dev/bpf* sudo chmod g+rw /dev/bpf*