start removing home server things from raddb

diff --git a/raddb/mods-available/couchbase b/raddb/mods-available/couchbase
index 6c2501c01b416b802da437455450c2af1a72f912..075a3b17b47e92852e107b690b904160bcf2ab23 100644 (file)
--- a/raddb/mods-available/couchbase
+++ b/raddb/mods-available/couchbase
@@ -84,12 +84,6 @@ couchbase {
 #                      password                        = 'test'
 #                      proto                           = tcp
 #                      require_message_authenticator   = yes
-
-                       # Uncomment to add a home_server with the same
-                       # attributes as the client.
-#                      coa_server {
-#                              response_window = 2.0
-#                      }
                }
 
                #

diff --git a/raddb/mods-available/ldap b/raddb/mods-available/ldap
index 62e8aa6c9502f223c729c18470ce5484feee0ae0..f178be825edd1e89fa6460dbe40f5fcaf9fe9a13 100644 (file)
--- a/raddb/mods-available/ldap
+++ b/raddb/mods-available/ldap
@@ -337,12 +337,6 @@ ldap {
 #                      password                        = 'test'
 #                      proto                           = tcp
 #                      require_message_authenticator   = yes
-
-                       # Uncomment to add a home_server with the same
-                       # attributes as the client.
-#                      coa_server {
-#                              response_window = 2.0
-#                      }
                }
 
                #

diff --git a/raddb/sites-available/status b/raddb/sites-available/status
index f416347ec9136216bbd04f3008ce9f64c0a07372..c27234dfad6ce82f4af4d21c98219da4b37ed9dc 100644 (file)
--- a/raddb/sites-available/status
+++ b/raddb/sites-available/status
@@ -99,10 +99,6 @@ server status {
 #              FreeRADIUS-Stats-Server-IP-Address = 192.0.2.2
 #              FreeRADIUS-Stats-Server-Port = 1812
 
-#
-#  You can also get exponentially weighted moving averages of
-#  response times (in usec) of home servers.  Just set the config
-#  item "historic_average_window" in a home_server section.
 #
 #  By default it is zero (don't calculate it).  Useful values
 #  are between 100, and 10,000.  The server will calculate and

diff --git a/raddb/templates.conf b/raddb/templates.conf
index 7b8b44e051c974c1a0a6e27a0cff50e621835df2..1fceeb0ecad64c2633c3879a1354ad63fcc01794 100644 (file)
--- a/raddb/templates.conf
+++ b/raddb/templates.conf
@@ -15,8 +15,8 @@
 #  The goal of the templates is to have common configuration located
 #  in this file, and to list only the *differences* in the individual
 #  sections.  This feature is most useful for sections like "clients"
-#  or "home_servers", where many may be defined, and each one has
-#  similar repeated configuration.
+#  where many may be defined, and each one has similar repeated
+#  configuration.
 #
 #  Something similar to templates can be done by putting common
 #  configuration into separate files, and using "$INCLUDE file...",
@@ -36,66 +36,6 @@ templates {
        #  the configuration files.
        #
 
-       #
-       #  This is a default template for the "home_server" section.
-       #  Note that there is no name for the section.
-       #
-       #  Any configuration item that is valid for a "home_server"
-       #  section is also valid here.  When a "home_server" section
-       #  is defined in proxy.conf, this section is referenced as
-       #  the template.
-       #
-       #  Configuration items that are explicitly listed in a
-       #  "home_server" section of proxy.conf are used in
-       #  preference to the configuration items listed here.
-       #
-       #  However, if a configuration item is NOT listed in a
-       #  "home_server" section of proxy.conf, then the value here
-       #  is used.
-       #
-       #  This functionality lets you put common configuration into
-       #  a template, and to put only the unique configuration
-       #  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
-               zombie_period = 40
-               revive_interval = 120
-               #
-               #  Etc.
-       }
-
-       #
-       #  You can also have named templates.  For example, if you
-       #  are proxying to 3 different home servers all at the same
-       #  site, with identical configurations (other than IP
-       #  addresses), you can use this named template.
-       #
-
-       #  Then, each "home_server" section in "proxy.conf" would
-       #  only list the IP address of that home server, and a
-       #  line saying
-       #
-       #               $template example_com
-       #
-       #  That would tell FreeRADIUS to look in the section below
-       #  for the rest of the configuration items.
-       #
-       #  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
-               response_window = 20
-               #
-               # Etc...
-       }
-
        #
        #  You can have templates for other sections, too, but they
        #  seem to be most useful for home_servers.

diff --git a/raddb/trigger.conf b/raddb/trigger.conf
index 7cb3ca65a80df18c5542f09232a1f04b6421dca6..c79580b8be9bec1a83e56dd4ad3ec41b75674e17 100644 (file)
--- a/raddb/trigger.conf
+++ b/raddb/trigger.conf
@@ -159,35 +159,6 @@ trigger {
                }
        }
 
-       # When a home server changes state.
-       # These traps are edge triggered.
-       home_server {
-               # common arguments: IP, port, identifier
-               args = "radiusAuthServerAddress a %{proxy-request:Packet-Dst-IP-Address} radiusAuthClientServerPortNumber i %{proxy-request:Packet-Dst-Port} radiusAuthServIdent s '%{home_server:instance}'"
-
-               # The home server has been marked "alive"
-               alive = "${snmptrap}::homeServerAlive ${args}"
-
-               # The home server has been marked "zombie"
-               zombie = "${snmptrap}::homeServerZombie ${args}"
-
-               # The home server has been marked "dead"
-               dead = "${snmptrap}::homeServerDead ${args}"
-       }
-
-       # When a pool of home servers changes state.
-       home_server_pool {
-               # common arguments
-               args = "radiusdConfigName s %{home_server:instance}"
-
-               # It has reverted to "normal" mode, where at least one
-               # home server is alive.
-               normal = "${snmptrap}::homeServerPoolNormal ${args}"
-
-               # It is in "fallback" mode, with all home servers "dead"
-               fallback = "${snmptrap}::homeServerPoolFallback ${args}"
-       }
-
        #  Triggers for specific modules.  These are NOT in the module
        #  configuration because they are global to all instances of the
        #  module.  You can have module-specific triggers, by placing a