diff --git a/hosted/config/systemd/freeradius.service b/hosted/config/systemd/freeradius.service index f4a795b..5cebcb1 100644 --- a/hosted/config/systemd/freeradius.service +++ b/hosted/config/systemd/freeradius.service @@ -24,12 +24,51 @@ Environment=TZ=UTC # a leak somewhere. MemoryLimit=2G +# Ensure the daemon can still write its pidfile after it drops +# privileges. Combination of options that work on a variety of +# systems. Test very carefully if you alter these lines. RuntimeDirectory=freeradius RuntimeDirectoryMode=0775 +# This does not work on Debian Jessie: +User=freerad +Group=freerad +# This does not work on Ubuntu Bionic: +ExecStartPre=/bin/chown freerad:freerad /var/run/freeradius + ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -lstdout -ExecStart=/usr/sbin/freeradius $FREERADIUS_OPTIONS +ExecStart=/usr/sbin/freeradius -f $FREERADIUS_OPTIONS Restart=on-failure -RestartSec=5 +RestartSec=3 +ExecReload=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cxm -lstdout +ExecReload=/bin/kill -HUP $MAINPID + +# Don't elevate privileges after starting +NoNewPrivileges=true + +# Allow binding to secure ports, broadcast addresses, and raw interfaces. +#CapabilityBoundingSet=CAP_NET_ADMIN CAP_NET_BIND_SERVICE CAP_NET_BROADCAST CAP_NET_RAW CAP_SETUID CAP_SETGID CAP_CHOWN CAP_DAC_OVERRIDE + +# Private /tmp that isn't shared by other processes +PrivateTmp=true + +# cgroups are readable only by radiusd, and child processes +ProtectControlGroups=true + +# don't load new kernel modules +ProtectKernelModules=true + +# don't tune kernel parameters +ProtectKernelTunables=true + +# Only allow native system calls +SystemCallArchitectures=native + +# We shouldn't be writing to the configuration directory +ReadOnlyDirectories=/etc/freeradius/ + +# We can read and write to the log directory. +ReadWriteDirectories=/var/log/freeradius/ [Install] WantedBy=multi-user.target + diff --git a/hosted/mods-enabled/raw b/hosted/mods-enabled/raw deleted file mode 100644 index f03b529..0000000 --- a/hosted/mods-enabled/raw +++ /dev/null @@ -1,2 +0,0 @@ -raw { -} \ No newline at end of file diff --git a/hosted/mods-enabled/rest b/hosted/mods-enabled/rest deleted file mode 100644 index a41443f..0000000 --- a/hosted/mods-enabled/rest +++ /dev/null @@ -1,300 +0,0 @@ -rest { - # - # This subsection configures the tls related items - # that control how FreeRADIUS connects to a HTTPS - # server. - # - tls { - # Certificate Authorities: - # "ca_file" (libcurl option CURLOPT_ISSUERCERT). - # File containing a single CA, which is the issuer of the server - # certificate. - # "ca_info_file" (libcurl option CURLOPT_CAINFO). - # File containing a bundle of certificates, which allow to handle - # certificate chain validation. - # "ca_path" (libcurl option CURLOPT_CAPATH). - # Directory holding CA certificates to verify the peer with. -# ca_file = ${certdir}/cacert.pem -# ca_info_file = ${certdir}/cacert_bundle.pem -# ca_path = ${certdir} - -# certificate_file = /path/to/radius.crt -# private_key_file = /path/to/radius.key -# private_key_password = "supersecret" -# random_file = /dev/urandom - - # Server certificate verification requirements. Can be: - # "no" (don't even bother trying) - # "yes" (verify the cert was issued by one of the - # trusted CAs) - # - # The default is "yes" -# check_cert = yes - - # Server certificate CN verification requirements. Can be: - # "no" (don't even bother trying) - # "yes" (verify the CN in the certificate matches the host - # in the URI) - # - # The default is "yes" -# check_cert_cn = yes - } - - # rlm_rest will open a connection to the server specified in connect_uri - # to populate the connection cache, ready for the first request. - # The server will not start if the server specified is unreachable. - # - # If you wish to disable this pre-caching and reachability check, - # comment out the configuration item below. - #connect_uri = "http://connectone.me:31668" - connect_uri = "http://#API_HOST#:#API_PORT#/" - - # - # How long before new connection attempts timeout, defaults to 4.0 seconds. - # -# connect_timeout = 4.0 - - # - # Specify HTTP protocol version to use. one of '1.0', '1.1', '2.0', '2.0+auto', - # '2.0+tls' or 'default'. (libcurl option CURLOPT_HTTP_VERSION) - # -# http_negotiation = 1.1 - - # - # The following config items can be used in each of the sections. - # The sections themselves reflect the sections in the server. - # For example if you list rest in the authorize section of a virtual server, - # the settings from the authorize section here will be used. - # - # The following config items may be listed in any of the sections: - # uri - to send the request to. - # method - HTTP method to use, one of 'get', 'post', 'put', 'patch', - # 'delete' or any custom HTTP method. - # body - The format of the HTTP body sent to the remote server. - # May be 'none', 'post' or 'json', defaults to 'none'. - # attr_num - If true, the attribute number is supplied for each attribute. - # Defaults to false. - # raw_value - If true, enumerated attribute values are provided as numeric - # values. Defaults to false. - # data - Send custom freeform data in the HTTP body. Content-type - # may be specified with 'body'. Will be expanded. - # Values from expansion will not be escaped, this should be - # done using the appropriate xlat method e.g. %{urlencode:}. - # force_to - Force the response to be decoded with this decoder. - # May be 'plain' (creates reply:REST-HTTP-Body), 'post' - # or 'json'. - # tls - TLS settings for HTTPS. - # auth - HTTP auth method to use, one of 'none', 'srp', 'basic', - # 'digest', 'digest-ie', 'gss-negotiate', 'ntlm', - # 'ntlm-winbind', 'any', 'safe'. defaults to 'none'. - # username - User to authenticate as, will be expanded. - # password - Password to use for authentication, will be expanded. - # require_auth - Require HTTP authentication. - # timeout - HTTP request timeout in seconds, defaults to 4.0. - # chunk - Chunk size to use. If set, HTTP chunked encoding is used to - # send data to the REST server. Make sure that this is large - # enough to fit your largest attribute value's text - #  representation. - # A number like 8192 is good. - # - # Additional HTTP headers may be specified with control:REST-HTTP-Header. - # The values of those attributes should be in the format: - # - # control:REST-HTTP-Header := ": " - # - # The control:REST-HTTP-Header attributes will be consumed - # (i.e. deleted) after each call to the rest module, and each - # %{rest:} expansion. This is so that headers from one REST - # call do not affect headers from a different REST call. - # - # Body encodings are the same for requests and responses - # - # POST - All attributes and values are urlencoded - # [outer.][:]=&[outer.][:]= - # - # JSON - All attributes and values are escaped according to the JSON specification - # - attribute Name of the attribute. - # - attr_num Number of the attribute. Only available if the configuration item - # 'attr_num' is enabled. - # - type Type of the attribute (e.g. "integer", "string", "ipaddr", "octets", ...). - # - value Attribute value, for enumerated attributes the human readable value is - # provided and not the numeric value (Depends on the 'raw_value' config item). - # { - # "":{ - # "attr_num":, - # "type":"", - # "value":[,,] - # }, - # "":{ - # "attr_num":, - # "type":"", - # "value":[...] - # }, - # "":{ - # "attr_num":, - # "type":"", - # "value":[...] - # }, - # } - # - # The response format adds three optional fields: - # - do_xlat If true, any values will be xlat expanded. Defaults to true. - # - is_json If true, any nested JSON data will be copied to the attribute - # in string form. Defaults to true. - # - op Controls how the attribute is inserted into the target list. - # Defaults to ':='. To create multiple attributes from multiple - # values, this should be set to '+=', otherwise only the last - # value will be used, and it will be assigned to a single - # attribute. - # { - # "":{ - # "is_json":, - # "do_xlat":, - # "op":"", - # "value":[,,] - # }, - # "":"value", - # "":{ - # "value":[,,], - # "op":"+=" - # } - # } - - # - # Module return codes are determined by HTTP response codes. These vary depending on the - # section. - # - # If the body is processed and found to be malformed or unsupported fail will be returned. - # If the body is processed and found to contain attribute updated will be returned, - # except in the case of a 401 code. - # - - # Authorize/Authenticate - # - # Code Meaning Process body Module code - # 404 not found no notfound - # 410 gone no notfound - # 403 forbidden no userlock - # 401 unauthorized yes reject - # 204 no content no ok - # 2xx successful yes ok/updated - # 5xx server error no fail - # xxx - no invalid - # - # The status code is held in %{reply:REST-HTTP-Status-Code}. - # - authorize { - uri = "${..connect_uri}radius/auth" - method = 'post' - body = 'json' - data = '{"ip": "%{Packet-Src-IP-Address}", "hotspot-group": "%{raw:Called-Station-Id}", "hotspot-id": "%{raw:NAS-Identifier}"}' - force_to = 'json' - auth = 'none' - require_auth = no - timeout = 4.000000 - } -# authorize { -# uri = "${..connect_uri}/user/%{User-Name}/mac/%{Called-Station-ID}?action=authorize" -# method = 'get' -# tls = ${..tls} -# } -# authenticate { -# uri = "${..connect_uri}/user/%{User-Name}/mac/%{Called-Station-ID}?action=authenticate" -# method = 'get' -# tls = ${..tls} -# } - - # Preacct/Accounting/Post-auth/Pre-Proxy/Post-Proxy - # - # Code Meaning Process body Module code - # 204 no content no ok - # 2xx successful yes ok/updated - # 5xx server error no fail - # xxx - no invalid -# preacct { -# uri = "${..connect_uri}/user/%{User-Name}/sessions/%{Acct-Unique-Session-ID}?action=preacct" -# method = 'post' -# tls = ${..tls} -# } -# accounting { -# uri = "${..connect_uri}/user/%{User-Name}/sessions/%{Acct-Unique-Session-ID}?action=accounting" -# method = 'post' -# tls = ${..tls} -# } -# post-auth { -# uri = "${..connect_uri}/user/%{User-Name}/mac/%{Called-Station-ID}?action=post-auth" -# method = 'post' -# tls = ${..tls} -# } -# pre-proxy { -# uri = "${..connect_uri}/user/%{User-Name}/mac/%{Called-Station-ID}?action=pre-proxy" -# method = 'post' -# tls = ${..tls} -# } -# post-proxy { -# uri = "${..connect_uri}/user/%{User-Name}/mac/%{Called-Station-ID}?action=post-proxy" -# method = 'post' -# tls = ${..tls} -# } - - # - # The connection pool is used to pool outgoing connections. - # - pool { - # Connections to create during module instantiation. - # If the server cannot create specified number of - # connections during instantiation it will exit. - # Set to 0 to allow the server to start without the - # web service being available. - start = ${thread[pool].start_servers} - - # Minimum number of connections to keep open - min = ${thread[pool].min_spare_servers} - - # Maximum number of connections - # - # If these connections are all in use and a new one - # is requested, the request will NOT get a connection. - # - # Setting 'max' to LESS than the number of threads means - # that some threads may starve, and you will see errors - # like 'No connections available and at max connection limit' - # - # Setting 'max' to MORE than the number of threads means - # that there are more connections than necessary. - max = ${thread[pool].max_servers} - - # Spare connections to be left idle - # - # NOTE: Idle connections WILL be closed if "idle_timeout" - # is set. This should be less than or equal to "max" above. - spare = ${thread[pool].max_spare_servers} - - # Number of uses before the connection is closed - # - # 0 means "infinite" - uses = 0 - - # The number of seconds to wait after the server tries - # to open a connection, and fails. During this time, - # no new connections will be opened. - retry_delay = 30 - - # The lifetime (in seconds) of the connection - lifetime = 0 - - # idle timeout (in seconds). A connection which is - # unused for this length of time will be closed. - idle_timeout = 60 - - # NOTE: All configuration settings are enforced. If a - # connection is closed because of "idle_timeout", - # "uses", or "lifetime", then the total number of - # connections MAY fall below "min". When that - # happens, it will open a new connection. It will - # also log a WARNING message. - # - # The solution is to either lower the "min" connections, - # or increase lifetime/idle_timeout. - } -} diff --git a/hosted/mods-enabled/sql b/hosted/mods-enabled/sql deleted file mode 100644 index 1834a9e..0000000 --- a/hosted/mods-enabled/sql +++ /dev/null @@ -1,371 +0,0 @@ -# -*- text -*- -## -## mods-available/sql -- SQL modules -## -## $Id: 7bcb664d32fecca0cd20c1d81bac13f0e1b9991b $ - -###################################################################### -# -# Configuration for the SQL module -# -# The database schemas and queries are located in subdirectories: -# -# sql//main/schema.sql Schema -# sql//main/queries.conf Authorisation and Accounting queries -# -# Where "DB" is mysql, mssql, oracle, or postgresql. -# -# The name used to query SQL is sql_user_name, which is set in the file -# -# raddb/mods-config/sql/main/${dialect}/queries.conf -# -# If you are using realms, that configuration should be changed to use -# the Stripped-User-Name attribute. See the comments around sql_user_name -# for more information. -# - -sql { - # - # The dialect of SQL being used. - # - # Allowed dialects are: - # - # mssql - # mysql - # oracle - # postgresql - # sqlite - # mongo - # - dialect = "postgresql" - - # - # The driver module used to execute the queries. Since we - # don't know which SQL drivers are being used, the default is - # "rlm_sql_null", which just logs the queries to disk via the - # "logfile" directive, below. - # - # In order to talk to a real database, delete the next line, - # and uncomment the one after it. - # - # If the dialect is "mssql", then the driver should be set to - # one of the following values, depending on your system: - # - # rlm_sql_db2 - # rlm_sql_firebird - # rlm_sql_freetds - # rlm_sql_iodbc - # rlm_sql_unixodbc - # -# driver = "rlm_sql_null" - driver = "rlm_sql_${dialect}" - - # - # Driver-specific subsections. They will only be loaded and - # used if "driver" is something other than "rlm_sql_null". - # When a real driver is used, the relevant driver - # configuration section is loaded, and all other driver - # configuration sections are ignored. - # - sqlite { - # Path to the sqlite database - filename = "/etc/freeradius/freeradius.db" - - # How long to wait for write locks on the database to be - # released (in ms) before giving up. - busy_timeout = 200 - - # If the file above does not exist and bootstrap is set - # a new database file will be created, and the SQL statements - # contained within the bootstrap file will be executed. - bootstrap = "${modconfdir}/${..:name}/main/sqlite/schema.sql" - } - - mysql { - # If any of the files below are set, TLS encryption is enabled - tls { - ca_file = "/etc/ssl/certs/my_ca.crt" - ca_path = "/etc/ssl/certs/" - certificate_file = "/etc/ssl/certs/private/client.crt" - private_key_file = "/etc/ssl/certs/private/client.key" - cipher = "DHE-RSA-AES256-SHA:AES128-SHA" - - tls_required = yes - tls_check_cert = no - tls_check_cert_cn = no - } - - # If yes, (or auto and libmysqlclient reports warnings are - # available), will retrieve and log additional warnings from - # the server if an error has occured. Defaults to 'auto' - warnings = auto - } - - postgresql { - - # unlike MySQL, which has a tls{} connection configuration, postgresql - # uses its connection parameters - see the radius_db option below in - # this file - - # Send application_name to the postgres server - # Only supported in PG 9.0 and greater. Defaults to no. - send_application_name = yes - - # - # The default application name is "FreeRADIUS - .." with the current version. - # The application name can be customized here to any non-zero value. - # -# application_name = "" - } - - # - # Configuration for Mongo. - # - # Note that the Mongo driver is experimental. The FreeRADIUS developers - # are unable to help with the syntax of the Mongo queries. Please see - # the Mongo documentation for that syntax. - # - # The Mongo driver supports only the following methods: - # - # aggregate - # findAndModify - # findOne - # insert - # - # For examples, see the query files: - # - # raddb/mods-config/sql/main/mongo/queries.conf - # raddb/mods-config/sql/main/ippool/queries.conf - # - # In order to use findAndModify with an aggretation pipleline, make - # sure that you are running MongoDB version 4.2 or greater. FreeRADIUS - # assumes that the paramaters passed to the methods are supported by the - # version of MongoDB which it is connected to. - # - mongo { - # - # The application name to use. - # - appname = "freeradius" - - # - # The TLS parameters here map directly to the Mongo TLS configuration - # - tls { - certificate_file = /path/to/file - certificate_password = "password" - ca_file = /path/to/file - ca_dir = /path/to/directory - crl_file = /path/to/file - weak_cert_validation = false - allow_invalid_hostname = false - } - } - - # Connection info: - # - server = "#PG_HOST#" - port = #PG_PORT# - login = "#PG_USER#" - password = "#PG_PASS#" - - # Connection info for Mongo - # Authentication Without SSL - # server = "mongodb://USER:PASSWORD@192.16.0.2:PORT/DATABASE?authSource=admin&ssl=false" - - # Authentication With SSL - # server = "mongodb://USER:PASSWORD@192.16.0.2:PORT/DATABASE?authSource=admin&ssl=true" - - # Authentication with Certificate - # Use this command for retrieve Derived username: - # openssl x509 -in mycert.pem -inform PEM -subject -nameopt RFC2253 - # server = mongodb://@192.168.0.2:PORT/DATABASE?authSource=$external&ssl=true&authMechanism=MONGODB-X509 - - # Database table configuration for everything except Oracle - radius_db = "#PG_DB#" - - # If you are using Oracle then use this instead -# radius_db = "(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521))(CONNECT_DATA=(SID=your_sid)))" - - # If you're using postgresql this can also be used instead of the connection info parameters -# radius_db = "dbname=radius host=localhost user=radius password=raddpass" - - # Postgreql doesn't take tls{} options in its module config like mysql does - if you want to - # use SSL connections then use this form of connection info parameter -# radius_db = "host=localhost port=5432 dbname=radius user=radius password=raddpass sslmode=verify-full sslcert=/etc/ssl/client.crt sslkey=/etc/ssl/client.key sslrootcert=/etc/ssl/ca.crt" - - # If you want both stop and start records logged to the - # same SQL table, leave this as is. If you want them in - # different tables, put the start table in acct_table1 - # and stop table in acct_table2 - acct_table1 = "radacct" - acct_table2 = "radacct" - - # Allow for storing data after authentication - postauth_table = "radpostauth" - - # Tables containing 'check' items - authcheck_table = "radcheck" - groupcheck_table = "radgroupcheck" - - # Tables containing 'reply' items - authreply_table = "radreply" - groupreply_table = "radgroupreply" - - # Table to keep group info - usergroup_table = "radusergroup" - - # If set to 'yes' (default) we read the group tables unless Fall-Through = no in the reply table. - # If set to 'no' we do not read the group tables unless Fall-Through = yes in the reply table. -# read_groups = yes - - # If set to 'yes' (default) we read profiles unless Fall-Through = no in the groupreply table. - # If set to 'no' we do not read profiles unless Fall-Through = yes in the groupreply table. -# read_profiles = yes - - # Remove stale session if checkrad does not see a double login - delete_stale_sessions = yes - - # Write SQL queries to a logfile. This is potentially useful for tracing - # issues with authorization queries. See also "logfile" directives in - # mods-config/sql/main/*/queries.conf. You can enable per-section logging - # by enabling "logfile" there, or global logging by enabling "logfile" here. - # - # Per-section logging can be disabled by setting "logfile = ''" -# logfile = ${logdir}/sqllog.sql - - # Set the maximum query duration and connection timeout - # for rlm_sql_mysql. -# query_timeout = 5 - - # As of v3, the "pool" section has replaced the - # following v2 configuration items: - # - # num_sql_socks - # connect_failure_retry_delay - # lifetime - # max_queries - - # - # The connection pool is used to pool outgoing connections. - # - # When the server is not threaded, the connection pool - # limits are ignored, and only one connection is used. - # - # If you want to have multiple SQL modules re-use the same - # connection pool, use "pool = name" instead of a "pool" - # section. e.g. - # - # sql sql1 { - # ... - # pool { - # ... - # } - # } - # - # # sql2 will use the connection pool from sql1 - # sql sql2 { - # ... - # pool = sql1 - # } - # - pool { - # Connections to create during module instantiation. - # If the server cannot create specified number of - # connections during instantiation it will exit. - # Set to 0 to allow the server to start without the - # database being available. - start = ${thread[pool].start_servers} - - # Minimum number of connections to keep open - min = ${thread[pool].min_spare_servers} - - # Maximum number of connections - # - # If these connections are all in use and a new one - # is requested, the request will NOT get a connection. - # - # Setting 'max' to LESS than the number of threads means - # that some threads may starve, and you will see errors - # like 'No connections available and at max connection limit' - # - # Setting 'max' to MORE than the number of threads means - # that there are more connections than necessary. - max = ${thread[pool].max_servers} - - # Spare connections to be left idle - # - # NOTE: Idle connections WILL be closed if "idle_timeout" - # is set. This should be less than or equal to "max" above. - spare = ${thread[pool].max_spare_servers} - - # Number of uses before the connection is closed - # - # 0 means "infinite" - uses = 0 - - # The number of seconds to wait after the server tries - # to open a connection, and fails. During this time, - # no new connections will be opened. - retry_delay = 30 - - # The lifetime (in seconds) of the connection - lifetime = 0 - - # idle timeout (in seconds). A connection which is - # unused for this length of time will be closed. - idle_timeout = 60 - - # NOTE: All configuration settings are enforced. If a - # connection is closed because of "idle_timeout", - # "uses", or "lifetime", then the total number of - # connections MAY fall below "min". When that - # happens, it will open a new connection. It will - # also log a WARNING message. - # - # The solution is to either lower the "min" connections, - # or increase lifetime/idle_timeout. - } - - # Set to 'yes' to read radius clients from the database ('nas' table) - # Clients will ONLY be read on server startup. - # - # A client can be link to a virtual server via the SQL - # module. This link is done via the following process: - # - # If there is no listener in a virtual server, SQL clients - # are added to the global list for that virtual server. - # - # If there is a listener, and the first listener does not - # have a "clients=..." configuration item, SQL clients are - # added to the global list. - # - # If there is a listener, and the first one does have a - # "clients=..." configuration item, SQL clients are added to - # that list. The client { ...} ` configured in that list are - # also added for that listener. - # - # The only issue is if you have multiple listeners in a - # virtual server, each with a different client list, then - # the SQL clients are added only to the first listener. - # -# read_clients = yes - - # Table to keep radius client info - client_table = "nas" - - # - # The group attribute specific to this instance of rlm_sql - # - - # This entry should be used for additional instances (sql foo {}) - # of the SQL module. -# group_attribute = "${.:instance}-SQL-Group" - - # This entry should be used for the default instance (sql {}) - # of the SQL module. - group_attribute = "SQL-Group" - - # Read database-specific queries - $INCLUDE ${modconfdir}/${.:name}/main/${dialect}/queries.conf -} diff --git a/hosted/sites-enabled/default b/hosted/sites-enabled/default deleted file mode 100644 index 7a7dd83..0000000 --- a/hosted/sites-enabled/default +++ /dev/null @@ -1,1159 +0,0 @@ -###################################################################### -# -# As of 2.0.0, FreeRADIUS supports virtual hosts using the -# "server" section, and configuration directives. -# -# Virtual hosts should be put into the "sites-available" -# directory. Soft links should be created in the "sites-enabled" -# directory to these files. This is done in a normal installation. -# -# If you are using 802.1X (EAP) authentication, please see also -# the "inner-tunnel" virtual server. You will likely have to edit -# that, too, for authentication to work. -# -# $Id: 78b7ae7f37a487276e963d8e9b67913285e8ab18 $ -# -###################################################################### -# -# Read "man radiusd" before editing this file. See the section -# titled DEBUGGING. It outlines a method where you can quickly -# obtain the configuration you want, without running into -# trouble. See also "man unlang", which documents the format -# of this file. -# -# This configuration is designed to work in the widest possible -# set of circumstances, with the widest possible number of -# authentication methods. This means that in general, you should -# need to make very few changes to this file. -# -# The best way to configure the server for your local system -# is to CAREFULLY edit this file. Most attempts to make large -# edits to this file will BREAK THE SERVER. Any edits should -# be small, and tested by running the server with "radiusd -X". -# Once the edits have been verified to work, save a copy of these -# configuration files somewhere. (e.g. as a "tar" file). Then, -# make more edits, and test, as above. -# -# There are many "commented out" references to modules such -# as ldap, sql, etc. These references serve as place-holders. -# If you need the functionality of that module, then configure -# it in radiusd.conf, and un-comment the references to it in -# this file. In most cases, those small changes will result -# in the server being able to connect to the DB, and to -# authenticate users. -# -###################################################################### - -server default { -# -# If you want the server to listen on additional addresses, or on -# additional ports, you can use multiple "listen" sections. -# -# Each section make the server listen for only one type of packet, -# therefore authentication and accounting have to be configured in -# different sections. -# -# The server ignore all "listen" section if you are using '-i' and '-p' -# on the command line. -# -listen { - # Type of packets to listen for. - # Allowed values are: - # auth listen for authentication packets - # acct listen for accounting packets - # auth+acct listen for both authentication and accounting packets - # proxy IP to use for sending proxied packets - # detail Read from the detail file. For examples, see - # raddb/sites-available/copy-acct-to-home-server - # status listen for Status-Server packets. For examples, - # see raddb/sites-available/status - # coa listen for CoA-Request and Disconnect-Request - # packets. For examples, see the file - # raddb/sites-available/coa - # - type = auth - - # Note: "type = proxy" lets you control the source IP used for - # proxying packets, with some limitations: - # - # * A proxy listener CANNOT be used in a virtual server section. - # * You should probably set "port = 0". - # * Any "clients" configuration will be ignored. - # - # See also proxy.conf, and the "src_ipaddr" configuration entry - # in the sample "home_server" section. When you specify the - # source IP address for packets sent to a home server, the - # proxy listeners are automatically created. - - # ipaddr/ipv4addr/ipv6addr - IP address on which to listen. - # If multiple ones are listed, only the first one will - # be used, and the others will be ignored. - # - # The configuration options accept the following syntax: - # - # ipv4addr - IPv4 address (e.g.192.0.2.3) - # - wildcard (i.e. *) - # - hostname (radius.example.com) - # Only the A record for the host name is used. - # If there is no A record, an error is returned, - # and the server fails to start. - # - # ipv6addr - IPv6 address (e.g. 2001:db8::1) - # - wildcard (i.e. *) - # - hostname (radius.example.com) - # Only the AAAA record for the host name is used. - # If there is no AAAA record, an error is returned, - # and the server fails to start. - # - # ipaddr - IPv4 address as above - # - IPv6 address as above - # - wildcard (i.e. *), which means IPv4 wildcard. - # - hostname - # If there is only one A or AAAA record returned - # for the host name, it is used. - # If multiple A or AAAA records are returned - # for the host name, only the first one is used. - # If both A and AAAA records are returned - # for the host name, only the A record is used. - # - # ipv4addr = * - # ipv6addr = * - ipaddr = * - - # Port on which to listen. - # Allowed values are: - # integer port number (1812) - # 0 means "use /etc/services for the proper port" - port = 1812 - - # Some systems support binding to an interface, in addition - # to the IP address. This feature isn't strictly necessary, - # but for sites with many IP addresses on one interface, - # it's useful to say "listen on all addresses for eth0". - # - # If your system does not support this feature, you will - # get an error if you try to use it. - # -# interface = eth0 - - # Per-socket lists of clients. This is a very useful feature. - # - # The name here is a reference to a section elsewhere in - # radiusd.conf, or clients.conf. Having the name as - # a reference allows multiple sockets to use the same - # set of clients. - # - # If this configuration is used, then the global list of clients - # is IGNORED for this "listen" section. Take care configuring - # this feature, to ensure you don't accidentally disable a - # client you need. - # - # See clients.conf for the configuration of "per_socket_clients". - # -# clients = per_socket_clients - - # - # Set the default UDP receive buffer size. In most cases, - # the default values set by the kernel are fine. However, in - # some cases the NASes will send large packets, and many of - # them at a time. It is then possible to overflow the - # buffer, causing the kernel to drop packets before they - # reach FreeRADIUS. Increasing the size of the buffer will - # avoid these packet drops. - # -# recv_buff = 65536 - - # - # Connection limiting for sockets with "proto = tcp". - # - # This section is ignored for other kinds of sockets. - # - limit { - # - # Limit the number of simultaneous TCP connections to the socket - # - # The default is 16. - # Setting this to 0 means "no limit" - max_connections = 16 - - # The per-socket "max_requests" option does not exist. - - # - # The lifetime, in seconds, of a TCP connection. After - # this lifetime, the connection will be closed. - # - # Setting this to 0 means "forever". - lifetime = 0 - - # - # The idle timeout, in seconds, of a TCP connection. - # If no packets have been received over the connection for - # this time, the connection will be closed. - # - # Setting this to 0 means "no timeout". - # - # We STRONGLY RECOMMEND that you set an idle timeout. - # - idle_timeout = 30 - } -} - -# -# This second "listen" section is for listening on the accounting -# port, too. -# -listen { - ipaddr = * -# ipv6addr = :: - port = 1813 - type = acct -# interface = eth0 -# clients = per_socket_clients - - limit { - # The number of packets received can be rate limited via the - # "max_pps" configuration item. When it is set, the server - # tracks the total number of packets received in the previous - # second. If the count is greater than "max_pps", then the - # new packet is silently discarded. This helps the server - # deal with overload situations. - # - # The packets/s counter is tracked in a sliding window. This - # means that the pps calculation is done for the second - # before the current packet was received. NOT for the current - # wall-clock second, and NOT for the previous wall-clock second. - # - # Useful values are 0 (no limit), or 100 to 10000. - # Values lower than 100 will likely cause the server to ignore - # normal traffic. Few systems are capable of handling more than - # 10K packets/s. - # - # It is most useful for accounting systems. Set it to 50% - # more than the normal accounting load, and you can be sure that - # the server will never get overloaded - # -# max_pps = 0 - - # Only for "proto = tcp". These are ignored for "udp" sockets. - # -# idle_timeout = 0 -# lifetime = 0 -# max_connections = 0 - } -} - -# IPv6 versions of the above - read their full config to understand options -#listen { -# type = auth -# ipv6addr = :: # any. ::1 == localhost -# port = 0 -# interface = eth0 -# clients = per_socket_clients -# limit { -# max_connections = 16 -# lifetime = 0 -# idle_timeout = 30 -# } -#} - -#listen { -# ipv6addr = :: -# port = 0 -# type = acct -# interface = eth0 -# clients = per_socket_clients - -# limit { -# max_pps = 0 -# idle_timeout = 0 -# lifetime = 0 -# max_connections = 0 -# } -#} - -# Authorization. First preprocess (hints and huntgroups files), -# then realms, and finally look in the "users" file. -# -# Any changes made here should also be made to the "inner-tunnel" -# virtual server. -# -# The order of the realm modules will determine the order that -# we try to find a matching realm. -# -# Make *sure* that 'preprocess' comes before any realm if you -# need to setup hints for the remote radius server -authorize { - # - # Take a User-Name, and perform some checks on it, for spaces and other - # invalid characters. If the User-Name appears invalid, reject the - # request. - # - # See policy.d/filter for the definition of the filter_username policy. - # - filter_username - - # - # Some broken equipment sends passwords with embedded zeros. - # i.e. the debug output will show - # - # User-Password = "password\000\000" - # - # This policy will fix it to just be "password". - # -# filter_password - - # - # The preprocess module takes care of sanitizing some bizarre - # attributes in the request, and turning them into attributes - # which are more standard. - # - # It takes care of processing the 'raddb/mods-config/preprocess/hints' - # and the 'raddb/mods-config/preprocess/huntgroups' files. - preprocess - - # If you intend to use CUI and you require that the Operator-Name - # be set for CUI generation and you want to generate CUI also - # for your local clients then uncomment the operator-name - # below and set the operator-name for your clients in clients.conf -# operator-name - - # - # If you want to generate CUI for some clients that do not - # send proper CUI requests, then uncomment the - # cui below and set "add_cui = yes" for these clients in clients.conf -# cui - - # - # If you want to have a log of authentication requests, - # un-comment the following line. -# auth_log - - # - # The chap module will set 'Auth-Type := CHAP' if we are - # handling a CHAP request and Auth-Type has not already been set - chap - - # - # If the users are logging in with an MS-CHAP-Challenge - # attribute for authentication, the mschap module will find - # the MS-CHAP-Challenge attribute, and add 'Auth-Type := MS-CHAP' - # to the request, which will cause the server to then use - # the mschap module for authentication. - mschap - - # - # If you have a Cisco SIP server authenticating against - # FreeRADIUS, uncomment the following line, and the 'digest' - # line in the 'authenticate' section. - digest - - # - # The WiMAX specification says that the Calling-Station-Id - # is 6 octets of the MAC. This definition conflicts with - # RFC 3580, and all common RADIUS practices. If you are using - # old style WiMAX (non LTE) the un-commenting the "wimax" module - # here means that it will fix the Calling-Station-Id attribute to - # the normal format as specified in RFC 3580 Section 3.21. - # - # If you are using WiMAX 2.1 (LTE) then un-commenting will allow - # the module to handle SQN resyncronisation. Prior to calling the - # module it is necessary to populate the following attributes - # with the relevant keys: - # control:WiMAX-SIM-Ki - # control:WiMAX-SIM-OPc - # - # If WiMAX-Re-synchronization-Info is found in the request then - # the module will attempt to extract SQN and store it in - # control:WiMAX-SIM-SQN. Also a copy of RAND is extracted to - # control:WiMAX-SIM-RAND. - # - # If the SIM cannot be authenticated using Ki and OPc then reject - # will be returned. -# wimax - - # - # Look for IPASS style 'realm/', and if not found, look for - # '@realm', and decide whether or not to proxy, based on - # that. -# IPASS - - # - # Look for realms in user@domain format - suffix -# ntdomain - - # - # This module takes care of EAP-MD5, EAP-TLS, and EAP-LEAP - # authentication. - # - # It also sets the EAP-Type attribute in the request - # attribute list to the EAP type from the packet. - # - # The EAP module returns "ok" or "updated" if it is not yet ready - # to authenticate the user. The configuration below checks for - # "ok", and stops processing the "authorize" section if so. - # - # Any LDAP and/or SQL servers will not be queried for the - # initial set of packets that go back and forth to set up - # TTLS or PEAP. - # - # The "updated" check is commented out for compatibility with - # previous versions of this configuration, but you may wish to - # uncomment it as well; this will further reduce the number of - # LDAP and/or SQL queries for TTLS or PEAP. - # -# eap { -# ok = return -# updated = return -# } - - # - # Pull crypt'd passwords from /etc/passwd or /etc/shadow, - # using the system API's to get the password. If you want - # to read /etc/passwd or /etc/shadow directly, see the - # mods-available/passwd module. - # -# unix - - # - # Read the 'users' file. In v3, this is located in - # raddb/mods-config/files/authorize -# files - - # - # Look in an SQL database. The schema of the database - # is meant to mirror the "users" file. - # - # See "Authorization Queries" in mods-available/sql - -sql - - # - # If you are using /etc/smbpasswd, and are also doing - # mschap authentication, the un-comment this line, and - # configure the 'smbpasswd' module. -# smbpasswd - - # - # The ldap module reads passwords from the LDAP database. -# -ldap - - # - # If you're using Active Directory and PAP, then uncomment - # the following lines, and the "Auth-Type LDAP" section below. - # - # This will let you do PAP authentication to AD. - # -# if ((ok || updated) && User-Password && !control:Auth-Type) { -# update control { -# &Auth-Type := ldap -# } -# } - - # - # Enforce daily limits on time spent logged in. -# daily - - # - expiration - logintime - - # - # If no other module has claimed responsibility for - # authentication, then try to use PAP. This allows the - # other modules listed above to add a "known good" password - # to the request, and to do nothing else. The PAP module - # will then see that password, and use it to do PAP - # authentication. - # - # This module should be listed last, so that the other modules - # get a chance to set Auth-Type for themselves. - # - pap - - # - # If "status_server = yes", then Status-Server messages are passed - # through the following section, and ONLY the following section. - # This permits you to do DB queries, for example. If the modules - # listed here return "fail", then NO response is sent. - # -# Autz-Type Status-Server { -# -# } - - # - # RADIUS/TLS (or RadSec) connections are processed through - # this section. See sites-available/tls, and the configuration - # item "check_client_connections" for more information. - # - # The request contains TLS client certificate attributes, - # and nothing else. The debug output will print which - # attributes are available on your system. - # - # If the section returns "ok" or "updated", then the - # connection is accepted. Otherwise the connection is - # terminated. - # - Autz-Type New-TLS-Connection { - ok - } -} - - -# Authentication. -# -# -# This section lists which modules are available for authentication. -# Note that it does NOT mean 'try each module in order'. It means -# that a module from the 'authorize' section adds a configuration -# attribute 'Auth-Type := FOO'. That authentication type is then -# used to pick the appropriate module from the list below. -# - -# In general, you SHOULD NOT set the Auth-Type attribute. The server -# will figure it out on its own, and will do the right thing. The -# most common side effect of erroneously setting the Auth-Type -# attribute is that one authentication method will work, but the -# others will not. -# -# The common reasons to set the Auth-Type attribute by hand -# is to either forcibly reject the user (Auth-Type := Reject), -# or to or forcibly accept the user (Auth-Type := Accept). -# -# Note that Auth-Type := Accept will NOT work with EAP. -# -# Please do not put "unlang" configurations into the "authenticate" -# section. Put them in the "post-auth" section instead. That's what -# the post-auth section is for. -# -authenticate { - # - # PAP authentication, when a back-end database listed - # in the 'authorize' section supplies a password. The - # password can be clear-text, or encrypted. - Auth-Type PAP { - pap - } - - # - # Most people want CHAP authentication - # A back-end database listed in the 'authorize' section - # MUST supply a CLEAR TEXT password. Encrypted passwords - # won't work. - Auth-Type CHAP { - chap - } - - # - # MSCHAP authentication. - #Auth-Type MS-CHAP { - # mschap - #} - - # - # For old names, too. - # - #mschap - - # - # If you have a Cisco SIP server authenticating against - # FreeRADIUS, uncomment the following line, and the 'digest' - # line in the 'authorize' section. - digest - - # - # Pluggable Authentication Modules. -# pam - - # Uncomment it if you want to use ldap for authentication - # - # Note that this means "check plain-text password against - # the ldap database", which means that EAP won't work, - # as it does not supply a plain-text password. - # - # We do NOT recommend using this. LDAP servers are databases. - # They are NOT authentication servers. FreeRADIUS is an - # authentication server, and knows what to do with authentication. - # LDAP servers do not. - # - # However, it is necessary for Active Directory, because - # Active Directory won't give the passwords to FreeRADIUS. - # -# Auth-Type LDAP { -# ldap -# } - - # - # Allow EAP authentication. - #eap - - # - # The older configurations sent a number of attributes in - # Access-Challenge packets, which wasn't strictly correct. - # If you want to filter out these attributes, uncomment - # the following lines. - # -# Auth-Type eap { -# eap { -# handled = 1 -# } -# if (handled && (Response-Packet-Type == Access-Challenge)) { -# attr_filter.access_challenge.post-auth -# handled # override the "updated" code from attr_filter -# } -# } -} - - -# -# Pre-accounting. Decide which accounting type to use. -# -preacct { - preprocess - - # - # Merge Acct-[Input|Output]-Gigawords and Acct-[Input-Output]-Octets - # into a single 64bit counter Acct-[Input|Output]-Octets64. - # -# acct_counters64 - - # - # Session start times are *implied* in RADIUS. - # The NAS never sends a "start time". Instead, it sends - # a start packet, *possibly* with an Acct-Delay-Time. - # The server is supposed to conclude that the start time - # was "Acct-Delay-Time" seconds in the past. - # - # The code below creates an explicit start time, which can - # then be used in other modules. It will be *mostly* correct. - # Any errors are due to the 1-second resolution of RADIUS, - # and the possibility that the time on the NAS may be off. - # - # The start time is: NOW - delay - session_length - # - -# update request { -# &FreeRADIUS-Acct-Session-Start-Time = "%{expr: %l - %{%{Acct-Session-Time}:-0} - %{%{Acct-Delay-Time}:-0}}" -# } - - - # - # Ensure that we have a semi-unique identifier for every - # request, and many NAS boxes are broken. - acct_unique - - # - # Look for IPASS-style 'realm/', and if not found, look for - # '@realm', and decide whether or not to proxy, based on - # that. - # - # Accounting requests are generally proxied to the same - # home server as authentication requests. -# IPASS - suffix -# ntdomain - - # - # Read the 'acct_users' file - files -} - -# -# Accounting. Log the accounting data. -# -accounting { - # Update accounting packet by adding the CUI attribute - # recorded from the corresponding Access-Accept - # use it only if your NAS boxes do not support CUI themselves -# cui - # - # Create a 'detail'ed log of the packets. - # Note that accounting requests which are proxied - # are also logged in the detail file. - detail -# daily - - # Update the wtmp file - # - # If you don't use "radlast", you can delete this line. - unix - - # - # For Simultaneous-Use tracking. - # - # Due to packet losses in the network, the data here - # may be incorrect. There is little we can do about it. -# radutmp -# sradutmp - - # - # Return an address to the IP Pool when we see a stop record. - # - # Ensure that &control:Pool-Name is set to determine which - # pool of IPs are used. -# sqlippool - - # - # Log traffic to an SQL database. - # - # See "Accounting queries" in mods-available/sql - -sql - - # - # If you receive stop packets with zero session length, - # they will NOT be logged in the database. The SQL module - # will print a message (only in debugging mode), and will - # return "noop". - # - # You can ignore these packets by uncommenting the following - # three lines. Otherwise, the server will not respond to the - # accounting request, and the NAS will retransmit. - # -# if (noop) { -# ok -# } - - # Cisco VoIP specific bulk accounting -# pgsql-voip - - # For Exec-Program and Exec-Program-Wait - exec - - # Filter attributes from the accounting response. - attr_filter.accounting_response - - # - # See "Autz-Type Status-Server" for how this works. - # -# Acct-Type Status-Server { -# -# } -} - - -# Session database, used for checking Simultaneous-Use. Either the radutmp -# or rlm_sql module can handle this. -# The rlm_sql module is *much* faster -session { -# radutmp - - # - # See "Simultaneous Use Checking Queries" in mods-available/sql -# sql -} - - -# Post-Authentication -# Once we KNOW that the user has been authenticated, there are -# additional steps we can take. -post-auth { - # - # If you need to have a State attribute, you can - # add it here. e.g. for later CoA-Request with - # State, and Service-Type = Authorize-Only. - # -# if (!&reply:State) { -# update reply { -# State := "0x%{randstr:16h}" -# } -# } - - # - # Reject packets where User-Name != TLS-Client-Cert-Common-Name - # There is no reason for users to lie about their names. - # - # In general, User-Name == EAP Identity == TLS-Client-Cert-Common-Name - # -# verify_tls_client_common_name - - # - # If there is no Stripped-User-Name in the request, AND we have a client cert, - # then create a Stripped-User-Name from the TLS client certificate information. - # - # Note that this policy MUST be edited for your local system! - # We do not know which fields exist in which certificate, as - # there is no standard here. There is no way for us to have - # a default configuration which "just works" everywhere. We - # can only make recommendations. - # - # The Stripped-User-Name is updated so that it is logged in - # the various "username" fields. This logging means that you - # can associate a particular session with a particular client - # certificate. - # -# if (&EAP-Message && !&Stripped-User-Name && &TLS-Client-Cert-Serial) { -# update request { -# &Stripped-User-Name := "%{%{TLS-Client-Cert-Subject-Alt-Name-Email}:-%{%{TLS-Client-Cert-Common-Name}:-%{TLS-Client-Cert-Serial}}}" -# } -# - # - # Create a Class attribute which is a hash of a bunch - # of information which we hope exists. This - # attribute should be echoed back in - # Accounting-Request packets, which will let the - # administrator correlate authentication and - # accounting. - # -# update reply { -# Class += "%{md5:%{Calling-Station-Id}%{Called-Station-Id}%{TLS-Client-Cert-Subject-Alt-Name-Email}%{TLS-Client-Cert-Common-Name}%{TLS-Client-Cert-Serial}%{NAS-IPv6-Address}%{NAS-IP-Address}%{NAS-Identifier}%{NAS-Port}" -# } -# -# } - - # - # For EAP-TTLS and PEAP, add the cached attributes to the reply. - # The "session-state" attributes are automatically cached when - # an Access-Challenge is sent, and automatically retrieved - # when an Access-Request is received. - # - # The session-state attributes are automatically deleted after - # an Access-Reject or Access-Accept is sent. - # - # If both session-state and reply contain a User-Name attribute, remove - # the one in the reply if it is just a copy of the one in the request, so - # we don't end up with two User-Name attributes. - - if (session-state:User-Name && reply:User-Name && request:User-Name && (reply:User-Name == request:User-Name)) { - update reply { - &User-Name !* ANY - } - } - update { - &reply: += &session-state: - } - - # - # Refresh leases when we see a start or alive. Return an address to - # the IP Pool when we see a stop record. - # - # Ensure that &control:Pool-Name is set to determine which - # pool of IPs are used. -# sqlippool - - - # Create the CUI value and add the attribute to Access-Accept. - # Uncomment the line below if *returning* the CUI. -# cui - - # Create empty accounting session to make simultaneous check - # more robust. See the accounting queries configuration in - # raddb/mods-config/sql/main/*/queries.conf for details. - # - # The "sql_session_start" policy is defined in - # raddb/policy.d/accounting. See that file for more details. -# sql_session_start - - # - # If you want to have a log of authentication replies, - # un-comment the following line, and enable the - # 'detail reply_log' module. -# reply_log - - # - # After authenticating the user, do another SQL query. - # - # See "Authentication Logging Queries" in mods-available/sql - -sql - - # - # Un-comment the following if you want to modify the user's object - # in LDAP after a successful login. - # -# ldap - - # For Exec-Program and Exec-Program-Wait - exec - - # - # In order to calcualate the various keys for old style WiMAX - # (non LTE) you will need to define the WiMAX NAI, usually via - # - # update request { - # &WiMAX-MN-NAI = "%{User-Name}" - # } - # - # If you want various keys to be calculated, you will need to - # update the reply with "template" values. The module will see - # this, and replace the template values with the correct ones - # taken from the cryptographic calculations. e.g. - # - # update reply { - # &WiMAX-FA-RK-Key = 0x00 - # &WiMAX-MSK = "%{reply:EAP-MSK}" - # } - # - # You may want to delete the MS-MPPE-*-Keys from the reply, - # as some WiMAX clients behave badly when those attributes - # are included. See "raddb/modules/wimax", configuration - # entry "delete_mppe_keys" for more information. - # - # For LTE style WiMAX you need to populate the following with the - # relevant values: - # control:WiMAX-SIM-Ki - # control:WiMAX-SIM-OPc - # control:WiMAX-SIM-AMF - # control:WiMAX-SIM-SQN - # -# wimax - - # If there is a client certificate (EAP-TLS, sometimes PEAP - # and TTLS), then some attributes are filled out after the - # certificate verification has been performed. These fields - # MAY be available during the authentication, or they may be - # available only in the "post-auth" section. - # - # The first set of attributes contains information about the - # issuing certificate which is being used. The second - # contains information about the client certificate (if - # available). -# -# update reply { -# Reply-Message += "%{TLS-Cert-Serial}" -# Reply-Message += "%{TLS-Cert-Expiration}" -# Reply-Message += "%{TLS-Cert-Subject}" -# Reply-Message += "%{TLS-Cert-Issuer}" -# Reply-Message += "%{TLS-Cert-Common-Name}" -# Reply-Message += "%{TLS-Cert-Subject-Alt-Name-Email}" -# -# Reply-Message += "%{TLS-Client-Cert-Serial}" -# Reply-Message += "%{TLS-Client-Cert-Expiration}" -# Reply-Message += "%{TLS-Client-Cert-Subject}" -# Reply-Message += "%{TLS-Client-Cert-Issuer}" -# Reply-Message += "%{TLS-Client-Cert-Common-Name}" -# Reply-Message += "%{TLS-Client-Cert-Subject-Alt-Name-Email}" -# } - - # Insert class attribute (with unique value) into response, - # aids matching auth and acct records, and protects against duplicate - # Acct-Session-Id. Note: Only works if the NAS has implemented - # RFC 2865 behaviour for the class attribute, AND if the NAS - # supports long Class attributes. Many older or cheap NASes - # only support 16-octet Class attributes. -# insert_acct_class - - # MacSEC requires the use of EAP-Key-Name. However, we don't - # want to send it for all EAP sessions. Therefore, the EAP - # modules put required data into the EAP-Session-Id attribute. - # This attribute is never put into a request or reply packet. - # - # Uncomment the next few lines to copy the required data into - # the EAP-Key-Name attribute -# if (&reply:EAP-Session-Id) { -# update reply { -# EAP-Key-Name := &reply:EAP-Session-Id -# } -# } - - # Remove reply message if the response contains an EAP-Message - remove_reply_message_if_eap - - # - # Access-Reject packets are sent through the REJECT sub-section of the - # post-auth section. - # - # Add the ldap module name (or instance) if you have set - # 'edir = yes' in the ldap module configuration - # - # The "session-state" attributes are not available here. - # - Post-Auth-Type REJECT { - # log failed authentications in SQL, too. - -sql - attr_filter.access_reject - - # Insert EAP-Failure message if the request was - # rejected by policy instead of because of an - # authentication failure - # eap - - # Remove reply message if the response contains an EAP-Message - remove_reply_message_if_eap - } - - # - # Filter access challenges. - # - Post-Auth-Type Challenge { -# remove_reply_message_if_eap -# attr_filter.access_challenge.post-auth - } - - # - # The Client-Lost section will be run for a request when - # FreeRADIUS has given up waiting for an end-users client to - # respond. This is most useful for logging EAP sessions where - # the client stopped responding (likely because the - # certificate was not acceptable.) i.e. this is not for - # RADIUS clients, but for end-user systems. - # - # This will only be triggered by new packets arriving, - # and will be run at some point in the future *after* the - # original request has been discarded. - # - # Therefore the *ONLY* attributes that are available here - # are those in the session-state list. If you want data - # to log, make sure it is copied to &session-state: - # before the client stops responding. NONE of the other - # original attributes (request, reply, etc) will be - # available. - # - # This section will only be run if `postauth_client_lost` - # is enabled in the main configuration in `radiusd.conf`. - # - # Note that there are MANY reasons why an end users system - # might not respond: - # - # * it could not get the packet due to firewall issues - # * it could not get the packet due to a lossy network - # * the users system might not like the servers cert - # * the users system might not like something else... - # - # In some cases, the client is helpful enough to send us a - # TLS Alert message, saying what it doesn't like about the - # certificate. In other cases, no such message is available. - # - # All that we can know on the FreeRADIUS side is that we sent - # an Access-Challenge, and the client never sent anything - # else. The reasons WHY this happens are buried inside of - # the logs on the client system. No amount of looking at the - # FreeRADIUS logs, or poking the FreeRADIUS configuration - # will tell you why the client gave up. The answers are in - # the logs on the client side. And no, the FreeRADIUS team - # didn't write the client, so we don't know where those logs - # are, or how to get at them. - # - # Information about the TLS state changes is in the - # &session-state:TLS-Session-Information attribute. - # - Post-Auth-Type Client-Lost { - # - # Debug ALL of the TLS state changes done during the - # EAP negotiation. - # -# %{debug_attr:&session-state:TLS-Session-Information[*]} - - # - # Debug the LAST TLS state change done during the EAP - # negotiation. For errors, this is usually a TLS - # alert from the client saying something like - # "unknown CA". - # -# %{debug_attr:&session-state:TLS-Session-Information[n]} - - # - # Debug the last module failure message. This may be - # useful, or it may refer to a server-side failure - # which did not cause the client to stop talking to the server. - # -# %{debug_attr:&session-state:Module-Failure-Message} - } - - # - # If the client sends EAP-Key-Name in the request, - # then echo the real value back in the reply. - # - if (EAP-Key-Name && &reply:EAP-Session-Id) { - update reply { - &EAP-Key-Name := &reply:EAP-Session-Id - } - } -} - -# -# When the server decides to proxy a request to a home server, -# the proxied request is first passed through the pre-proxy -# stage. This stage can re-write the request, or decide to -# cancel the proxy. -# -# Only a few modules currently have this method. -# -pre-proxy { - # Before proxing the request add an Operator-Name attribute identifying - # if the operator-name is found for this client. - # No need to uncomment this if you have already enabled this in - # the authorize section. -# operator-name - - # The client requests the CUI by sending a CUI attribute - # containing one zero byte. - # Uncomment the line below if *requesting* the CUI. -# cui - - # Uncomment the following line if you want to change attributes - # as defined in the preproxy_users file. -# files - - # Uncomment the following line if you want to filter requests - # sent to remote servers based on the rules defined in the - # 'attrs.pre-proxy' file. -# attr_filter.pre-proxy - - # If you want to have a log of packets proxied to a home - # server, un-comment the following line, and the - # 'detail pre_proxy_log' section, above. -# pre_proxy_log -} - -# -# When the server receives a reply to a request it proxied -# to a home server, the request may be massaged here, in the -# post-proxy stage. -# -post-proxy { - - # If you want to have a log of replies from a home server, - # un-comment the following line, and the 'detail post_proxy_log' - # section, above. -# post_proxy_log - - # Uncomment the following line if you want to filter replies from - # remote proxies based on the rules defined in the 'attrs' file. -# attr_filter.post-proxy - - # - # If you are proxying LEAP, you MUST configure the EAP - # module, and you MUST list it here, in the post-proxy - # stage. - # - # You MUST also use the 'nostrip' option in the 'realm' - # configuration. Otherwise, the User-Name attribute - # in the proxied request will not match the user name - # hidden inside of the EAP packet, and the end server will - # reject the EAP request. - # - #eap - - # - # If the server tries to proxy a request and fails, then the - # request is processed through the modules in this section. - # - # The main use of this section is to permit robust proxying - # of accounting packets. The server can be configured to - # proxy accounting packets as part of normal processing. - # Then, if the home server goes down, accounting packets can - # be logged to a local "detail" file, for processing with - # radrelay. When the home server comes back up, radrelay - # will read the detail file, and send the packets to the - # home server. - # - # See the "mods-available/detail.example.com" file for more - # details on writing a detail file specifically for one - # destination. - # - # See the "sites-available/robust-proxy-accounting" virtual - # server for more details on reading this "detail" file. - # - # With this configuration, the server always responds to - # Accounting-Requests from the NAS, but only writes - # accounting packets to disk if the home server is down. - # -# Post-Proxy-Type Fail-Accounting { -# detail.example.com - - # - # Ensure a response is sent to the NAS now that the - # packet has been written to a detail file. - # -# acct_response -# } -} -} diff --git a/hosted/sites-enabled/dynamic-clients b/hosted/sites-enabled/dynamic-clients deleted file mode 100644 index 0f575e2..0000000 --- a/hosted/sites-enabled/dynamic-clients +++ /dev/null @@ -1,93 +0,0 @@ -# -*- text -*- -###################################################################### -# -# Sample configuration file for dynamically updating the list -# of RADIUS clients at run time. -# -# Everything is keyed off of a client "network". (e.g. 192.0.2/24) -# This configuration lets the server know that clients within -# that network are defined dynamically. -# -# When the server receives a packet from an unknown IP address -# within that network, it tries to find a dynamic definition -# for that client. If the definition is found, the IP address -# (and other configuration) is added to the server's internal -# cache of "known clients", with a configurable lifetime. -# -# Further packets from that IP address result in the client -# definition being found in the cache. Once the lifetime is -# reached, the client definition is deleted, and any new requests -# from that client are looked up as above. -# -# If the dynamic definition is not found, then the request is -# treated as if it came from an unknown client. i.e. It is -# silently discarded. -# -# As part of protection from Denial of Service (DoS) attacks, -# the server will add only one new client per second. This CANNOT -# be changed, and is NOT configurable. -# -# $Id: 0459a7f4b1dc824b1684e9d220a0410c69b3248a $ -# -###################################################################### - - - -# -# This is the virtual server referenced above by "dynamic_clients". -server dynamic_clients { - - # - # The only contents of the virtual server is the "authorize" section. - authorize { - - # - # Put any modules you want here. SQL, LDAP, "exec", - # Perl, etc. The only requirements is that the - # attributes MUST go into the control item list. - # - # The request that is processed through this section - # is EMPTY. There are NO attributes. The request is fake, - # and is NOT the packet that triggered the lookup of - # the dynamic client. - # - # The ONLY piece of useful information is either - # - # Packet-Src-IP-Address (IPv4 clients) - # Packet-Src-IPv6-Address (IPv6 clients) - # - # The attributes used to define a dynamic client mirror - # the configuration items in the "client" structure. - # - - # - # Example 1: Hard-code a client IP. This example is - # useless, but it documents the attributes - # you need. - # - if ("%{raw:NAS-Identifier}") { - if ("%{sql: select count(*) from nas where shortname='%{raw:NAS-Identifier}'}" == 1) { - update control { - &FreeRADIUS-Client-IP-Address = "%{Packet-Src-IP-Address}" - &FreeRADIUS-Client-Require-MA = no - &FreeRADIUS-Client-Secret = "%{sql: select nas.secret from nas where shortname='%{raw:NAS-Identifier}'}" - &FreeRADIUS-Client-Shortname = "%{sql: select shortname from nas where shortname='%{raw:NAS-Identifier}'}" - &FreeRADIUS-Client-NAS-Type = "other" - } - ok - } - else { - rest - } - } else { - reject - } - - # - # Tell the caller that the client was defined properly. - # - # If the authorize section does NOT return "ok", then - # the new client is ignored. - ok - } -}