October 2008 - Freeradius-Users - lists.freeradius.org

Re: Allocate IP address
by Rasool Jalali 18 Oct '08

18 Oct '08

hi it dose not work.Output : +++[control] returns noop PLZ help me ----- Original Message ---- From: "tnt(a)kalik.net" <tnt(a)kalik.net> To: FreeRadius users mailing list <freeradius-users(a)lists.freeradius.org> Sent: Saturday, October 18, 2008 3:36:17 PM Subject: Re: Allocate IP address update control { ... Ivan Kalik Kalik Informatika ISP Dana 18/10/2008, "Rasool Jalali" <r_jalali(a)ymail.com> piše: >hi all >i have a code like this in auth-post section : >if (condition) { > allocate from pool_1 >} >else { > allocate from pool_2 >} > >I write this code but it dose not work : > >if (condition) { > update reply { > Pool-Name : = pool_1 > } >} >else { > update reply { > Pool-Name : = pool_2 > } >} > >PLZ help me >tanx. > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Unlang/Perl
by rsg 18 Oct '08

18 Oct '08

Could Perl called (like any other pre-compiled module such as chap,sql...) within an unlang script? The requirement is to query an external http server during the Auth process. Thanks, rg.

2 4

Allocate IP address
by Rasool Jalali 18 Oct '08

18 Oct '08

hi all i have a code like this in auth-post section : if (condition) { allocate from pool_1 } else { allocate from pool_2 } I write this code but it dose not work : if (condition) { update reply { Pool-Name : = pool_1 } } else { update reply { Pool-Name : = pool_2 } } PLZ help me tanx. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

Error in the negotiations certificates
by Martin Silvero 17 Oct '08

17 Oct '08

and that I did when I run radiusd-X I get an error in the inicializacion modules: eap.conf: eap { # Invoke the default supported EAP type when # EAP-Identity response is received. # # The incoming EAP messages DO NOT specify which EAP # type they will be using, so it MUST be set here. # # For now, only one default EAP type may be used at a time. # # If the EAP-Type attribute is set by another module, # then that EAP type takes precedence over the # default type configured here. # #default_eap_type = md5 # A list is maintained to correlate EAP-Response # packets with EAP-Request packets. After a # configurable length of time, entries in the list # expire, and are deleted. # #timer_expire = 60 # There are many EAP types, but the server has support # for only a limited subset. If the server receives # a request for an EAP type it does not support, then # it normally rejects the request. By setting this # configuration to "yes", you can tell the server to # instead keep processing the request. Another module # MUST then be configured to proxy the request to # another RADIUS server which supports that EAP type. # # If another module is NOT configured to handle the # request, then the request will still end up being # rejected. #ignore_unknown_eap_types = no # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given # a User-Name attribute in an Access-Accept, it copies one # more byte than it should. # # We can work around it by configurably adding an extra # zero byte. cisco_accounting_username_bug = no # Supported EAP-types # # We do NOT recommend using EAP-MD5 authentication # for wireless connections. It is insecure, and does # not provide for dynamic WEP keys. # #md5 { #} # Cisco LEAP # # We do not recommend using LEAP in new deployments. See: # http://www.securiteam.com/tools/5TP012ACKE.html # # Cisco LEAP uses the MS-CHAP algorithm (but not # the MS-CHAP attributes) to perform it's authentication. # # As a result, LEAP *requires* access to the plain-text # User-Password, or the NT-Password attributes. # 'System' authentication is impossible with LEAP. # leap { } # Generic Token Card. # # Currently, this is only permitted inside of EAP-TTLS, # or EAP-PEAP. The module "challenges" the user with # text, and the response from the user is taken to be # the User-Password. # # Proxying the tunneled EAP-GTC session is a bad idea, # the users password will go over the wire in plain-text, # for anyone to see. # gtc { # The default challenge, which many clients # ignore.. #challenge = "Password: " # The plain-text response which comes back # is put into a User-Password attribute, # and passed to another module for # authentication. This allows the EAP-GTC # response to be checked against plain-text, # or crypt'd passwords. # # If you say "Local" instead of "PAP", then # the module will look for a User-Password # configured for the request, and do the # authentication itself. # auth_type = PAP } ## EAP-TLS # # See raddb/certs/README for additional comments # on certificates. # # If OpenSSL was not found at the time the server was # built, the "tls", "ttls", and "peap" sections will # be ignored. # # Otherwise, when the server first starts in debugging # mode, test certificates will be created. See the # "make_cert_command" below for details, and the README # file in raddb/certs # # These test certificates SHOULD NOT be used in a normal # deployment. They are created only to make it easier # to install the server, and to perform some simple # tests with EAP-TLS, TTLS, or PEAP. # # See also: # # http://www.dslreports.com/forum/remark,9286052~mode=flat # tls { # # These is used to simplify later configurations. # certdir = ${confdir}/certs cadir = ${confdir}/certs private_key_password = testing123 private_key_file = ${certdir}/server.pem # If Private key & Certificate are located in # the same file, then private_key_file & # certificate_file must contain the same file # name. # # If CA_file (below) is not used, then the # certificate_file below MUST include not # only the server certificate, but ALSO all # of the CA certificates used to sign the # server certificate. certificate_file = ${certdir}/server.pem # Trusted Root CA list # # ALL of the CA's in this list will be trusted # to issue client certificates for authentication. # # In general, you should use self-signed # certificates for 802.1x (EAP) authentication. # In that case, this CA file should contain # *one* CA certificate. # # This parameter is used only for EAP-TLS, # when you issue client certificates. If you do # not use client certificates, and you do not want # to permit EAP-TLS authentication, then delete # this configuration item. CA_file = ${cadir}/ca.pem # # For DH cipher suites to work, you have to # run OpenSSL to create the DH file first: # # openssl dhparam -out certs/dh 1024 # dh_file = ${certdir}/dh random_file = ${certdir}/random # # This can never exceed the size of a RADIUS # packet (4096 bytes), and is preferably half # that, to accomodate other attributes in # RADIUS packet. On most APs the MAX packet # length is configured between 1500 - 1600 # In these cases, fragment size should be # 1024 or less. # fragment_size = 1024 # include_length is a flag which is # by default set to yes If set to # yes, Total Length of the message is # included in EVERY packet we send. # If set to no, Total Length of the # message is included ONLY in the # First packet of a fragment series. # include_length = yes # Check the Certificate Revocation List # # 1) Copy CA certificates and CRLs to same directory. # 2) Execute 'c_rehash <CA certs&CRLs Directory>'. # 'c_rehash' is OpenSSL's command. # 3) uncomment the line below. # 5) Restart radiusd # check_crl = yes # CA_path = /path/to/directory/with/ca_certs/and/crls/ # # If check_cert_issuer is set, the value will # be checked against the DN of the issuer in # the client certificate. If the values do not # match, the cerficate verification will fail, # rejecting the user. # # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd" # # If check_cert_cn is set, the value will # be xlat'ed and checked against the CN # in the client certificate. If the values # do not match, the certificate verification # will fail rejecting the user. # # This check is done only if the previous # "check_cert_issuer" is not set, or if # the check succeeds. # # check_cert_cn = %{User-Name} # # Set this option to specify the allowed # TLS cipher suites. The format is listed # in "man 1 ciphers". cipher_list = "DEFAULT" # # This configuration entry should be deleted # once the server is running in a normal # configuration. It is here ONLY to make # initial deployments easier. # # make_cert_command = "${certdir}/bootstrap" } # The TTLS module implements the EAP-TTLS protocol, # which can be described as EAP inside of Diameter, # inside of TLS, inside of EAP, inside of RADIUS... # # Surprisingly, it works quite well. # # The TTLS module needs the TLS module to be installed # and configured, in order to use the TLS tunnel # inside of the EAP packet. You will still need to # configure the TLS module, even if you do not want # to deploy EAP-TLS in your network. Users will not # be able to request EAP-TLS, as it requires them to # have a client certificate. EAP-TTLS does not # require a client certificate. # # You can make TTLS require a client cert by setting # # EAP-TLS-Require-Client-Cert = Yes # # in the control items for a request. # #ttls { # The tunneled EAP session needs a default # EAP type which is separate from the one for # the non-tunneled EAP module. Inside of the # TTLS tunnel, we recommend using EAP-MD5. # If the request does not contain an EAP # conversation, then this configuration entry # is ignored. # default_eap_type = md5 # The tunneled authentication request does # not usually contain useful attributes # like 'Calling-Station-Id', etc. These # attributes are outside of the tunnel, # and normally unavailable to the tunneled # authentication request. # # By setting this configuration entry to # 'yes', any attribute which NOT in the # tunneled authentication request, but # which IS available outside of the tunnel, # is copied to the tunneled request. # # allowed values: {no, yes} # copy_request_to_tunnel = no # The reply attributes sent to the NAS are # usually based on the name of the user # 'outside' of the tunnel (usually # 'anonymous'). If you want to send the # reply attributes based on the user name # inside of the tunnel, then set this # configuration entry to 'yes', and the reply # to the NAS will be taken from the reply to # the tunneled request. # # allowed values: {no, yes} # use_tunneled_reply = no # # The inner tunneled request can be sent # through a virtual server constructed # specifically for this purpose. # # If this entry is commented out, the inner # tunneled request will be sent through # the virtual server that processed the # outer requests. # # virtual_server = "inner-tunnel" #} ################################################## # # !!!!! WARNINGS for Windows compatibility !!!!! # ################################################## # # If you see the server send an Access-Challenge, # and the client never sends another Access-Request, # then # # STOP! # # The server certificate has to have special OID's # in it, or else the Microsoft clients will silently # fail. See the "scripts/xpextensions" file for # details, and the following page: # # http://support.microsoft.com/kb/814394/en-us # # For additional Windows XP SP2 issues, see: # # http://support.microsoft.com/kb/885453/en-us # # Note that we do not necessarily agree with their # explanation... but the fix does appear to work. # ################################################## # # The tunneled EAP session needs a default EAP type # which is separate from the one for the non-tunneled # EAP module. Inside of the TLS/PEAP tunnel, we # recommend using EAP-MS-CHAPv2. # # The PEAP module needs the TLS module to be installed # and configured, in order to use the TLS tunnel # inside of the EAP packet. You will still need to # configure the TLS module, even if you do not want # to deploy EAP-TLS in your network. Users will not # be able to request EAP-TLS, as it requires them to # have a client certificate. EAP-PEAP does not # require a client certificate. # # # You can make TTLS require a client cert by setting # # EAP-TLS-Require-Client-Cert = Yes # # in the control items for a request. # peap { # The tunneled EAP session needs a default # EAP type which is separate from the one for # the non-tunneled EAP module. Inside of the # PEAP tunnel, we recommend using MS-CHAPv2, # as that is the default type supported by # Windows clients. default_eap_type = mschapv2 # the PEAP module also has these configuration # items, which are the same as for TTLS. copy_request_to_tunnel = no use_tunneled_reply = no # When the tunneled session is proxied, the # home server may not understand EAP-MSCHAP-V2. # Set this entry to "no" to proxy the tunneled # EAP-MSCHAP-V2 as normal MSCHAPv2. # proxy_tunneled_request_as_eap = yes # # The inner tunneled request can be sent # through a virtual server constructed # specifically for this purpose. # # If this entry is commented out, the inner # tunneled request will be sent through # the virtual server that processed the # outer requests. # virtual_server = "inner-tunnel" } # # This takes no configuration. # # Note that it is the EAP MS-CHAPv2 sub-module, not # the main 'mschap' module. # # Note also that in order for this sub-module to work, # the main 'mschap' module MUST ALSO be configured. # # This module is the *Microsoft* implementation of MS-CHAPv2 # in EAP. There is another (incompatible) implementation # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not # currently support. # mschapv2 { } }

3 2

Error in the negotiations certificates
by Martin Silvero 17 Oct '08

17 Oct '08

In that case, disable the module md5 because I just want to use tls? Why does the error that I showed you? certificates? thanks!

2 1

Error in the negotiations certificates
by Martin Silvero 17 Oct '08

17 Oct '08

Good day mate. Well, finally understood what I recomendastes and I did, I created a package with server.pem ca.pem and then convert it to. der, the amount to the notebook but this time gave an error with the validation of the server: rad_recv: Access-Request packet from host 10.0.31.40 port 1645, id=13, length=136 User-Name = "cert" Framed-MTU = 1400 Called-Station-Id = "0019.2fdb.9e00" Calling-Station-Id = "001f.3c22.44c5" Service-Type = Login-User Message-Authenticator = 0x4c4673bed5a0d93399f5b623d8046b1d EAP-Message = 0x020100090163657274 NAS-Port-Type = Wireless-802.11 NAS-Port = 1301 NAS-IP-Address = 10.0.31.40 NAS-Identifier = "ap-Reconquista-31" Fri Oct 17 10:47:33 2008 : Debug: +- entering group authorize Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling preprocess (rlm_preprocess) for request 0 Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from preprocess (rlm_preprocess) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[preprocess] returns ok Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling chap (rlm_chap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from chap (rlm_chap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[chap] returns noop Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling mschap (rlm_mschap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from mschap (rlm_mschap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[mschap] returns noop Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling suffix (rlm_realm) for request 0 Fri Oct 17 10:47:33 2008 : Debug: rlm_realm: No '@' in User-Name = "cert", looking up realm NULL Fri Oct 17 10:47:33 2008 : Debug: rlm_realm: No such realm "NULL" Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from suffix (rlm_realm) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[suffix] returns noop Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling eap (rlm_eap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: rlm_eap: EAP packet type response id 1 length 9 Fri Oct 17 10:47:33 2008 : Debug: rlm_eap: No EAP Start, assuming it's an on-going EAP conversation Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from eap (rlm_eap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[eap] returns updated Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling unix (rlm_unix) for request 0 Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from unix (rlm_unix) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[unix] returns notfound Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling files (rlm_files) for request 0 Fri Oct 17 10:47:33 2008 : Debug: users: Matched entry cert at line 76 Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from files (rlm_files) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[files] returns ok Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling expiration (rlm_expiration) for request 0 Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from expiration (rlm_expiration) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[expiration] returns noop Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling logintime (rlm_logintime) for request 0 Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from logintime (rlm_logintime) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[logintime] returns noop Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: calling pap (rlm_pap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: rlm_pap: Found existing Auth-Type, not changing it. Fri Oct 17 10:47:33 2008 : Debug: modsingle[authorize]: returned from pap (rlm_pap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[pap] returns noop Fri Oct 17 10:47:33 2008 : Debug: rad_check_password: Found Auth-Type EAP Fri Oct 17 10:47:33 2008 : Debug: auth: type "EAP" Fri Oct 17 10:47:33 2008 : Debug: +- entering group authenticate Fri Oct 17 10:47:33 2008 : Debug: modsingle[authenticate]: calling eap (rlm_eap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: rlm_eap: EAP Identity Fri Oct 17 10:47:33 2008 : Debug: rlm_eap: processing type md5 Fri Oct 17 10:47:33 2008 : Debug: rlm_eap_md5: Issuing Challenge Fri Oct 17 10:47:33 2008 : Debug: modsingle[authenticate]: returned from eap (rlm_eap) for request 0 Fri Oct 17 10:47:33 2008 : Debug: ++[eap] returns handled Sending Access-Challenge of id 13 to 10.0.31.40 port 1645 EAP-Message = 0x0102001604105b73da6c29c23d1018905b343c4fb5c9 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x267005d0267201665ceab013c67b6d34 Fri Oct 17 10:47:33 2008 : Debug: Finished request 0. Fri Oct 17 10:47:33 2008 : Debug: Going to the next request Fri Oct 17 10:47:33 2008 : Debug: Waking up in 4.9 seconds. a question: this certificate I'm going to install on multiple computers, can I generate problems that?

2 1

[awful patch] "Multiple levels of TLS nesting is invalid."
by Matt Bernstein 17 Oct '08

17 Oct '08

So saith FreeRADIUS 2.1.1, but I wasn't trying to do multiple levels of TLS nesting. I'm trying to use virtual servers so that a single radiusd can terminate TTLS/PEAP for multiple subrealms, _and_ use the inner-tunnel trick, keeping the configs completely independent for each subrealm. This allows me to hook up different departments with different AAA infrastructures into one radius set-up for our eduroam service. My "default" server has a pair of listen{} blocks, and little else: authorize { suffix } authenticate { } So, rlm_realm finds my virtual servers in proxy.conf, eg: realm dcs.qmul.ac.uk { nostrip virtual_server = dcs } ..and "dcs" has its own EAP config, which references a virtual_server "dcs-inner" for the PEAP/TTLS innards, which has _its_ own EAP config. My problem is that eap.c (line 219), as called by "dcs-inner", notices the request has a grandparent, and assumes it's multiple layers of TLS nesting. Interestingly, the comment omits the magic word "TLS". I think perhaps that the virtual servers appear to count as layers. Anyway, this braindead patch makes it work for me: --- freeradius-server-2.1.1/src/modules/rlm_eap/eap.c.orig 2008-09-25 09:41:26.000000000 +0100 +++ freeradius-server-2.1.1/src/modules/rlm_eap/eap.c 2008-10-14 15:19:53.800553926 +0100 @@ -216,10 +216,13 @@ /* * Multiple levels of nesting are invalid. */ - if (handler->request->parent && handler->request->parent->parent) { - RDEBUG2("Multiple levels of TLS nesting is invalid."); + if (handler->request->parent && handler->request->parent->parent && handler->request->parent->parent->parent ) { + RDEBUG2("Multiple levels of TLS nesting is really invalid."); return EAP_INVALID; } + if (handler->request->parent && handler->request->parent->parent) { + RDEBUG2("Multiple levels of nesting is thought invalid, continuing anyway."); + } /* * Figure out what to do. ..and my "radiusd -X" output now looks like this: Found Auth-Type = dcs-inner-eap +- entering group authenticate {...} [dcs-inner-eap] Request found, released from the list [dcs-inner-eap] Multiple levels of nesting is thought invalid, continuing anyway. [dcs-inner-eap] EAP/mschapv2 [dcs-inner-eap] processing type mschapv2 [mschapv2] +- entering group MS-CHAP {...} [mschap] No Cleartext-Password configured. Cannot create LM-Password. [mschap] Found NT-Password [mschap] Told to do MS-CHAPv2 for username(a)dcs.qmul.ac.uk with NT-Password [mschap] adding MS-CHAPv2 MPPE keys ++[mschap] returns ok MSCHAP Success ++[dcs-inner-eap] returns handled So.. I hope this is useful. Do drop me a mail on- or off-list on <mb/freeradius(a)dcs.qmul.ac.uk>, if you want any further information or if I'm not being clear enough. Matt

3 7

Mschapv2 not working! Please help!
by saini_jas16 17 Oct '08

17 Oct '08

Hello All, I am trying to authenticate a Windows XP Client with the username and password configured in the Users file on the Radius Server. I have tried saveral changes, but I am not able to get rid of this error. I am running freeradius 2.1.1 on Suse 10 SP1. Kindly Help, I am in urgent need of making this radius server up and running. Below is the error I am receiving. rad_recv: Access-Request packet from host 130.1.254.174 port 20000, id=212, length=182 NAS-Port-Id = "2049/1" Calling-Station-Id = "00-1F-3B-70-5B-7F" Called-Station-Id = "00-18-6E-30-70-C0:NYCC_TEST" Service-Type = Framed-User User-Name = "jaswinder" State = 0x2aaca71b29aabed260fc846046180105 EAP-Message = 0x02060021198000000017150301001294659677442f8e7a361ee8ee93374c90ed53 NAS-Port-Type = Wireless-802.11 NAS-Identifier = "3Com" NAS-IP-Address = 130.1.254.174 Message-Authenticator = 0xe42d1530c16b34c5b74bfb4c486083aa +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "jaswinder", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 6 length 33 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS TLS Length 23 [peap] Length Included [peap] eaptls_verify returned 11 [peap] <<< TLS 1.0 Alert [length 0002], fatal access_denied TLS Alert read:fatal:access denied [peap] WARNING: No data inside of the tunnel. [peap] eaptls_process returned 7 [peap] EAPTLS_OK [peap] Session established. Decoding tunneled attributes. [peap] Tunneled data is invalid. [eap] Handler failed in EAP/peap [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> jaswinder attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 5 for 1 seconds Going to the next request Any help is greatly appreciated. Thanks, Jas -- View this message in context: http://www.nabble.com/Mschapv2-not-working%21-Please-help%21-tp20015619p200… Sent from the FreeRadius - User mailing list archive at Nabble.com.

5 14

Changes made
by Martin MacLeod-Brown 17 Oct '08

17 Oct '08

Ok, after a bit of googling and some feedback from the mailing list - here is my new sanity check In radius.conf ldap { server = "ldap-master.london.edu" identity = "cn=NetworkAuth,ou=People,o=london.edu,o=lbs" password = ********* basedn = "ou=People,o=london.edu,o=lbs" filter = "(uid=%u)" start_tls = no access_attr = "uid" dictionary_mapping = ${raddbdir}/ldap.attrmap base_filter = "(objectclass=people)" quote >DEFAULT Auth-Type = LDAP > Fall-Through :=1 > Don't do that. You can configure ldap module to set auth type itself. Ok fair enough, I have changed it back to DEFAULT Auth-Type = System Fall-Through = 1 Im confused - where can I set ldap module to set auth type itself.???? Find radiusd belonging to freeradius and run it. It would appear to be running... root@morpheus:/etc/freeradius# ps -ef |grep radiusd root 24106 11597 0 14:36 pts/1 00:00:00 grep radiusd Martin Macleod-Brown | Infrastructure Engineer - Networks & Security Infrastructure Team London Business School | Regent's Park | London NW1 4SA | United Kingdom Switchboard +44 (0)20 7000 7000 | Direct line +44 (0)20 7000 7772 | Mobile +44 (0)796 690 7772 | Email mmacleod(a)london.edu <mailto:mmacleod@london.edu> www.london.edu <http://www.london.edu> | London experience. World impact. Please consider the environment before printing this email ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System on behalf of the London Business School community. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

2 1

What Have I missed out?
by Martin MacLeod-Brown 17 Oct '08

17 Oct '08

Hi there, Im trying to get a basic radius set-up working and could do with a sanity check as it is not working? Steps taken so far 1) Default radius install on Unbuntu server (apt-get install freeradius freeradius-ldap) 2) In radiusd.conf - configure LDAP server properties in the modules section ldap { server = "ldap-master.london.edu" identity = "cn=NetworkAuth,ou=People,o=london.edu,o=lbs" password = ********* basedn = "ou=People,o=london.edu,o=lbs" filter = "(uid=%{Stripped-User-Name:-%{User-Name}})" base_filter = "(objectclass=radiusprofile)" Uncommented the following line: # ldap File: /etc/freeradius/radiusd.conf - Authentication Section. Uncommented the following three lines: # Auth-Type LDAP { # ldap # } File: /etc/freeradius/users Find: DEFAULT Auth-Type = System Fall-Through = 1 Replace with: DEFAULT Auth-Type = LDAP Fall-Through :=1 File: /etc/freeradius/clients.conf client 127.0.0.1 { secret = testing123 shortname = localhost nastype = other } Now when I try to test I get the following error radclient: no response from server for ID 80 Looking in the radius.log - I get no output at all from a tail -f command Putting the server into debug mode I get root@morpheus:/etc/freeradius# radiusd -X The program 'radiusd' can be found in the following packages: * radiusd-livingston * yardradius * xtradius Try: apt-get install <selected package> bash: radiusd: command not found This is now making me thing I have not installed it properly? Any pointers gratefully received :-) Thanks Martin Martin Macleod-Brown | Infrastructure Engineer - Networks & Security Infrastructure Team London Business School | Regent's Park | London NW1 4SA | United Kingdom Switchboard +44 (0)20 7000 7000 | Direct line +44 (0)20 7000 7772 | Mobile +44 (0)796 690 7772 | Email mmacleod(a)london.edu www.london.edu | London experience. World impact. Please consider the environment before printing this email ______________________________________________________________________ This email has been scanned by the MessageLabs Email Security System on behalf of the London Business School community. For more information please visit http://www.messagelabs.com/email ______________________________________________________________________

3 2