| Alexander Afanasyev | 3ecec50 | 2014-04-16 13:42:44 -0700 | [diff] [blame] | 1 | NRD (NFD RIB Daemon) |
| 2 | ======================== |
| 3 | |
| 4 | NRD is a complementary daemon designed to work in parallel with NFD |
| 5 | and to provide services for Routing Information Base management and |
| 6 | constructing NFD's FIB: |
| 7 | |
| 8 | * prefix registration from applications; |
| 9 | * manual prefix registration; |
| 10 | * prefix registrations from multiple dynamic routing protocols. |
| 11 | |
| 12 | Running and Configuring NRD |
| 13 | --------------------------- |
| 14 | |
| 15 | NRD's runtime settings may be modified via configuration file. After |
| 16 | installation, a working sample configuration is provided at |
| 17 | ``SYSCONFDIR/ndn/nrd.conf.sample``. At startup, NRD will attempt to read |
| 18 | the default configuration file from following location: |
| 19 | ``SYSCONFDIR/ndn/nrd.conf``. |
| 20 | |
| 21 | You may also specify an alternative configuration file location by |
| 22 | running NRD with: |
| 23 | |
| 24 | :: |
| 25 | |
| 26 | nrd --config </path/to/nrd.conf> |
| 27 | |
| 28 | Currently, nrd.conf contains only a security section, which is well |
| 29 | documented in the sample configuration file. |
| 30 | |
| 31 | Starting experiments |
| 32 | -------------------- |
| 33 | |
| 34 | 1. Build, install and setup NFD by following the directions provided in |
| 35 | README.md in NFD root folder. |
| 36 | |
| 37 | 2. Create certificates by following the instructions in NFD's README.md |
| 38 | |
| 39 | 3. Build and install NRD by following the directions in INSTALL.md |
| 40 | |
| 41 | 4. Create nrd.conf file. You can simply copy the provided sample file in |
| 42 | ``SYSCONFDIR/ndn/nrd.conf``. |
| 43 | |
| 44 | 5. Setup the trust-anchors in nrd.conf. Ideally, the prefix registration |
| 45 | Interest should be signed by application/user key, and this |
| 46 | application/user key should be used as trust-anchor. However, |
| 47 | currently the default certificate is used to sign the registration |
| 48 | Interests. Therefore, for initial testing the default certificate |
| 49 | should be set as the trust-anchor. For doing so, the default |
| 50 | certificate should be copied in the same folder where the nrd.conf |
| 51 | is. Secondly, the trust-anchor should point to the copied certificate |
| 52 | in nrd.conf. To know the id of default certificate you can use: |
| 53 | |
| 54 | ~$ ndnsec-get-default |
| 55 | |
| 56 | 6. Start NFD (assuming the NFD's conf file exist in |
| 57 | ``SYSCONFDIR/ndn/nfd.conf``): |
| 58 | |
| 59 | ~$ nfd |
| 60 | |
| 61 | 7. Start NRD (assuming the conf file exist in |
| 62 | ``SYSCONFDIR/ndn/nrd.conf``): |
| 63 | |
| 64 | ~$ nrd |
| 65 | |
| 66 | 8. Try to connect any application to NFD. For example, producer |
| 67 | application that is provided ndn-cpp-dev examples. |