blob: f2bd2d96f5165b9555ec54c9b4a78dae5c7b25ea [file] [log] [blame]
Vince Lehmanb722b102014-08-24 16:33:49 -05001Getting Started with NLSR
2=========================
3
4.. toctree::
5..
6
7Getting Source
8--------------
9
Alexander Afanasyev7decbbf2014-08-24 21:29:01 -070010- `GitHub NLSR repository <https://github.com/named-data/NLSR>`_
Vince Lehmanb722b102014-08-24 16:33:49 -050011
12Installation
13------------
14
15:doc:`INSTALL`
16
Nick Gordond5c1a372016-10-31 13:56:23 -050017
18Important Notes About Configuration
19-----------------------------------
20
21Since v0.4.0, NLSR no longer creates Faces for the neighbors that are
22specified in ``nlsr.conf``. Instead, it relies on the pre-existence of
23the Faces in NFD. NLSR will obtain this information from NFD, and
24configure its neighbors using this information.
25
26For people who were relying on NLSR to automagically configure their
27networks, this must now be done with ``nfdc``. Its documentation can
28be found `here
29<https://named-data.net/doc/NFD/current/manpages/nfdc.html>`_
30
Vince Lehmanb722b102014-08-24 16:33:49 -050031Configuration
32-------------
33
34After installing NLSR from source, you need to create a configuration file for
Alexander Afanasyev7decbbf2014-08-24 21:29:01 -070035NLSR. Please take a look at :doc:`manpages/nlsr.conf` for a sample configuration. For
36details on configuring a router, please refer to :doc:`ROUTER-CONFIG`. For details on
37security configuration, please refer to :doc:`SECURITY-CONFIG`.
Vince Lehmanb722b102014-08-24 16:33:49 -050038
39Running
40-------
41
42Run nlsr with the following command:
43
44::
45
46 nlsr
47
Alexander Afanasyev7decbbf2014-08-24 21:29:01 -070048NLSR will look for the default configuration file, ``nlsr.conf``, in the current directory.
Vince Lehmanb722b102014-08-24 16:33:49 -050049
Alexander Afanasyev7decbbf2014-08-24 21:29:01 -070050You can also run ``nlsr -f`` with the absolute path of the configuration file:
Vince Lehmanb722b102014-08-24 16:33:49 -050051
52::
53
Alexander Afanasyev7decbbf2014-08-24 21:29:01 -070054 nlsr -f /usr/local/etc/ndn/nlsr.conf
Vince Lehmanb722b102014-08-24 16:33:49 -050055
dmcoomescf8d0ed2017-02-21 11:39:01 -060056Logging
57-------
58
59NLSR uses the ndn-cxx logging facility. All levels listed below the selected log-level
60value are enabled.
Vince Lehmanb722b102014-08-24 16:33:49 -050061
62::
63
dmcoomescf8d0ed2017-02-21 11:39:01 -060064 Valid values:
65
66 TRACE trace messages (most verbose)
67 DEBUG debugging messages
68 INFO informational messages
69 WARN warning messages
70 ERROR error messages
71 FATAL fatal (will be logged unconditionally)
72
73To obtain logs for NLSR, set the NDN_LOG environment variable with the correct prefix and
74log-level settings. For example, running the command `export NDN_LOG=nlsr.*=TRACE && nlsr`
75will display all log messages in NLSR with a DEBUG level or below. If the user is presented
76with an error message `User does not have read and write permission on the directory` it can
77be circumvented by running the application with sudo: `sudo env NDN_LOG=nlsr.*=DEBUG nlsr`.
78Use `man ndn-log` for more detailed instructions.