+# -*- text -*-
+##
+## templates.conf -- configurations to be used in multiple places
+##
+## $Id$
+
######################################################################
#
# Version 2.0 has a useful new feature called "templates".
#
# Use templates by adding a line in radiusd.conf:
#
-# $INCLUDE ${confdir}/templates.conf.
-#
-# Templates are not included in the default configuration because
-# they can have large effects on the server configuration.
+# $INCLUDE templates.conf
#
# The goal of the templates is to have common configuration located
# in this file, and to list only the *differences* in the individual
# The templates are defined in the "templates" section, so that they
# do not affect the rest of the server configuration.
#
+# A section can reference a template by using "$template name"
+#
templates {
#
# The contents of the templates section are other
#
# This functionality lets you put common configuration into
# a template, and to put only the unique configuration
- # items in "proxy.conf".
+ # items in "proxy.conf". Each section in proxy.conf can
+ # then contain a line "$template home_server", which will
+ # cause it to reference this template.
#
home_server {
response_window = 20
# only list the IP address of that home server, and a
# line saying
#
- # template = example.com
+ # $template example_com
#
# That would tell FreeRADIUS to look in the section below
# for the rest of the configuration items.
#
- home_server example.com {
+ # For various reasons, you shouldn't have a "." in the template
+ # name. Doing so means that the server will be unable to find
+ # the template.
+ #
+ example_com {
type = auth
port = 1812
secret = testing123