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