including configuration file /etc/raddb/clients.conf
====
-It now loads all of the modules. The module configuration is usually stored in `raddb/mods-enabled/`, with one module configuration per file in that directory.
+It now loads all of the modules. The module configuration is usually stored in `mods-enabled/`, with one module configuration per file in that directory.
Sometimes the module you're using does not seem to be loaded or used. In that case, you should check this section to see that the file is loaded.
[%collapsible]
## Modules
-When the server read the module configuration file above (from `raddb/mods-enabled`), that meant just reding the contents of the file. It is now ready to load the dynamic library which reads that configuration, and which parses the configuration to determine what to do with it.
+When the server read the module configuration file above (from `mods-enabled`), that meant just reding the contents of the file. It is now ready to load the dynamic library which reads that configuration, and which parses the configuration to determine what to do with it.
Each module will print out it's configuration, along with any errors or warnings it sees when it is loading itself.
and follow the instructions in the proceeding section.
You can also enable the `panic_action` given in
-`raddb/radiusd.conf`. See the comments in that file for more details
+`radiusd.conf`. See the comments in that file for more details
about automatically collecting gdb debugging information when the server
crashes.
useful for when running the server with "valgrind".
*-n name*::
- Read `raddb/name.conf` instead of `raddb/radiusd.conf`.
+ Read `name.conf` instead of `radiusd.conf`.
+
Note that by default, the server looks for a configuration file
which matches its own name. Creating a soft link from file `foo`
to `radiusd`, and then running the program `foo`, will cause the
-binary to look for `raddb/foo.conf`.
+binary to look for `foo.conf`.
*-s*::
Run in "single server" mode. The server normally runs with multiple
4) If you need to add a connection to a database FOO (e.g. LDAP
or SQL), then:
+
-a) Edit `raddb/modules/foo`
+a) Edit `modules/foo`
+
This file contains the default configuration for the module. It contains
comments describing what can be configured, and what those configuration
entries mean.
+
-b) Edit `raddb/sites-available/default`
+b) Edit `sites-available/default`
+
This file contains the default policy for the server. e.g. "enable CHAP,
MS-CHAP, and EAP authentication". Look in this file for all references
to your module "foo". Read the comments, and remove the leading hash '#'
from the lines referencing the module. This enables the module.
+
-c) Edit `raddb/sites-available/inner-tunnel`
+c) Edit `sites-available/inner-tunnel`
+
This file contains the default policy for the "tunneled" portion of
certain EAP methods. Perform the same kind of edits as above, for the