Obaid Amin | 561ac80 | 2013-03-27 18:25:20 -0500 | [diff] [blame] | 1 | Installation: |
| 2 | |
| 3 | 1: Getting NLSR: |
| 4 | |
| 5 | https://github.com/NDN-Routing/NLSR0.0 |
| 6 | |
| 7 | 2: run make to compile. |
| 8 | |
| 9 | 3: Start ccnx daemon (ccnd) and Repo (ccnr). |
| 10 | |
| 11 | 4: Add '/ndn/keys' route to your neighboring testbed nodes. |
| 12 | This can be done by adding routes in your ccnd.conf to all neigbors, |
| 13 | e.g. |
| 14 | add /ndn/keys udp 10.0.XX.XX |
| 15 | add /ndn/keys udp 10.0.YY.YY ... |
| 16 | add /ndn/keys udp 10.0.ZZ.ZZ |
| 17 | |
| 18 | 5: Create your keys and publish them through repo. Please have |
| 19 | a look at https://github.com/named-data/ndn-testbed-key-suite for details. |
| 20 | |
| 21 | 6: create a nlsr configuration file, have a look at |
| 22 | macbook.conf and 'Configuration Parameters' section for details |
| 23 | |
| 24 | 7: start nlsr |
| 25 | |
| 26 | |
| 27 | Configuration Parameter: |
| 28 | |
| 29 | 1. router-name </name/prefix/of/the/router> |
| 30 | It is a required configuration parameter that is used to set the router name. |
| 31 | Name prefix of the router must start with `/ndn' and followed by a strict |
| 32 | hierarchical order of name components up to the hostname of the router. For |
| 33 | e.g. if router has a hostname host.dept.org.edu pollux.cs.memphis.edu then the |
| 34 | router name can be `/ndn/org.edu/dept/host.. |
| 35 | |
| 36 | 2. ccnneighbor </name/prefix/of/neighbor> [neighbor_ip_addrr] |
| 37 | This parameter is used to configure the neighboring router. Name prefix of a |
| 38 | neighbor must start with `/ndn. and followed by a strict hierarchical order of |
| 39 | name component as mentioned for router-name. If a router has a neighbor having |
| 40 | hostname `neighbor.dept.org.edu' then configuration command would be |
| 41 | `ccnneighbor /ndn/org.edu/dept/neighbor. The optional parameter, |
| 42 | [neighbor_ip_addrr], can be provided for explicitly connecting to a given |
| 43 | IP. This is useful if there is no entry of the hostname in the DNS. |
| 44 | |
| 45 | 3. ccnname </name/prefix/to/be/advertised> |
| 46 | ccnname is used to advertise the name prefix of the services hosted by the |
| 47 | router. Name prefix must follow the ccnx naming convention. |
| 48 | |
| 49 | 4. topo-prefix <name/prefix/of/repo/topo> |
| 50 | It is used to configure the topological prefix of the `sync. slice created for |
| 51 | nlsr in a repo. Prefix must follow the ccnx naming convention. Default value |
| 52 | for topo prefix is `/ndn/routing/nlsr' |
| 53 | |
| 54 | 5. slice-prefix <name/prefix/of/repo/slice> |
| 55 | This parameter is used to set the sync's slice prefix. All nlsr nodes `must' |
| 56 | have the same slice prefix and must follow the ccnx naming convention. Default |
| 57 | value for slice prefix is `/ndn/routing/nlsr/LSA' |
| 58 | |
| 59 | 6. lsa-refresh-time <sec> |
| 60 | It is the time in seconds, after which router will refresh its LSAs. Default |
| 61 | value = 1800 sec, Min = 240 sec |
| 62 | |
| 63 | 7. router-dead-interval <sec> |
| 64 | It is the time after which router will consider its neighbor dead if it does |
| 65 | not hear anything for that amount of time. If an LSA generated by neighbor has |
| 66 | a lifetime greater than router-dead-interval then router will simply discard |
| 67 | the LSA and update name prefix table, routing table and ccnd FIB accordingly. |
| 68 | Default value = 3600 sec, Min = 360 sec. |
| 69 | |
| 70 | 8. interest-retry <number> |
| 71 | interest-retry is maximum number of times a router will send same interest if |
| 72 | the interest is timed out. Default = 3, Min =1 and Max = 10 |
| 73 | |
| 74 | 9. interest-resend-time <sec> |
| 75 | When an interest is timed out, NLSR waits for `interest-resend-time. before |
| 76 | sending another interest. The interest is retransmitted up to the value of |
| 77 | `interest-retry.. If the interest doesn.t get satisfied during this time the |
| 78 | neighbor will be considered as dead. Default value = 15 sec, Min = 1 sec, Max = |
| 79 | 60 sec |
| 80 | |
| 81 | 10. max-faces-per-prefix <number> |
| 82 | By default NLSR calculates and add faces for all available faces to a prefix. |
| 83 | Number of faces can be restricted with this parameter, if this is configured |
| 84 | NLSR will add <number> or faces per prefixes in ccnd FIB. |
| 85 | |
| 86 | 11. debug <on/off> |
| 87 | Enable nlsr debugging by printing out detail messages on the standard output. |
| 88 | By default it is off. |
| 89 | |
| 90 | 12. logdir </directory/for/logging/> |
| 91 | NLSR will start writing log in logdir folder. If logdir is not configured NLSR |
| 92 | will create a log directory name nlsrLog in user home directory and write log |
| 93 | into that folder. |
| 94 | |
| 95 | 13. tunnel-type <udp | tcp> |
| 96 | This is used to specify the tunnel type that NLSR should create for building an |
| 97 | overlay network. By default NLSR creates udp tunnels. |
| 98 | |
| 99 | **Following Commands are only required for hyperbolic routing** |
| 100 | |
akmhoque | 4438c3e | 2013-06-14 10:44:30 -0500 | [diff] [blame] | 101 | 14. hyperbolic-routing <on|dry_run> |
| 102 | This option enables hyperbolic routing. With option on, link state routing |
| 103 | doesn't work while with dry_run option route is calculated by Link State |
| 104 | routing and hyperbolic routes are just recorded only in log file.Following |
| 105 | field is required if hyperbolic routing is on. |
Obaid Amin | 561ac80 | 2013-03-27 18:25:20 -0500 | [diff] [blame] | 106 | |
| 107 | 15. hyperbolic-cordinate <radius> <theta> |
| 108 | Polar coordinates of a node in a form of radius and theta. Currently, calculation |
| 109 | of the polar coordinates is an offline process and done by |
| 110 | the operator of a site. |
| 111 | |
Obaid Amin | 561ac80 | 2013-03-27 18:25:20 -0500 | [diff] [blame] | 112 | 16. keystore-path </path/to/keystore/file name(.ccnx_keystore)> |
| 113 | Path to the keystore. The keystore folder is usually created by |
| 114 | ccninitkeystore. Keys in this folder will be used by NLSR to sign the packets. |
| 115 | |
| 116 | 17. root-key-prefix </key/prefix> |
| 117 | Name prefix of the root key; the site key should be signed by this key. |
| 118 | e.g. root-key-prefix /ndn/keys |
| 119 | |
| 120 | 18. site-name </name/prefix/of/site> |
| 121 | Name of the site of which this router is a part. |
| 122 | |
akmhoque | df9f97b | 2013-08-16 14:49:08 -0500 | [diff] [blame] | 123 | 19. network </name/of/network> |
| 124 | Name of the networks router belongs to |