######################################################################
#
-# Make file to be installed in /etc/raddb/certs to enable
+# Make file to be installed in _confdir_/certs to enable
# the easy creation of certificates.
#
# See the README file in this directory for more information.
#
# If these certificates have not been auto-generated:
#
- # cd raddb/certs
+ # cd _confdir_/certs
# make
#
# These test certificates *SHOULD NOT* be used in a normal
#
# You can create the `inner-server.pem` file by doing:
#
- # cd raddb/certs
+ # cd _confdir_/certs
# vi inner-server.cnf
# make inner-server
#
#
# The `users` file as located in `mods-config/files/authorize`. (Livingston-style format).
#
-# See the raddb/mods-config/files/users.adoc file for information
+# See the doc/antora/modules/reference/pages/raddb/mods-config/files/users.adoc file for information
# on the format of the input file, and how it operates.
#
+bob Password.Cleartext := "bob"
+
#
# Configuration file for the rlm_files module.
# Please see rlm_files documentation for more information.
# users with spaces in their names, you must also change
# the "filter_username" policy to allow spaces.
#
-# See raddb/policy.d/filter, filter_username {} section.
+# See policy.d/filter, filter_username {} section.
#
#"John Doe" Password.Cleartext := "hello"
# Reply-Message = "Hello, %{User-Name}"
#
# NOTE: unlike MySQL, which has a tls{} connection configuration, postgresql
# uses its connection parameters - see the radius_db option in
- # the main raddb/mods-available/sql file
+ # the main mods-available/sql file
#
#
-- setup.sql -- MySQL commands for creating the RADIUS user.
--
-- WARNING: You should change 'localhost' and 'radpass'
--- to something else. Also update raddb/mods-available/sql
+-- to something else. Also update mods-available/sql
-- with the new RADIUS password.
--
-- $Id$
## admin.sql -- MySQL commands for creating the RADIUS user.
##
## WARNING: You should change 'localhost' and 'radpass'
-## to something else. Also update raddb/mods-available/sql
+## to something else. Also update mods-available/sql
## with the new RADIUS password.
##
## $Id$
-- which is designed for simple dialup installations of FreeRadius.
--
-- For this schema to work properly you MUST use
--- raddb/sql/postgresql/voip-postpaid.conf rather than
--- raddb/sql/postgresql/dialup.conf
+-- sql/postgresql/voip-postpaid.conf rather than
+-- sql/postgresql/dialup.conf
--
-- If you wish to do RADIUS Authentication using the same database,
--- you MUST use use raddb/sql/postgresql/schema.sql as well as this schema.
+-- you MUST use use sql/postgresql/schema.sql as well as this schema.
--
--
-- setup.sql -- PostgreSQL commands for creating the RADIUS user.
--
-- WARNING: You should change 'localhost' and 'radpass'
--- to something else. Also update raddb/mods-available/sql
+-- to something else. Also update mods-available/sql
-- with the new RADIUS password.
--
-- WARNING: This example file is untested. Use at your own risk.
# match the regular expression: /[a-zA-Z0-9_.]+/
#
# It allows you to define new virtual servers simply by placing
-# a file into the raddb/sites-enabled/ directory.
+# a file into the sites-enabled/ directory.
#
# All of the other configuration sections like:
#
#
# Send an Access-Challenge.
- # See raddb/policy.d/control for the definition
+ # See policy.d/control for the definition
# of "challenge"
#
challenge
#
# Write the "detail" files.
#
- # See raddb/modules/detail.example.com for more info.
+ # See mods-available/detail.example.com for more info.
detail.example.com
}
#
# This is a virtual server that handles DHCP.
#
-# See raddb/mods-available/sqlippool for the IP Pool configuration.
+# See mods-available/sqlippool for the IP Pool configuration.
#
-# See raddb/mods-config/sql/ippool/ for the schemas.
+# See mods-config/sql/ippool/ for the schemas.
#
-# See raddb/sites-available/dhcp for instructions on how to configure
+# See sites-available/dhcp for instructions on how to configure
# the DHCP server.
#
# $Id$
# If you want it to do real DHCP, change this to 67, and good luck!
#
# You can also bind the DHCP socket to an interface.
-# See below, and raddb/radiusd.conf for examples.
+# See below, and radiusd.conf for examples.
#
# This lets you run *one* DHCP server instance and have it listen on
# multiple interfaces, each with a separate policy.
# There is a preconfigured "mac2ip" module setup in
# mods-available/mac2ip. To use it do:
#
-# # cd raddb/
-# # ln -s ../mods-available/mac2ip mods-enabled/mac2ip
-# # mkdir mods-config/passwd
+# $ cd _confdir_
+# $ ln -s ../mods-available/mac2ip mods-enabled/mac2ip
+# $ mkdir mods-config/passwd
#
# Then create the file mods-config/passwd/mac2ip with the above
# format.
#
# outer.request.<attribute>
#
- # The following policy in raddb/policy.d/eap can be used
+ # The following policy in policy.d/eap can be used
# to copy attributes over.
#
# copy_request_to_tunnel
# a single persistent search.
#
# Most options within the listen section are identical to rlm_ldap.
-# See /etc/raddb/mods-available/ldap for more detailed descriptions of
+# See mods-available/ldap for more detailed descriptions of
# configuration items.
#
server ldap_sync {
}
# (4) Define a detail file writer.
-# See raddb/modules/detail.example.com
+# See mods-available/detail.example.com
# (5) Define a virtual server to handle pre/post-proxy re-writing
server home.example.com {