May 2018 - Freeradius-Users - lists.freeradius.org

Radius Policy / Cisco
by Yahn do Amaral Almeida Pinheiro 29 May '18

29 May '18

Hello, I have a problem with my Radius X Cisco. In the radius are configured policys that are tied to the clients. But for some reason, when clients connect, some policys are not delivered to the Cisco. I wonder if there is any configuration to be changed in the radius to avoid this kind of problem.

2 1

Greetings
by Chrispin Simasiku Sitali 29 May '18

29 May '18

I am new to freeradius. I would like to install freeradius 3.x and use the users and clients.conf files only. My students use a variety of devices laptops, tablets, smart phone and different OS's Windows 7, 8, 10 and android. Any simple manual available or would someone point me in the right direction. Thank you Sitali CS -- Charles Lwanga College of Education, P. O. Box 660193, Monze, ZAMBIA. Mobile: +26 0979 869471 +26 0966 869471 SKYPE: Libsitali

2 2

Upgrade FreeRadius from 2.1.12 to 3.0.12 POSTGRESQL
by lorenzo farioli 29 May '18

29 May '18

Hello, I would need to do a migration of a postgresql database using the 2.1.12 freeradius application to a machine that uses freeradius 3.0.12 Seeing that the structures of the two databases generate by freeradius scripts are different I wanted to ask you it is possible to do this operation without importing the tables one by one -- *Lorenzo Farioli* Dba The content of this e-mail and any files transmitted with it may be of a confidential and/or private nature and are, in any case, intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, distributing and/or copying the contents of this e-mail is strictly prohibited in accordance with current privacy regulations and art. 616 of the penal code. Pursuant to the General Data Protection Regulation (GDPR) (EU) 2016/679, you are informed that any personal contact data may be stored in our company database in order to streamline information management (e.g. business relations, recruitment, workflow, etc.). If you received this e-mail by mistake, please notify the sender immediately by replying to this e-mail and follow with its deletion. If you want to receive our newsletter subscribe here: https://www.sorint.it/en/newsletter/

2 1

Re: Error while authenticating users on Wifi.
by Saurabh Lahoti 28 May '18

28 May '18

Dear Alan, Thanks for your help, issue git resolved with correct syntax. "ldap-instance-LDAP-Group" ---- *Thanks & Kind Regards,* Saurabh LAHOTI.

1 0

RADIUS packets larger than 4K over RadSec
by Stefan Paetow 27 May '18

27 May '18

Hi Alan, Arran, Matthew, I vaguely recall a while ago that there was a proposed change to FR 3 to allow RADIUS packets larger than 4096 octets over RadSec connections... was this ever implemented? I can't recall whether it was or not! With Regards Stefan Paetow Consultant, Trust and Identity t: +44 (0)1235 822 125 gpg: 0x3FCE5142 xmpp: stefanp(a)jabber.dev.ja.net skype: stefan.paetow.janet jisc.ac.uk Jisc is a registered charity (number 1149740) and a company limited by guarantee which is registered in England under Company No. 5747339, VAT No. GB 197 0632 86. Jisc’s registered office is: One Castlepark, Tower Hill, Bristol, BS2 0JA. T 0203 697 5800.

2 2

Re: Error while authenticating users on Wifi.
by Saurabh Lahoti 26 May '18

26 May '18

