blob: dff59317848b008bd031b64166b8fdf989dc7f80 [file] [log] [blame]
Alexander Afanasyev20cc34e2014-05-07 01:28:34 -07001; The general section contains settings of nfd process.
2; general
3; {
4; }
5
6log
7{
8 ; default_level specifies the logging level for modules
9 ; that are not explicitly named. All debugging levels
10 ; listed above the selected value are enabled.
11 ;
12 ; Valid values:
13 ;
14 ; NONE ; no messages
15 ; ERROR ; error messages
16 ; WARN ; warning messages
17 ; INFO ; informational messages (default)
18 ; DEBUG ; debugging messages
19 ; TRACE ; trace messages (most verbose)
20 ; ALL ; all messages
21
22 default_level INFO
23
24 ; You may override default_level by assigning a logging level
25 ; to the desired module name. Module names can be found in two ways:
26 ;
27 ; Run:
28 ; nfd --modules
29 ; nrd --modules
30 ;
31 ; Or look for NFD_LOG_INIT(<module name>) statements in .cpp files
32 ;
33 ; Example module-level settings:
34 ;
35 ; FibManager DEBUG
36 ; Forwarder INFO
37}
38
Alexander Afanasyevf9312c32014-12-18 14:23:41 -080039; The tables section configures the CS, PIT, FIB, Strategy Choice, and Measurements
40tables
41{
42
43 ; ContentStore size limit in number of packets
44 ; default is 65536, about 500MB with 8KB packet size
45 cs_max_packets 65536
46
47 ; Set the forwarding strategy for the specified prefixes:
48 ; <prefix> <strategy>
49 strategy_choice
50 {
51 / /localhost/nfd/strategy/best-route
52 /localhost /localhost/nfd/strategy/broadcast
53 /localhost/nfd /localhost/nfd/strategy/best-route
54 /ndn/broadcast /localhost/nfd/strategy/broadcast
55 }
56}
57
Alexander Afanasyev20cc34e2014-05-07 01:28:34 -070058; The face_system section defines what faces and channels are created.
59face_system
60{
61 ; The unix section contains settings of UNIX stream faces and channels.
Alexander Afanasyev011558e2015-01-17 19:54:54 -080062 ; Unix channel is always listening; delete unix section to disable
63 ; Unix stream faces and channels.
Alexander Afanasyev20cc34e2014-05-07 01:28:34 -070064 unix
65 {
Alexander Afanasyev20cc34e2014-05-07 01:28:34 -070066 path /var/run/nfd.sock ; UNIX stream listener path
67 }
68
69 ; The tcp section contains settings of TCP faces and channels.
70 tcp
71 {
72 listen yes ; set to 'no' to disable TCP listener, default 'yes'
73 port 6363 ; TCP listener port number
74 enable_v4 yes ; set to 'no' to disable IPv4 channels, default 'yes'
75 enable_v6 yes ; set to 'no' to disable IPv6 channels, default 'yes'
76 }
77
78 ; The udp section contains settings of UDP faces and channels.
79 ; UDP channel is always listening; delete udp section to disable UDP
80 udp
81 {
82 port 6363 ; UDP unicast port number
83 enable_v4 yes ; set to 'no' to disable IPv4 channels, default 'yes'
84 enable_v6 yes ; set to 'no' to disable IPv6 channels, default 'yes'
85 idle_timeout 600 ; idle time (seconds) before closing a UDP unicast face
86 keep_alive_interval 25; interval (seconds) between keep-alive refreshes
87
88 ; UDP multicast settings
89 ; NFD creates one UDP multicast face per NIC
90 mcast yes ; set to 'no' to disable UDP multicast, default 'yes'
91 mcast_port 56363 ; UDP multicast port number
92 mcast_group 224.0.23.170 ; UDP multicast group (IPv4 only)
93 }
94
Alexander Afanasyev011558e2015-01-17 19:54:54 -080095 ; The ether section contains settings of Ethernet faces and channels.
96 ether
97 {
98 ; Ethernet multicast settings
99 ; NFD creates one Ethernet multicast face per NIC
100 mcast yes ; set to 'no' to disable Ethernet multicast, default 'yes'
101 mcast_group 01:00:5E:00:17:AA ; Ethernet multicast group
102 }
103
104 ; The websocket section contains settings of WebSocket faces and channels.
105
106 websocket
107 {
108 listen yes ; set to 'no' to disable WebSocket listener, default 'yes'
109 port 9696 ; WebSocket listener port number
110 enable_v4 yes ; set to 'no' to disable listening on IPv4 socket, default 'yes'
111 enable_v6 yes ; set to 'no' to disable listening on IPv6 socket, default 'yes'
112 }
Alexander Afanasyev20cc34e2014-05-07 01:28:34 -0700113}
114
115authorizations
116{
117 authorize
118 {
119 certfile certs/localhost_daemons_nrd.ndncert
120 privileges
121 {
122 faces
123 fib
124 strategy-choice
125 }
126 }
127
128 authorize
129 {
130 certfile any
131 privileges
132 {
133 faces
134 strategy-choice
135 }
136 }
137}
138
139rib
140{
141 ; The following localhost_security allows anyone to register routing entries in local RIB
142 localhost_security
143 {
144 trust-anchor
145 {
146 type any
147 }
148 }
149
150 ; localhop_security should be enabled when NFD runs on a hub.
151 ; "/localhop/nfd/fib" command prefix will be disabled when localhop_security section is missing.
152 ; localhop_security
153 ; {
154 ; ; This section defines the trust model for NFD RIB Management. It consists of rules and
155 ; ; trust-anchors, which are briefly defined in this file. For more information refer to
156 ; ; manpage of ndn-validator.conf:
157 ; ;
158 ; ; man ndn-validator.conf
159 ; ;
160 ; ; A trust-anchor is a pre-trusted certificate. This can be any certificate that is the
161 ; ; root of certification chain (e.g., NDN testbed root certificate) or an existing
162 ; ; default system certificate `default.ndncert`.
163 ; ;
164 ; ; A rule defines conditions a valid packet MUST have. A packet must satisfy one of the
165 ; ; rules defined here. A rule can be broken into two parts: matching & checking. A packet
166 ; ; will be matched against rules from the first to the last until a matched rule is
167 ; ; encountered. The matched rule will be used to check the packet. If a packet does not
168 ; ; match any rule, it will be treated as invalid. The matching part of a rule consists
169 ; ; of `for` and `filter` sections. They collectively define which packets can be checked
170 ; ; with this rule. `for` defines packet type (data or interest) and `filter` defines
171 ; ; conditions on other properties of a packet. Right now, you can only define conditions
172 ; ; on packet name, and you can only specify ONLY ONE filter for packet name. The
173 ; ; checking part of a rule consists of `checker`, which defines the conditions that a
174 ; ; VALID packet MUST have. See comments in checker section for more details.
175 ;
176 ; rule
177 ; {
178 ; id "NRD Prefix Registration Command Rule"
179 ; for interest ; rule for Interests (to validate CommandInterests)
180 ; filter
181 ; {
182 ; type name ; condition on interest name (w/o signature)
183 ; regex ^[<localhop><localhost>]<nfd><rib>[<register><unregister>]<>{3}$
184 ; }
185 ; checker
186 ; {
187 ; type customized
188 ; sig-type rsa-sha256 ; interest must have a rsa-sha256 signature
189 ; key-locator
190 ; {
191 ; type name ; key locator must be the certificate name of the
192 ; ; signing key
193 ; regex ^[^<KEY>]*<KEY><>*<ksk-.*><ID-CERT>$
194 ; }
195 ; }
196 ; }
197 ; rule
198 ; {
199 ; id "NDN Testbed Hierarchy Rule"
200 ; for data ; rule for Data (to validate NDN certificates)
201 ; filter
202 ; {
203 ; type name ; condition on data name
204 ; regex ^[^<KEY>]*<KEY><>*<ksk-.*><ID-CERT><>$
205 ; }
206 ; checker
207 ; {
208 ; type hierarchical ; the certificate name of the signing key and
209 ; ; the data name must follow the hierarchical model
210 ; sig-type rsa-sha256 ; data must have a rsa-sha256 signature
211 ; }
212 ; }
213 ; trust-anchor
214 ; {
215 ; type file
216 ; file-name keys/default.ndncert ; the file name, by default this file should be placed in the
217 ; ; same folder as this config file.
218 ; }
219 ; ; trust-anchor ; Can be repeated multiple times to specify multiple trust anchors
220 ; ; {
221 ; ; type file
222 ; ; file-name keys/ndn-testbed.ndncert
223 ; ; }
224 ; }
Alexander Afanasyevf9312c32014-12-18 14:23:41 -0800225
226 remote_register
227 {
228 cost 15 ; forwarding cost of prefix registered on remote router
229 timeout 10000 ; timeout (in milliseconds) of remote prefix registration command
230 retry 0 ; maximum number of retries for each remote prefix registration command
231
232 refresh_interval 300 ; interval (in seconds) before refreshing the registration
233 ; This setting should be less than face_system.udp.idle_time,
234 ; so that the face is kept alive on the remote router.
235 }
Alexander Afanasyev20cc34e2014-05-07 01:28:34 -0700236}