Dear Alan, As per your recommendation, have configured ldap module for wifi, users to be allowed through clients.conf & wifi virtual server. While testing a user over wifi, authentication fails due to LDAP search criteria missing into ldap server config. Error: rlm_ldap (ldapwifi): Waiting for bind result... rlm_ldap (ldapwifi): Bind successful (0) [ldapwifi] = ok (0) if ((ok || updated) && User-Password) { (0) if ((ok || updated) && User-Password) -> TRUE (0) if ((ok || updated) && User-Password) { (0) update { (0) control:Auth-Type := LDAP (0) } # update = noop (0) } # if ((ok || updated) && User-Password) = noop (0) } # elsif ( Airespace-Wlan-Id == 2 ) = ok (0) [expiration] = noop (0) [logintime] = noop (0) } # authorize = ok (0) Found Auth-Type = LDAP (0) # Executing group from file /usr/app/radius-new2/prod-corp-internal/etc/raddb/sites-enabled/wifi (0) Auth-Type LDAP { rlm_ldap (ldapwifi): Reserved connection (1) (0) ldapwifi: Login attempt by "u5496622" (0) ldapwifi: Using user DN from request "uid=u5496622,ou=Wifiusers,ou=Partners,o=mydomain.com" (0) ldapwifi: Waiting for bind result... (0) ldapwifi: Bind successful (0) ldapwifi: Bind as user "uid=u5496622, ou=Wifiusers,ou=Partners,o= mydomain.com" was successful rlm_ldap (ldapwifi): Released connection (1) (0) [ldapwifi] = ok (0) } # Auth-Type LDAP = ok (0) # Executing section post-auth from file /usr/app/radius-new2/prod-corp-internal/etc/raddb/sites-enabled/wifi (0) post-auth { (0) if ( Airespace-Wlan-Id == 2 ) { (0) if ( Airespace-Wlan-Id == 2 ) -> TRUE (0) if ( Airespace-Wlan-Id == 2 ) { (0) if ( "%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o=mydomain.com$/i ) { (0) EXPAND %{control:LDAP-UserDN} (0) --> uid=u5496622,ou=Wifiusers,ou=Partners,o=mydomain.com (0) if ( "%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o= mydomain.com$/i ) -> FALSE (0) elsif ( LDAP_Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com" ) { (0) elsif ( LDAP_Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com" ) -> FALSE (0) else { (0) [reject] = reject (0) } # else = reject (0) } # if ( Airespace-Wlan-Id == 2 ) = reject (0) } # post-auth = reject (0) Using Post-Auth-Type Reject (0) Post-Auth-Type sub-section not found. Ignoring. (0) # Executing group from file /usr/app/radius-new2/prod-corp-internal/etc/raddb/sites-enabled/wifi (0) Rejected in post-auth: [u5496622] (from client WLC1 port 13 cli 00-28-f8-10-56-35) (0) Login incorrect: [u5496622] (from client WLC1 port 13 cli 00-28-f8-10-56-35) (0) Delaying response for 1.000000 seconds Waking up in 0.3 seconds. Waking up in 0.6 seconds. (0) Sending delayed response (0) Sent Access-Reject Id 16 from 192.168.154.96:1812 to 172.18.40.40:32774 length 20 Waking up in 3.9 seconds. (0) Cleaning up request packet ID 16 with timestamp +27 For existing working access: # Executing section post-auth from file /usr/app/radius/prod-corp-internal//sites-enabled/wifi +group post-auth { ++? if (Airespace-Wlan-Id == 2 ) ? Evaluating (Airespace-Wlan-Id == 2 ) -> TRUE ++? if (Airespace-Wlan-Id == 2 ) -> TRUE ++if (Airespace-Wlan-Id == 2 ) { +++? if ("%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o=mydomain.com$/i ) expand: %{control:LDAP-UserDN} -> uid=u5496622,# Executing section post-auth from file /usr/app/radius/prod-corp-internal//sites-enabled/wifi +group post-auth { ++? if (Airespace-Wlan-Id == 2 ) ? Evaluating (Airespace-Wlan-Id == 2 ) -> TRUE ++? if (Airespace-Wlan-Id == 2 ) -> TRUE ++if (Airespace-Wlan-Id == 2 ) { +++? if ("%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o=mydomain.com$/i ) expand: %{control:LDAP-UserDN} -> uid=u5496622, ou=Wifiusers,ou=Partners,o=mydomain.com ? Evaluating ("%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o=mydomain.com$/i) -> FALSE +++? if ("%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o=mydomain.com$/i ) -> FALSE +++? elsif (LDAP-Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com" ) [ldapwifi2] Entering ldap_groupcmp() expand: o=mydomain.com -> o=mydomain.com expand: (&(objectClass=GroupOfUniqueNames)(uniquemember=%{control:Ldap-UserDn})) -> (&(objectClass=GroupOfUniqueNames)(uniquemember=uid\3du5496622\2cou\3dWifiusers\2cou\3dPartners\2co\ 3dmydomain.com)) [ldapwifi2] ldap_get_conn: Checking Id: 0 [ldapwifi2] ldap_get_conn: Got Id: 0 [ldapwifi2] performing search in cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com, with filter (&(objectClass=GroupOfUniqueNames)(uniquemember=uid\3du5496622\2cou\3dWifiusers\2cou\3dPartners\2co\ 3dmydomain.com)) rlm_ldap::ldap_groupcmp: User found in group cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com [ldapwifi2] ldap_release_conn: Release Id: 0 ? Evaluating (LDAP-Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o= mydomain.com " ) -> TRUE +++? elsif (LDAP-Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o= mydomain.com " ) -> TRUE +++elsif (LDAP-Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o= mydomain.com " ) { ++++[noop] = noop +++} # elsif (LDAP-Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o= mydomain.com " ) = noop +++ ... skipping else for request 1: Preceding "if" was taken ++} # if (Airespace-Wlan-Id == 2 ) = noop Existing version is 2.0.x & new version is 3.0.17. Could you please help us with correct method to search LDAP directory from radius...? ---- *Thanks & Kind Regards,* Saurabh LAHOTI.

2 2

(no subject)
by Saurabh Lahoti 26 May '18

26 May '18

Dear Alan, Below is the configuration for wifi virtual server: specific to post-auth section post-auth { if( Airespace-Wlan-Id == 2 ) { if( "%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o=mydomain.com$/i ) { noop } elsif( LDAP_Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com") { noop } else { reject } } LDAP module config: # -*- text -*- # # $Id$ # # Lightweight Directory Access Protocol (LDAP) # ldap ldapwifi { # Note that this needs to match the name(s) in the LDAP server # certificate, if you're using ldaps. See OpenLDAP documentation # for the behavioral semantics of specifying more than one host. # # Depending on the libldap in use, server may be an LDAP URI. # In the case of OpenLDAP this allows additional the following # additional schemes: # - ldaps:// (LDAP over SSL) # - ldapi:// (LDAP over Unix socket) # - ldapc:// (Connectionless LDAP) server = 'ldapcorp.ux.mydomain.com' # server = 'ldap.rrdns.example.org' # server = 'ldap.rrdns.example.org' # Port to connect on, defaults to 389, will be ignored for LDAP URIs. port = 389 # Administrator account for searching and possibly modifying. # If using SASL + KRB5 these should be commented out. identity = 'uid=wifiadmin,ou=production,ou=system,o=mydomain.com' password = xxxxxxx # Unless overridden in another section, the dn from which all # searches will start from. base_dn = 'o=mydomain.com' # # SASL parameters to use for admin binds # # When we're prompted by the SASL library, these control # the responses given, as well as the identity and password # directives above. # # If any directive is commented out, a NULL response will be # provided to cyrus-sasl. # # Unfortunately the only way to control Keberos here is through # environmental variables, as cyrus-sasl provides no API to # set the krb5 config directly. # # Full documentation for MIT krb5 can be found here: # # http://web.mit.edu/kerberos/krb5-devel/doc/admin/env_variables.html # # At a minimum you probably want to set KRB5_CLIENT_KTNAME. # # sasl { # SASL mechanism # mech = 'PLAIN' # SASL authorisation identity to proxy. # proxy = 'autz_id' # SASL realm. Used for kerberos. # realm = 'example.org' # } # # Generic valuepair attribute # # If set, this will attribute will be retrieved in addition to any # mapped attributes. # # Values should be in the format: # <radius attr> <op> <value> # # Where: # <radius attr>: Is the attribute you wish to create # with any valid list and request qualifiers. # <op>: Is any assignment operator (=, :=, +=, -=). # <value>: Is the value to parse into the new valuepair. # If the value is wrapped in double quotes it # will be xlat expanded. # valuepair_attribute = 'radiusAttribute' # # Mapping of LDAP directory attributes to RADIUS dictionary attributes. # # WARNING: Although this format is almost identical to the unlang # update section format, it does *NOT* mean that you can use other # unlang constructs in module configuration files. # # Configuration items are in the format: # <radius attr> <op> <ldap attr> # # Where: # <radius attr>: Is the destination RADIUS attribute # with any valid list and request qualifiers. # <op>: Is any assignment attribute (=, :=, +=, -=). # <ldap attr>: Is the attribute associated with user or # profile objects in the LDAP directory. # If the attribute name is wrapped in double # quotes it will be xlat expanded. # # Request and list qualifiers may also be placed after the 'update' # section name to set defaults destination requests/lists # for unqualified RADIUS attributes. # # Note: LDAP attribute names should be single quoted unless you want # the name value to be derived from an xlat expansion, or an # attribute ref. update { control:Password-With-Header += 'userPassword' # control:NT-Password := 'ntPassword' # reply:Reply-Message := 'radiusReplyMessage' # reply:Tunnel-Type := 'radiusTunnelType' # reply:Tunnel-Medium-Type := 'radiusTunnelMediumType' # reply:Tunnel-Private-Group-ID := 'radiusTunnelPrivategroupId' # Where only a list is specified as the RADIUS attribute, # the value of the LDAP attribute is parsed as a valuepair # in the same format as the 'valuepair_attribute' (above). control: += 'radiusControlAttribute' request: += 'radiusRequestAttribute' reply: += 'radiusReplyAttribute' } # Set to yes if you have eDirectory and want to use the universal # password mechanism. # edir = no # Set to yes if you want to bind as the user after retrieving the # Cleartext-Password. This will consume the login grace, and # verify user authorization. # edir_autz = no # Note: set_auth_type was removed in v3.x.x # Equivalent functionality can be achieved by adding the following # stanza to the authorize {} section of your virtual server. # # ldap # if ((ok || updated) && User-Password) { # update { # control:Auth-Type := ldap # } # } # # User object identification. # user { # Where to start searching in the tree for users base_dn = "${..base_dn}" # Filter for user objects, should be specific enough # to identify a single user object. # # For Active Directory, you should use # "samaccountname=" instead of "uid=" # filter = "(uid=%{%{Stripped-User-Name}:-%{User-Name}})" # SASL parameters to use for user binds # # When we're prompted by the SASL library, these control # the responses given. # # Any of the config items below may be an attribute ref # or and expansion, so different SASL mechs, proxy IDs # and realms may be used for different users. # sasl { # SASL mechanism # mech = 'PLAIN' # SASL authorisation identity to proxy. # proxy = &User-Name # SASL realm. Used for kerberos. # realm = 'example.org' # } # Search scope, may be 'base', 'one', sub' or 'children' scope = 'sub' # Server side result sorting # # A list of space delimited attributes to order the result # set by, if the filter matches multiple objects. # Only the first result in the set will be processed. # # If the attribute name is prefixed with a hyphen '-' the # sorting order will be reversed for that attribute. # # If sort_by is set, and the server does not support sorting # the search will fail. # sort_by = '-uid' # If this is undefined, anyone is authorised. # If it is defined, the contents of this attribute # determine whether or not the user is authorised # access_attribute = 'dialupAccess' # Control whether the presence of 'access_attribute' # allows access, or denys access. # # If 'yes', and the access_attribute is present, or # 'no' and the access_attribute is absent then access # will be allowed. # # If 'yes', and the access_attribute is absent, or # 'no' and the access_attribute is present, then # access will not be allowed. # # If the value of the access_attribute is 'false', it # will negate the result. # # e.g. # access_positive = yes # access_attribute = userAccessAllowed # # With an LDAP object containing: # userAccessAllowed: false # # Will result in the user being locked out. # access_positive = yes } # # User membership checking. # group { # Where to start searching in the tree for groups base_dn = "${..base_dn}" # Filter for group objects, should match all available # group objects a user might be a member of. filter = '(&(objectClass=GroupOfUniqueNames)(uniquemember=%{control:LDAP-UserDN}))' # Search scope, may be 'base', 'one', sub' or 'children' scope = 'sub' # Attribute that uniquely identifies a group. # Is used when converting group DNs to group # names. name_attribute = cn # Filter to find group objects a user is a member of. # That is, group objects with attributes that # identify members (the inverse of membership_attribute). membership_filter = "(|(&(objectClass=group)(member=%{control:Ldap-UserDn})))" # The attribute in user objects which contain the names # or DNs of groups a user is a member of. # # Unless a conversion between group name and group DN is # needed, there's no requirement for the group objects # referenced to actually exist. # membership_attribute = 'memberOf' # If cacheable_name or cacheable_dn are enabled, # all group information for the user will be # retrieved from the directory and written to LDAP-Group # attributes appropriate for the instance of rlm_ldap. # # For group comparisons these attributes will be checked # instead of querying the LDAP directory directly. # # This feature is intended to be used with rlm_cache. # # If you wish to use this feature, you should enable # the type that matches the format of your check items # i.e. if your groups are specified as DNs then enable # cacheable_dn else enable cacheable_name. # cacheable_name = 'no' # cacheable_dn = 'no' # Override the normal cache attribute (<inst>-LDAP-Group or # LDAP-Group if using the default instance) and create a # custom attribute. This can help if multiple module instances # are used in fail-over. # cache_attribute = 'LDAP-Cached-Membership' } # # User profiles. RADIUS profile objects contain sets of attributes # to insert into the request. These attributes are mapped using # the same mapping scheme applied to user objects (the update section above). # # profile { # Filter for RADIUS profile objects # filter = '(objectclass=radiusprofile)' # The default profile. This may be a DN or an attribute # reference. # To get old v2.2.x style behaviour, or to use the # &User-Profile attribute to specify the default profile, # set this to &control:User-Profile. # default = 'cn=radprofile,dc=example,dc=org' # The LDAP attribute containing profile DNs to apply # in addition to the default profile above. These are # retrieved from the user object, at the same time as the # attributes from the update section, are are applied # if authorization is successful. # attribute = 'radiusProfileDn' # } # # Bulk load clients from the directory # # client { # Where to start searching in the tree for clients # base_dn = "${..base_dn}" # # Filter to match client objects # # filter = '(objectClass=radiusClient)' # Search scope, may be 'base', 'one', 'sub' or 'children' # scope = 'sub' # # Sets default values (not obtained from LDAP) for new client entries # # template { # login = 'test' # 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 # } # } # # Client attribute mappings are in the format: # <client attribute> = <ldap attribute> # # The following attributes are required: # * ipaddr | ipv4addr | ipv6addr - Client IP Address. # * secret - RADIUS shared secret. # # All other attributes usually supported in a client # definition are also supported here. # # Schemas are available in doc/schemas/ldap for openldap and eDirectory # # attribute { # ipaddr = 'radiusClientIdentifier' # secret = 'radiusClientSecret' # shortname = 'radiusClientShortname' # nas_type = 'radiusClientType' # virtual_server = 'radiusClientVirtualServer' # require_message_authenticator = 'radiusClientRequireMa' # } # } # Load clients on startup # read_clients = no # # Modify user object on receiving Accounting-Request # # Useful for recording things like the last time the user logged # in, or the Acct-Session-ID for CoA/DM. # # LDAP modification items are in the format: # <ldap attr> <op> <value> # # Where: # <ldap attr>: The LDAP attribute to add modify or delete. # <op>: One of the assignment operators: # (:=, +=, -=, ++). # Note: '=' is *not* supported. # <value>: The value to add modify or delete. # # WARNING: If using the ':=' operator with a multi-valued LDAP # attribute, all instances of the attribute will be removed and # replaced with a single attribute. accounting { reference = "%{tolower:type.%{Acct-Status-Type}}" type { start { update { description := "Online at %S" } } interim-update { update { description := "Last seen at %S" } } stop { update { description := "Offline at %S" } } } } # # Post-Auth can modify LDAP objects too # post-auth { update { description := "Authenticated at %S" } } # # LDAP connection-specific options. # # These options set timeouts, keep-alives, etc. for the connections. # options { # Control under which situations aliases are followed. # May be one of 'never', 'searching', 'finding' or 'always' # default: libldap's default which is usually 'never'. # # LDAP_OPT_DEREF is set to this value. # dereference = 'always' # # The following two configuration items control whether the # server follows references returned by LDAP directory. # They are mostly for Active Directory compatibility. # If you set these to 'no', then searches will likely return # 'operations error', instead of a useful result. # chase_referrals = yes rebind = yes # SASL Security Properties (see SASL_SECPROPS in ldap.conf man page). # Note - uncomment when using GSS-API sasl mechanism along with TLS # encryption against Active-Directory LDAP servers (this disables # sealing and signing at the GSS level as required by AD). #sasl_secprops = 'noanonymous,noplain,maxssf=0' # Seconds to wait for LDAP query to finish. default: 20 res_timeout = 10 # Seconds LDAP server has to process the query (server-side # time limit). default: 20 # # LDAP_OPT_TIMELIMIT is set to this value. srv_timelimit = 3 # Seconds to wait for response of the server. (network # failures) default: 10 # # LDAP_OPT_NETWORK_TIMEOUT is set to this value. net_timeout = 1 # LDAP_OPT_X_KEEPALIVE_IDLE idle = 60 # LDAP_OPT_X_KEEPALIVE_PROBES probes = 3 # LDAP_OPT_X_KEEPALIVE_INTERVAL interval = 3 # ldap_debug: debug flag for LDAP SDK # (see OpenLDAP documentation). Set this to enable # huge amounts of LDAP debugging on the screen. # You should only use this if you are an LDAP expert. # # default: 0x0000 (no debugging messages) # Example:(LDAP_DEBUG_FILTER+LDAP_DEBUG_CONNS) ldap_debug = 0x0028 } # # This subsection configures the tls related items # that control how FreeRADIUS connects to an LDAP # server. It contains all of the 'tls_*' configuration # entries used in older versions of FreeRADIUS. Those # configuration entries can still be used, but we recommend # using these. # tls { # Set this to 'yes' to use TLS encrypted connections # to the LDAP database by using the StartTLS extended # operation. # # The StartTLS operation is supposed to be # used with normal ldap connections instead of # using ldaps (port 636) connections start_tls = no # ca_file = ${certdir}/cacert.pem # ca_path = ${certdir} # certificate_file = /path/to/radius.crt # private_key_file = /path/to/radius.key # random_file = /dev/urandom # Certificate Verification requirements. Can be: # 'never' (do not even bother trying) # 'allow' (try, but don't fail if the certificate # cannot be verified) # 'demand' (fail if the certificate does not verify) # 'hard' (similar to 'demand' but fails if TLS # cannot negotiate) # # The default is libldap's default, which varies based # on the contents of ldap.conf. # require_cert = 'demand' } # As of version 3.0, the 'pool' section has replaced the # following configuration items: # # ldap_connections_number # The connection pool is new for 3.0, and will be used in many # modules, for all kinds of connection-related activity. # # When the server is not threaded, the connection pool # limits are ignored, and only one connection is used. 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 # directory 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. } } ERROR received: (0) if ( Airespace-Wlan-Id == 2 ) { (0) if ( Airespace-Wlan-Id == 2 ) -> TRUE (0) if ( Airespace-Wlan-Id == 2 ) { (0) if ( "%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o= mydomain.com$/i ) { (0) EXPAND %{control:LDAP-UserDN} (0) --> uid=u5496622,ou=Techmahindra,ou=Partners,o= mydomain.com (0) if ( "%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o= mydomain.com $/i ) -> FALSE (0) elsif ( LDAP_Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com" ) { (0) elsif ( LDAP_Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=mydomain.com ) -> FALSE (0) else { (0) [reject] = reject (0) } # else = reject (0) } # if ( Airespace-Wlan-Id == 2 ) = reject (0) } # post-auth = reject (0) Using Post-Auth-Type Reject Probably, radius isn't able to glance into the LDAP group & search for uid. Perhaps, query syntax is wrong or incorrect. Could you please help with correct syntax..? ---- *Thanks & Kind Regards,* Saurabh LAHOTI.

2 1

Re: problem with table radacct column acctstarttime acctstoptime
by Alexandr 24 May '18

24 May '18

On 24.05.2018 11:59, Alexandr wrote: > I found function strftime, i think it writes time , but i found error > contain strftime > > (12) sql: ERROR: rlm_sql_mysql: ERROR 1305 (FUNCTION > radius_serv.strftime does not exist): 42000 > (12) sql: SQL query returned: server error > > How do fix it? > > some sql queries ( insert / update) > > INSERT: > > rlm_sql (sql): Reserved connection (0) > (11) sql: EXPAND %{User-Name} > (11) sql: --> systemn > (11) sql: SQL-User-Name set to 'systemn' > (11) sql: EXPAND INSERT INTO radacct (acctsessionid, acctuniqueid, > username, realm, nasipaddress, nasportid, nasporttype, acctstarttime, > acctupdatetime, acctstoptime, acctsessiontime, acctauthentic, > connectinfo_start, connectinfo_stop, acctinputoctets, > acctoutputoctets, calledstationid, callingstationid, > acctterminatecause, servicetype, framedprotocol, framedipaddress) > VALUES ('%{Acct-Session-Id}', '%{Acct-Unique-Session-Id}', > '%{SQL-User-Name}', '%{Realm}', '%{NAS-IP-Address}', > '%{%{NAS-Port-ID}:-%{NAS-Port}}', '%{NAS-Port-Type}', > %{%{integer:Event-Timestamp}:-date('now')}, > %{%{integer:Event-Timestamp}:-date('now')}, NULL, '0', > '%{Acct-Authentic}', '%{Connect-Info}', '', '0', '0', > '%{Called-Station-Id}', '%{Calling-Station-Id}', '', > '%{Service-Type}', '%{Framed-Protocol}', '%{Framed-IP-Address}') > > (11) sql: --> INSERT INTO radacct (acctsessionid, acctuniqueid, > username, realm, nasipaddress, nasportid, nasporttype, acctstarttime, > acctupdatetime, acctstoptime, acctsessiontime, acctauthentic, > connectinfo_start, connectinfo_stop, acctinputoctets, > acctoutputoctets, calledstationid, callingstationid, > acctterminatecause, servicetype, framedprotocol, framedipaddress) > VALUES ('8D3C0B6681A85E4F', '4884926a9a6b3dadbdd270f22e5fd4c4', > 'systemn', '', '192.168.10.26', '2', 'Wireless-802.11', 1527148106, > 1527148106, NULL, '0', 'RADIUS', 'CONNECT 54Mbps 802.11g', '', '0', > '0', '60-E3-27-72-BF-5A:DEvChata_new', '38-2D-D1-32-61-1E', '', > 'Framed-User', '', '') > > (11) sql: Executing query: INSERT INTO radacct (acctsessionid, > acctuniqueid, username, realm, nasipaddress, nasportid, nasporttype, > acctstarttime, acctupdatetime, acctstoptime, acctsessiontime, > acctauthentic, connectinfo_start, connectinfo_stop, acctinputoctets, > acctoutputoctets, calledstationid, callingstationid, > acctterminatecause, servicetype, framedprotocol, framedipaddress) > VALUES ('8D3C0B6681A85E4F', '4884926a9a6b3dadbdd270f22e5fd4c4', > 'systemn', '', '192.168.10.26', '2', 'Wireless-802.11', 1527148106, > 1527148106, NULL, '0', 'RADIUS', 'CONNECT 54Mbps 802.11g', '', '0', > '0', '60-E3-27-72-BF-5A:DEvChata_new', '38-2D-D1-32-61-1E', '', > 'Framed-User', '', '') > (11) sql: SQL query returned: success > (11) sql: 1 record(s) updated > > > UPDATE: > rlm_sql (sql): Reserved connection (1) > (13) sql: EXPAND %{User-Name} > (13) sql: --> systemn > (13) sql: SQL-User-Name set to 'systemn' > (13) sql: EXPAND UPDATE radacct SET acctstoptime = > %{%{integer:Event-Timestamp}:-date('now')}, acctsessiontime = > %{%{Acct-Session-Time}:-NULL}, acctinputoctets = > %{%{Acct-Input-Gigawords}:-0} << 32 | %{%{Acct-Input-Octets}:-0}, > acctoutputoctets = %{%{Acct-Output-Gigawords}:-0} << 32 | > %{%{Acct-Output-Octets}:-0}, acctterminatecause = > '%{Acct-Terminate-Cause}', connectinfo_stop = '%{Connect-Info}' WHERE > AcctUniqueId = '%{Acct-Unique-Session-Id}' > > (13) sql: --> UPDATE radacct SET acctstoptime = 1527150519, > acctsessiontime = 36, acctinputoctets = 0 << 32 | 282380, > acctoutputoctets = 0 << 32 | 1486385, acctterminatecause = > 'User-Request', connectinfo_stop = 'CONNECT 54Mbps 802.11g' WHERE > AcctUniqueId = '4ac1349d1e910f79fba700d0d1a1abba' > > (13) sql: Executing query: UPDATE radacct SET acctstoptime = > 1527150519, acctsessiontime = 36, acctinputoctets = 0 << 32 | > 282380, acctoutputoctets = 0 << 32 | 1486385, acctterminatecause = > 'User-Request', connectinfo_stop = 'CONNECT 54Mbps 802.11g' WHERE > AcctUniqueId = '4ac1349d1e910f79fba700d0d1a1abba' > > rlm_sql_mysql: Rows matched: 1 Changed: 1 Warnings: 1 > (13) sql: SQL query returned: success > (13) sql: 1 record(s) updated > > > > On 23.05.2018 13:51, Alan DeKok wrote: >> On May 23, 2018, at 4:00 AM, Alexandr<systemn17088(a)gmail.com> wrote: >>> freeradius -v3.0.18 >>> >>> Instead db mysql in table radacct shows incorrect time column acctstartime and acctstoptime in v.3 , if I will use v.2 or v.4 it will be ok. It's a bug ? >> Those times are created by the access point. FreeRADIUS just writes them to the database. >> >> Run the server in debugging mode to see what's going on. >> >> Alan DeKok. >> >> >> - >> List info/subscribe/unsubscribe? Seehttp://www.freeradius.org/list/users.html >

2 1

(no subject)
by Saurabh Lahoti 24 May '18

24 May '18

Dear Alan, Below is our ldap module config: ldap ldapwifi1 { server = "192.168.154.33" identity = "uid=wifitest,ou=production,ou=system,o=domain.com" password = xxxxxx basedn = "o=domain.com" filter = "(&(uid=%{Stripped-User-Name:-%{User-Name}})(!(nsaccountlock=true)))" base_filter = "(objectclass=*)" groupmembership_filter = "(&(objectClass=GroupOfUniqueNames)(uniquemember=%{control:Ldap-UserDn}))" ldap_connections_number = 5 timeout = 10 timelimit = 9 net_timeout = 10 tls { start_tls = no } dictionary_mapping = ${confdir}/ldap.attrmap Framed-Ip-Address = ipaddress edir_account_policy_check = no } ldap ldapwifi2 { server = "192.168.154.34" identity = "uid=wifitest,ou=production,ou=system,o=domain.com" password = xxxxxx basedn = "o=mobistar.be" filter = "(&(uid=%{Stripped-User-Name:-%{User-Name}})(!(nsaccountlock=true)))" base_filter = "(objectclass=*)" groupmembership_filter = "(&(objectClass=GroupOfUniqueNames)(uniquemember=%{control:Ldap-UserDn}))" ldap_connections_number = 5 timeout = 10 timelimit = 9 net_timeout = 10 tls { start_tls = no } dictionary_mapping = ${confdir}/ldap.attrmap Framed-Ip-Address = ipaddress edir_account_policy_check = no } Below is my ldap server config in sites-enabled: server wifi { authorize { preprocess suffix # if ( Called-Station-id =~ /:OBE_Byod$/ ) { # eap_byod # } if( Called-Station-Id =~ /:OBE_Office$/ ) { eap } elsif( Airespace-Wlan-Id == 2 ) { redundant-load-balance { ldapwifi1 ldapwifi2 } } expiration logintime } authenticate { Auth-Type LDAP { redundant-load-balance { ldapwifi1 ldapwifi2 } } # Auth-Type eap_byod { # eap_byod #} Auth-Type eap { eap } } preacct { preprocess update request { FreeRADIUS-Acct-Session-Start-Time = "%{expr: %l - %{%{Acct-Session-Time}:-0} - %{%{Acct-Delay-Time}:-0}}" } acct_unique suffix } accounting { wifi linelog-session } session { } post-auth { if( Airespace-Wlan-Id == 2 ) { if( "%{control:LDAP-UserDN}" =~ /ou=guest,ou=wifi,o=domain.com$/i ) { noop } elsif( LDAP_Group == "cn=WiFiGuestPartners,ou=RADIUS Groups,ou=Groups,ou=staff,o=domain.com" ) { noop } else { reject } } linelog-access # Post-Auth-Type REJECT { # linelog-access # attr_filter.access_reject # } } pre-proxy { } post-proxy { } } Could you please help where is the configuration wrong..? ---- *Thanks & Kind Regards,* Saurabh LAHOTI.

2 1

TLSMC: MozNSS compatibility interception begins message
by Chris Howley 23 May '18

23 May '18

Hello, We upgraded our test RADIUS server to use CentOS Linux release 7.5.1804 (Core) this morning and noticed the following messages in the /var/log/message file: May 23 09:04:05 XXXXXX systemd: Starting FreeRADIUS high performance RADIUS server.... May 23 09:04:05 XXXXXX radiusd: TLSMC: MozNSS compatibility interception begins. May 23 09:04:05 XXXXXX radiusd: tlsmc_convert: INFO: cannot open the NSS DB, expecting PEM configuration is present. May 23 09:04:05 XXXXXX radiusd: tlsmc_intercept_initialization: INFO: successfully intercepted TLS initialization. Continuing with OpenSSL only. May 23 09:04:05 XXXXXX radiusd: TLSMC: MozNSS compatibility interception ends. We're using FR 3.0.15. The current version of OpenSSL package is 1.0.2k-12. (previous version 1.0.2k-8). Please, could someone provide an explanation of these messages. Thanks, Chris Howley

3 3