February 2011 - Freeradius-Users - lists.freeradius.org

unsubscribe
by Josh Richard 26 Feb '11

26 Feb '11

2 1

..::Cisco Nac::..
by Alfonso Alejandro Reyes Jiménez 26 Feb '11

26 Feb '11

Hi everyone, I need to configure a freeradius server to grant access to our Network based in the Cisco Nac solution. I just want to know if anyone has configured Cisco Nac on their network and any advice when doing it. Right know we are just gathering all the information related (Vendor specific attributes), and the other question is how can we prevent the system users to authenticate on the radius?. Thanks in advance. regards. Alfonso.

2 2

Auth-Type Perl instead of Auth-Type EAP?
by Josh Richard 26 Feb '11

26 Feb '11

Hello list, After a bit of digging, I would like to ask a question to ensure this idea is even possible. :) I am running FR 2 on Debian. What I would like to do is have a WPA2 PEAP/MS_ChapV2 Cisco wireless SSID hook into the FR server above. The FR server currently is using rlm_perl to handle authentication and this does work with FR running with -x and a client test using radtest: Sending Access-Request of id 184 to <ip> port 1812 User-Name = "jrichar4" User-Password = "removed" NAS-IP-Address = 127.0.1.1 NAS-Port = 10 rad_recv: Access-Accept packet from host <ip> port 1812, id=184, length=20 on the server I see: rlm_perl: Added pair User-Name = jrichar4 rlm_perl: Added pair User-Password = <removed> rlm_perl: Added pair NAS-IP-Address = 127.0.1.1 rlm_perl: Added pair NAS-Port = 10 rlm_perl: Added pair Crypt-Password = <removed> rlm_perl: Added pair Auth-Type = Perl I wrote some Perl in the rlm_perl code that uses Perl's Authen::Radius to proxy the lookup to a different production FR server containing the set of all users. Neat. I hope to use this server to flip VLANs using $RAD_REPLY{'Tunnel-Private-Group-ID'} based on an eventual db lookup to control wireless machine infections without mutzing with an existing server. When the SSID is wired in, we see this: [peap] Got inner identity 'jrichar4' # Executing section authorize from file /etc/freeradius/sites-enabled/inner-tunnel rlm_perl: Added pair User-Name = jrichar4 rlm_perl: Added pair EAP-Message = 0x0206000c016d736865746b61 rlm_perl: Added pair EAP-Type = Identity rlm_perl: Added pair FreeRADIUS-Proxied-To = 127.0.0.1 rlm_perl: Added pair Crypt-Password = * rlm_perl: Added pair Auth-Type = EAP rlm_perl: Added pair Proxy-To-Realm = LOCAL rlm_perl: Added pair EAP-Type = MS-CHAP-V2 I would prefer the use Auth-Type = Perl in the EAP inner tunnel. Is this possible? I am hoping something simple is amiss as this is close to working! I have only: DEFAULT Auth-Type = Perl in users. In inner tunnel I have: authenticate { .... Auth-Type Perl { perl } ... eap } Do I need to overload anything in eap.conf? Thank you all and kind regards, Josh Richard University of Minnesota Duluth USA

2 2

Re: pam_radius_auth query
by vijay s sheelavantar 26 Feb '11

26 Feb '11

Hi ,Marc and Alan Thanx for the reply . What I exactly mean by authorization is Management-Privilege-Level which is defined in RFC 5607, I want to give restricted access to certain resources on my NE to the user accounts. basically I want to authorize user accounts based on groups and privileges. If a user belongs to certain group and have the previlege level (security admin or administrator) then only he can execute certain commands on the NE.right now PAM module is doing this in my NE. I want it to be done by Radius server. Now pam_radius_auth module sends "authentication only" in request message so, the server is not doing authorization it seems. How can I ask Server to do authorization and when server sends the authorization attributes AVPs in the access-Accept message how to process those values? or PAM module will take care of this thing.? I am really not getting how to support this "management-privilege-level" feature using pam-radius-auth. On Fri, 25 Feb 2011 20:11:32 , freeradius-users-request(a)lists.freeradius.org wrote Send Freeradius-Users mailing list submissions to    freeradius-users(a)lists.freeradius.org To subscribe or unsubscribe via the World Wide Web, visit    http://lists.freeradius.org/mailman/listinfo/freeradius-users or, via email, send a message with subject or body 'help' to    freeradius-users-request(a)lists.freeradius.org You can reach the person managing the list at    freeradius-users-owner(a)lists.freeradius.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Freeradius-Users digest..." Today's Topics:   1. Re: store and proxy accounting packets (Waqas Toor)   2. Re: store and proxy accounting packets (Alan DeKok)   3. Re: pam_radius_auth query (Marc Phillips)   4. Re: store and proxy accounting packets (Waqas Toor)   5. Re: store and proxy accounting packets (Alan DeKok)   6. Re: store and proxy accounting packets (Waqas Toor)   7. Re: store and proxy accounting packets (Alan DeKok) ---------------------------------------------------------------------- Message: 1 Date: Fri, 25 Feb 2011 16:01:06 +0500 From: Waqas Toor <waqasnasirtoor(a)gmail.com> Subject: Re: store and proxy accounting packets To: FreeRadius users mailing list    <freeradius-users(a)lists.freeradius.org> Cc: Alan DeKok <aland(a)deployingradius.com> Message-ID:    <AANLkTinpZ94e6NpNMJo+fLgSbkreryZvio6=FBPcUpbg(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Hi, On Thu, Feb 24, 2011 at 11:33 AM, Alan DeKok <aland(a)deployingradius.com> wrote: > Waqas Toor wrote: >> but what to do to get accounting to other client, Also if that fails >> is it going to create detail files ? > > ?Did you bother *reading* the "robust-proxy-accounting" file? > I have configured the robust-proxy-accounting below is the file ==================================== home_server home1.example.com {    type = acct    ipaddr = 10.1.67.41    port = 1813    secret = freerad    status_check = request    username = "test_user_status_check"    response_window = 6 } home_server home2.example.com {    type = acct    ipaddr = 10.1.67.42    port = 1813    secret = freerad    response_window = 6 } home_server acct_detail.example.com {    virtual_server = acct_detail.example.com } home_server_pool acct_pool.example.com {    home_server = home1.example.com    home_server = home2.example.com    fallback = acct_detail.example.com    virtual_server = home.example.com } realm acct_realm.example.com {    acct_pool = acct_pool.example.com } server acct_detail.example.com {    accounting {       detail.example.com    } } server home.example.com {    pre-proxy {       #  Insert pre-proxy rules here    }    post-proxy {       Post-Proxy-Type Fail {          detail.example.com       }    }    listen {       type = detail       filename = "${radacctdir}/detail.example.com/detail-*:*"       load_factor = 10    }    accounting {       # You may want accounting policies here...       update control {          Proxy-To-Realm := "acct_realm.example.com"       }    } } ==================================== but it is not working neither its creating any file here is the debug last lines =================================== } # server radiusd: #### Opening IP addresses and Ports #### listen {        type = "auth"        ipaddr = *        port = 0 } listen {        type = "acct"        ipaddr = *        port = 0 } listen {        type = "control" listen {        socket = "/usr/local/var/run/radiusd/radiusd.sock"        mode = "rw" } } listen {        type = "detail"  listen {        filename = "/usr/local/var/log/radius/radacct/detail.example.com/detail-*:*"        load_factor = 10        poll_interval = 1        retry_interval = 30  } } listen {        type = "auth"        ipaddr = 127.0.0.1        port = 18120 } Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Listening on detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* as server home.example.com Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.000000 sec Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel Listening on proxy address * port 1814 Waking up in 0.9 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.134651 sec Waking up in 1.1 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.011006 sec Waking up in 1.0 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.113558 sec Waking up in 1.1 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 0.903584 sec Waking up in 0.9 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.185763 sec Waking up in 1.1 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 0.916197 sec Waking up in 0.9 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 0.925224 sec Waking up in 0.9 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.160946 sec Waking up in 1.1 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 0.817426 sec Waking up in 0.8 seconds. ================== I am missing something but could not figure it out what regards. Waqas ------------------------------ Message: 2 Date: Fri, 25 Feb 2011 14:02:33 +0100 From: Alan DeKok <aland(a)deployingradius.com> Subject: Re: store and proxy accounting packets To: FreeRadius users mailing list    <freeradius-users(a)lists.freeradius.org> Message-ID: <4D67A869.7050209(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Waqas Toor wrote: >>  Did you bother *reading* the "robust-proxy-accounting" file? >> > I have configured the robust-proxy-accounting  That doesn't answer the question.  The comments in that file describe how it works.  This includes answering your original question. > I am missing something but could not figure it out what  The debug log doesn't show it receiving packets.  What do you *expect* to happen when it doesn't received packets?  The answer should be obvious: it's documented in the comments in the "robust-proxy-accounting" file.  Go read it.  Alan DeKok. ------------------------------ Message: 3 Date: Fri, 25 Feb 2011 07:09:14 -0600 From: Marc Phillips <rmarc(a)copacetic.net> Subject: Re: pam_radius_auth query To: vijay s sheelavantar <s_vijay65(a)rediffmail.com> Cc: freeradius-users <freeradius-users(a)lists.freeradius.org> Message-ID: <20110225130914.GB12219(a)archwayconcepts.com> Content-Type: text/plain; charset=us-ascii vijay s sheelavantar <s_vijay65(a)rediffmail.com> wrote: > Hi, > Please clarify my doubts. > > 1. does pam_radius_auth.so support authorization of user accounts? the pam module just sends the user info to the radius server. The radius server does authorization and authentication.  It first authorizes via your authorization rules you defined.  If it passes that, it moves on to the authentication rules. There's nothing special you have to do on the pam module side. R. Marc ------------------------------ Message: 4 Date: Fri, 25 Feb 2011 18:48:40 +0500 From: Waqas Toor <waqasnasirtoor(a)gmail.com> Subject: Re: store and proxy accounting packets To: FreeRadius users mailing list    <freeradius-users(a)lists.freeradius.org> Cc: Alan DeKok <aland(a)deployingradius.com> Message-ID:    <AANLkTikNCwcteS+oFcb8btnjPiR9+zfX9HgYWwBz6R57(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Thank you Alan for you help, But please can you point out where I am wrong or a line may be which is a bad config, I am having trouble understanding why the packets are not being forwarded while being in site-enabled directory. I read the file I am still struggling to understand FreeRadius proxy and virtual servers, treat me as a noob Waqas On Fri, Feb 25, 2011 at 6:02 PM, Alan DeKok <aland(a)deployingradius.com> wrote: > Waqas Toor wrote: >>> ?Did you bother *reading* the "robust-proxy-accounting" file? >>> >> I have configured the robust-proxy-accounting > > ?That doesn't answer the question. ?The comments in that file describe > how it works. ?This includes answering your original question. > >> I am missing something but could not figure it out what > > ?The debug log doesn't show it receiving packets. > > ?What do you *expect* to happen when it doesn't received packets? > > ?The answer should be obvious: it's documented in the comments in the > "robust-proxy-accounting" file. > > ?Go read it. ------------------------------ Message: 5 Date: Fri, 25 Feb 2011 14:53:02 +0100 From: Alan DeKok <aland(a)deployingradius.com> Subject: Re: store and proxy accounting packets To: FreeRadius users mailing list    <freeradius-users(a)lists.freeradius.org> Message-ID: <4D67B43E.4020309(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Waqas Toor wrote: > Thank you Alan for you help, > But please can you point out where I am wrong or a line may be which > is a bad config, I am having trouble understanding why the packets are > not being forwarded while being in site-enabled directory.  As I said, the debug log you posted shows *no* packets being received.  How can it forward packets it doesn't receive?  How can you debug the failure to proxy packets, when it doesn't receive any packets? > I read the file I am still struggling to understand FreeRadius proxy > and virtual servers, treat me as a noob  I'm asking you to read the documents, and the messages on this list. Nothing more.  Alan DeKok. ------------------------------ Message: 6 Date: Fri, 25 Feb 2011 19:10:53 +0500 From: Waqas Toor <waqasnasirtoor(a)gmail.com> Subject: Re: store and proxy accounting packets To: FreeRadius users mailing list    <freeradius-users(a)lists.freeradius.org> Cc: Alan DeKok <aland(a)deployingradius.com> Message-ID:    <AANLkTinubNyY8nagxyVNK+G+DAOgqn8oV+ALiEiAVYsF(a)mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Ahaan, Ok below is an accounting packet and and its response also please tell me if the the lines that i get while in debug mode are normal ? Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.159171 sec Waking up in 1.1 seconds. ================================================= Waking up in 0.8 seconds. Polling for detail file /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* Detail listener /usr/local/var/log/radius/radacct/detail.example.com/detail-*:* state unopened signalled 0 waiting 1.058084 sec Waking up in 1.0 seconds. rad_recv: Accounting-Request packet from host 2.2.2.2 port 10044, id=248, length=248        Acct-Status-Type = Start        WiMAX-Beginning-Of-Session = 1        WiMAX-IP-Technology = Reserved-0        WiMAX-Prepaid-Indicator = 0        Acct-Session-Id = "12033268"        Acct-Multi-Session-Id = "9a7f45c70eb9cfc263d4b7f5db740d25"        non-hw-flow-info = "\000\000\000"        Framed-IP-Address = 175.110.77.76        User-Name = "002682D1A232(a)test_cpe.com"        Calling-Station-Id = "002682d1a232"        NAS-Identifier = "WASN"        WiMAX-hHA-IP-MIP4 = 0.0.0.0        NAS-IP-Address = 2.2.2.2        WiMAX-BS-Id = 0x303030303066303030663130        WiMAX-GMT-Timezone-offset = 18000        Event-Timestamp = "Feb 25 2011 18:36:49 PKT"        Huawei-Attr-218 = 0x00000000        NAS-Port-Type = Wireless-802.16 # Executing section preacct from file /usr/local/etc/raddb/sites-enabled/default +- entering group preacct {...} ++[preprocess] returns ok [acct_unique] WARNING: Attribute NAS-Port was not found in request, unique ID MAY be inconsistent [acct_unique] Hashing ',Client-IP-Address = 2.2.2.2,NAS-IP-Address = 2.2.2.2,Acct-Session-Id = "12033268",User-Name = "002682D1A232(a)test_cpe.com"' [acct_unique] Acct-Unique-Session-ID = "8b9e32f20020add2". ++[acct_unique] returns ok [suffix] Looking up realm "test_cpe.com" for User-Name = "002682D1A232(a)test_cpe.com" [suffix] No such realm "test_cpe.com" ++[suffix] returns noop ++[files] returns noop # Executing section accounting from file /usr/local/etc/raddb/sites-enabled/default +- entering group accounting {...} [detail]        expand: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d -> /usr/local/var/log/radius/radacct/2.2.2.2/detail-20110225 [detail] /usr/local/var/log/radius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/2.2.2.2/detail-20110225 [detail]        expand: %t -> Fri Feb 25 18:35:11 2011 ++[detail] returns ok ++[unix] returns noop [radutmp]       expand: /usr/local/var/log/radius/radutmp -> /usr/local/var/log/radius/radutmp [radutmp]       expand: %{User-Name} -> 002682D1A232(a)test_cpe.com  rlm_radutmp: No NAS-Port seen.  Cannot do anything.  rlm_radumtp: WARNING: checkrad will probably not work! ++[radutmp] returns noop [sql]   expand: %{User-Name} -> 002682D1A232(a)test_cpe.com [sql] sql_set_user escaped user --> '002682D1A232(a)test_cpe.com' [sql]   expand: INSERT into accounting (RadAcctId, AcctSessionId, AcctUniqueId, UserName, Realm, NASIPAddress, NASPortId, NASPortType, AcctStartTime, AcctStopTime, AcctSessionTime, AcctAuthentic, ConnectInfo_start, ConnectInfo_stop, AcctInputOctets, AcctOutputOctets, CalledStationId, CallingStationId, AcctTerminateCause, ServiceType, FramedProtocol, FramedIPAddress, AcctStartDelay, AcctStopDelay, XAscendSessionSvrKey, AcctStatusType) VALUES('', '%{Acct-Session-Id}', '%{Acct-Unique-Session-Id}', '%{SQL-User-Name}', '%{Realm}', '%{NAS-IP-Address}', '%{NAS-Port-Id}', '%{NAS-Port-Type}', TO_DATE('%S','yyyy-mm-dd hh24:mi:ss'), NULL, '0', '%{Acct-Authentic}', '%{Connect-Info}', '', '0', '0', '%{Called-Station-Id}', '%{Calling-Station-Id}', '', '%{Service-Type}', '%{Framed-Protocol}', '%{Framed-IP-Address}', '%{Acct-Delay-Time}', '0', '%{X-Ascend-Session-Svr-Key}', '%{Acct-Status-Type}') -> INSERT into accounting (RadAcctId, AcctSessionId, AcctUniqueId, UserName, Realm, NASIPAddress, NASPortId, NASPortType, AcctSta rlm_sql (sql): Reserving sql socket id: 0 rlm_sql (sql): Released sql socket id: 0 ++[sql] returns ok ++[exec] returns noop [attr_filter.accounting_response]       expand: %{User-Name} -> 002682D1A232(a)test_cpe.com attr_filter: Matched entry DEFAULT at line 12 ++[attr_filter.accounting_response] returns updated Sending Accounting-Response of id 248 to 2.2.2.2 port 10044 Finished request 9. Cleaning up request 9 ID 248 with timestamp +20 Going to the next request Waking up in 0.7 seconds. ======================================================= On Fri, Feb 25, 2011 at 6:53 PM, Alan DeKok <aland(a)deployingradius.com> wrote: > Waqas Toor wrote: >> Thank you Alan for you help, >> But please can you point out where I am wrong or a line may be which >> is a bad config, I am having trouble understanding why the packets are >> not being forwarded while being in site-enabled directory. > > ?As I said, the debug log you posted shows *no* packets being received. > > ?How can it forward packets it doesn't receive? > > ?How can you debug the failure to proxy packets, when it doesn't > receive any packets? > >> I read the file I am still struggling to understand FreeRadius proxy >> and virtual servers, treat me as a noob > > ?I'm asking you to read the documents, and the messages on this list. > Nothing more. > > ?Alan DeKok. > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html > ------------------------------ Message: 7 Date: Fri, 25 Feb 2011 15:39:53 +0100 From: Alan DeKok <aland(a)deployingradius.com> Subject: Re: store and proxy accounting packets To: FreeRadius users mailing list    <freeradius-users(a)lists.freeradius.org> Message-ID: <4D67BF39.8070803(a)deployingradius.com> Content-Type: text/plain; charset=ISO-8859-1 Waqas Toor wrote: > Ahaan, Ok below is an accounting packet and and its response > also please tell me if the the lines that i get while in debug mode are normal ?  Yes, but... > [suffix] Looking up realm "test_cpe.com" for User-Name = > "002682D1A232(a)test_cpe.com" > [suffix] No such realm "test_cpe.com"  That should be fixed.  Alan DeKok. ------------------------------ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html End of Freeradius-Users Digest, Vol 70, Issue 99 ************************************************

2 1

global hash variable Perl
by vhn 25 Feb '11

25 Feb '11

hi all, I was able to setup my freeradius to use perl and mysql. Things are working ok. I wanted to use a global hash variable to store information. This way all other requests can also access this hash variable. Is this doable? I know you can use mysql for this purpose, but i wanted to reduce the # of mysql hits. Thanks. -- View this message in context: http://freeradius.1045715.n5.nabble.com/global-hash-variable-Perl-tp3400771… Sent from the FreeRadius - User mailing list archive at Nabble.com.

1 0

Re: Auth-Type Perl instead of Auth-Type EAP?
by Alan Buxey 25 Feb '11

25 Feb '11

How are you dealing with the challenge response. If you use eap ttls with pap them this is not an issue alan ----- Reply message ----- From: "Josh Richard" <jrichar4(a)d.umn.edu> Date: Fri, Feb 25, 2011 17:59 Subject: Auth-Type Perl instead of Auth-Type EAP? To: "freeradius-users(a)lists.freeradius.org" <freeradius-users(a)lists.freeradius.org> Hello list, After a bit of digging, I would like to ask a question to ensure this idea is even possible. :) I am running FR 2 on Debian. What I would like to do is have a WPA2 PEAP/MS_ChapV2 Cisco wireless SSID hook into the FR server above. The FR server currently is using rlm_perl to handle authentication and this does work with FR running with -x and a client test using radtest: Sending Access-Request of id 184 to <ip> port 1812 User-Name = "jrichar4" User-Password = "removed" NAS-IP-Address = 127.0.1.1 NAS-Port = 10 rad_recv: Access-Accept packet from host <ip> port 1812, id=184, length=20 on the server I see: rlm_perl: Added pair User-Name = jrichar4 rlm_perl: Added pair User-Password = <removed> rlm_perl: Added pair NAS-IP-Address = 127.0.1.1 rlm_perl: Added pair NAS-Port = 10 rlm_perl: Added pair Crypt-Password = <removed> rlm_perl: Added pair Auth-Type = Perl I wrote some Perl in the rlm_perl code that uses Perl's Authen::Radius to proxy the lookup to a different production FR server containing the set of all users. Neat. I hope to use this server to flip VLANs using $RAD_REPLY{'Tunnel-Private-Group-ID'} based on an eventual db lookup to control wireless machine infections without mutzing with an existing server. When the SSID is wired in, we see this: [peap] Got inner identity 'jrichar4' # Executing section authorize from file /etc/freeradius/sites-enabled/inner-tunnel rlm_perl: Added pair User-Name = jrichar4 rlm_perl: Added pair EAP-Message = 0x0206000c016d736865746b61 rlm_perl: Added pair EAP-Type = Identity rlm_perl: Added pair FreeRADIUS-Proxied-To = 127.0.0.1 rlm_perl: Added pair Crypt-Password = * rlm_perl: Added pair Auth-Type = EAP rlm_perl: Added pair Proxy-To-Realm = LOCAL rlm_perl: Added pair EAP-Type = MS-CHAP-V2 I would prefer the use Auth-Type = Perl in the EAP inner tunnel. Is this possible? I am hoping something simple is amiss as this is close to working! I have only: DEFAULT Auth-Type = Perl in users. In inner tunnel I have: authenticate { .... Auth-Type Perl { perl } ... eap } Do I need to overload anything in eap.conf? Thank you all and kind regards, Josh Richard University of Minnesota Duluth USA - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

1 0

pam_radius_auth query
by vijay s sheelavantar 25 Feb '11

25 Feb '11

Hi,Please clarify my doubts. 1. does pam_radius_auth.so support authorization of user accounts? 2. If Yes how can we achieve it? what configurations need to be done. Now pam_radius_auth.c sends authentication requests with the value PW_AUTHENTICATE_ONLY. what value i need to send? and what configuration I have to make at server side to implement authorization. I am using pam_radius_auth.so for authentication and it is working fine. At the free radius server side  I am authenticating users using /etc/password  file as database.(I have enabled "unix" option in "default" file authorization section.) Thanks and Regards, VIJAY S.

3 2

TTLS-MSCHAPv2 works but PEAP-MSCHAPv2 doesn't (FreeRADIUS 2.1.3)
by Wenche Backman 25 Feb '11

25 Feb '11

Hi, I have a FreeRADIUS-server for configuration testing purposes and on this server TTLS-MSCHAPv2 works fine but PEAP-MSCHAPv2 fails. PEAP-MSCHAPv2 fails both with the WindowsXP client and the NetworkManager included in Ubuntu 8.04 LTS. The output from radius -X are shown below. The configuration files are attached. I'd appreciate if someone could take a look at this and check where the problem might be. Regards, Wenche Backman PEAP-MSCHAPv2 failure (this one from Ubuntu 8.04 LTS, the output from WinXP is the same): Ready to process requests rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=137 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x02000011016475406d79746573742e6669 Message-Authenticator = 0xb613072b66070df9b35799b65683a666 server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 0 length 17 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled } # server eduroam Sending Access-Challenge of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x010100061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xb667f4e0b666ed0567b6ebba8e637a5c Finished request 0. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=231 Cleaning up request 0 ID 0 with timestamp +107 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 State = 0xb667f4e0b666ed0567b6ebba8e637a5c NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0201005d190016030100520100004e03014d638d2813d992579c034f3369d4734a02fcc8603b1297948e5ee5d6950eb9ae00002600390038003500160013000a00330032002f0005000400150012000900140011000800060003020100 Message-Authenticator = 0x7aaf685db9bfc8a730e04e61846a8ba4 server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 1 length 93 [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 [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] (other): before/accept initialization [peap] TLS_accept: before/accept initialization [peap] <<< TLS 1.0 Handshake [length 0052], ClientHello [peap] TLS_accept: SSLv3 read client hello A [peap] >>> TLS 1.0 Handshake [length 002a], ServerHello [peap] TLS_accept: SSLv3 write server hello A [peap] >>> TLS 1.0 Handshake [length 085e], Certificate [peap] TLS_accept: SSLv3 write certificate A [peap] >>> TLS 1.0 Handshake [length 020d], ServerKeyExchange [peap] TLS_accept: SSLv3 write key exchange A [peap] >>> TLS 1.0 Handshake [length 0004], ServerHelloDone [peap] TLS_accept: SSLv3 write server done A [peap] TLS_accept: SSLv3 flush data [peap] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled } # server eduroam Sending Access-Challenge of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x0102040019c000000aad160301002a0200002603014d638d2822caad2a4af2262ab74eea2824d9767d409a66ca0cfad0ae45610e7500003901160301085e0b00085a0008570003a6308203a23082028aa003020102020101300d06092a864886f70d0101040500308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479 EAP-Message = 0x301e170d3039303131363130323433375a170d3130303131363130323433375a307c310b3009060355040613024652310f300d0603550408130652616469757331153013060355040a130c4578616d706c6520496e632e312330210603550403131a4578616d706c65205365727665722043657274696669636174653120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d30820122300d06092a864886f70d01010105000382010f003082010a0282010100bca3a7d340515ebd6023cbfb2c18b2ffc99f5276c2af17db6621b34a2e596aa4193eee8582efc0a84f8cb24b740602f7344f0d3e07f05dfab378f03112e3 EAP-Message = 0xa43530d75b5a611e456d530cc9e9a5143dbdcf6129d99273f9960b4d6bb2124f42bc61be778bad4e34a21d75e2904cc26ab003927898cdab60fb4bc1780c19d23e5d64065248e8a2e586a9d7f7ac6dc089269890532c952ea979de7202b549e5979c1be63419a29d64febe0a4576d629e7431a2e1fcca05c550172c0c4e309e746662bb2a80d26c975b979409596dd3e079a96850532745cb92dfdca8aab7bbb66fedd8a9ac3f30c62252a453c57acbc33cb0f669326ece07032fafb4584bcc417430203010001a317301530130603551d25040c300a06082b06010505070301300d06092a864886f70d01010405000382010100110e3b6ca51ea7854b EAP-Message = 0x05a122cefcc96f0060bc1c3d2de06a79f50ff17de7c50664598b7b499ebf536f80bc0c3a86bfb6c9837cd23992d522be1693f12aa3b9e8eead66d0e85316cb038b7673642d83b924891b057126d85e52d91452c0a52203424fc16d6094e812ef0bd1535852edbe3e5a9696a0c5c7611badba4f789f1a04dd6548127c82d7b4e4635c03b12b621b2b4022644907e12ab5f0ecfd4863cfeb440636da869fcb57b65d67b95c007afb7bd160d20e01d946cb8f4d7a3d6c252417172ea45ffb847585e98c8c6d0d34094d031cc69cfc015b24297fa0d085fe4dfb2b2de27a9363d8d023b151867e8a5c04dcfc072e0397a063db3bf4bdc5f26f0004ab308204 EAP-Message = 0xa73082038fa0030201020209 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xb667f4e0b765ed0567b6ebba8e637a5c Finished request 1. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=144 Cleaning up request 1 ID 0 with timestamp +107 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 State = 0xb667f4e0b765ed0567b6ebba8e637a5c NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020200061900 Message-Authenticator = 0xf24d59a32f188207dee0c313a901bfb3 server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 2 length 6 [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 [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled } # server eduroam Sending Access-Challenge of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x010303fc19400095425f8466e364f5300d06092a864886f70d0101050500308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f72697479301e170d3039303131363130323433375a170d3130303131363130323433375a308193310b3009060355040613024652310f300d060355040813065261646975733112301006035504 EAP-Message = 0x071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f7269747930820122300d06092a864886f70d01010105000382010f003082010a0282010100a79b656861b09eb9d5bd77174981b3b00554530ffc18238cf3164a1882e42c6379db8d256187bc4788e63349ae25379f606087ab41864d8a533d738c7c5286b4057c96d0f5be5972a34b0d27d784d2571bc8a085f15fd17942948566e7589f1b4994676beb9e3d9828bdda3bd6f767 EAP-Message = 0xed21bdf2e4bd035a8e235ddf4341c2b5a587e707e5b333c49d4533110ce905b31071c90bc795dee46e8b0b063862c0d58c4765553bcef3d8408dffcb951b81a1b5e8e61f5e857bc6f5931f132146fd145ed316517e7e8bd8f5941b7d571a7a0b8500a2d4538c0a036d12ce655a55dea0b4360739b0c251ed44c91900b67a7206c83e22b34ead286d9ac6023258892f4d150203010001a381fb3081f8301d0603551d0e041604140397fbc3d67c570e8f13b91c45394b5f44616cf43081c80603551d230481c03081bd80140397fbc3d67c570e8f13b91c45394b5f44616cf4a18199a48196308193310b3009060355040613024652310f300d06035504 EAP-Message = 0x0813065261646975733112301006035504071309536f6d65776865726531153013060355040a130c4578616d706c6520496e632e3120301e06092a864886f70d010901161161646d696e406578616d706c652e636f6d312630240603550403131d4578616d706c6520436572746966696361746520417574686f7269747982090095425f8466e364f5300c0603551d13040530030101ff300d06092a864886f70d0101050500038201010023477ecf0e1f391af60dccc8605dd8743615a07242f1d68f3815855b86ab605a9fa22c9da76fe73fdcceb1a76afb224d424dd032efa93e7d7bacc26a0fc592ed29a04993e5c4043fcfd4312b92337b2919f5 EAP-Message = 0x5746b2fc48857aac Message-Authenticator = 0x00000000000000000000000000000000 State = 0xb667f4e0b464ed0567b6ebba8e637a5c Finished request 2. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=144 Cleaning up request 2 ID 0 with timestamp +107 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 State = 0xb667f4e0b464ed0567b6ebba8e637a5c NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020300061900 Message-Authenticator = 0xb8250ec4167cfca1229cd8fed99c2ebe server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 3 length 6 [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 [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled } # server eduroam Sending Access-Challenge of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x010402c71900d8fba265108675c4143ba764839add9dad12b1e94d9c914c0f18108e5d9f99090bf291b83623238457fe4576e87c1f3b3cb9dd0cf0de1522e48948e5af796c8ed530986f5610a0dc3b0d89fa14686238e318a1cbb0de862d2ea63cc0b0b29ae1210bf94ab9e772de19b817e7d0df45b71a9595499756b5d5e6c757ca7bc55b1fc7a3ebe98be922105889149cfaa023c94eda62121c053d11f6c6e59736b2d25a0496aab4db2f160301020d0c0002090080d6c327b60d685b7dea0b3bf533d54f8e151fb5d72b4a805e4c120a847706984eedeb80d3a48fabd0f36bbabdd4125fe717709c5c73010ac5185e4154b12c4738f6cb62d40b82 EAP-Message = 0x47efc9ae7da9c0612f0bf7592be07f1eb2f5b45b5289743831f2b2cad359dbf213c9e14aaf44a1ede1e7ac48b9fbb7b371d82ec2d6ab9415ff230001020080185049cf069168f5fa3037bab3f8cbe72ffa09d5222d80db41a2265b2a270aae741f7ef06a574144055e27724d75001556dd166feedcfb7827625b2fa66f72a1c85cd9dc3e1dd693ef38f2bf0c3d8f08e21d86b9ed9d8dba54a571bdb36bed6190ddfa42816f76e3a154799ba7c629ca358df7f55f2746f7918be7a9ded259fb01006b443e4a0e6f85d615db5c3a3308860a8e7335b4c3ed7a6ca6a26b60b60399b81d97499c77a6c889c21293b3bcc5ff03b87cc98556f0b3d6c1e211ed EAP-Message = 0x7e11c75caad6f24d6d967130f88120690fbce884666d5c4d9e235230e58b53878eb7437b253601580401c2cafba3ae088abce707763cec25709e95cb0dc4a3a9b772a507058baa5783dbf780b2e59cc2be5e8bf28401722211bec6093170c426993baf969daad724132211f1ae38314bbbb6e6a7681a57894482574f43fc60fc18d8f40b92d2fa6de896ddedfd5be469845235a8fa561c2abc94cd37764575ff0c209165d1d128af9cde0b51be10533052b7180313f411529ba43abd073e54b2111495a516030100040e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xb667f4e0b563ed0567b6ebba8e637a5c Finished request 3. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=342 Cleaning up request 3 ID 0 with timestamp +107 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 State = 0xb667f4e0b563ed0567b6ebba8e637a5c NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020400cc1900160301008610000082008086f0298b073e157e853a830e045a18b40f17a02efbe131d943518b00817f8a72a2be1b64d1208657beea1cff038418106c6beda352e34d9950e7b9c397932bd7cb8f722ff87b819edfea5910676e1e898ec4c071c6cdedab5b8c8980dbd752c9f74bbf5818cc35900515d0a97a4b6139b94e24c2b0aa1aa7ca282e205952121e140301000101160301003053d0e5fbe8ed7e32c5d7318f3baf834371d7ccc760d9a0fb0b2320f9707c9acf7f218bcb8c70a8b51e88bbdc2274aec8 Message-Authenticator = 0x7b92c60ebe961910947ed53e0f3deced server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 4 length 204 [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 [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] <<< TLS 1.0 Handshake [length 0086], ClientKeyExchange [peap] TLS_accept: SSLv3 read client key exchange A [peap] <<< TLS 1.0 ChangeCipherSpec [length 0001] [peap] <<< TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 read finished A [peap] >>> TLS 1.0 ChangeCipherSpec [length 0001] [peap] TLS_accept: SSLv3 write change cipher spec A [peap] >>> TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 write finished A [peap] TLS_accept: SSLv3 flush data [peap] (other): SSL negotiation finished successfully SSL Connection Established [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled } # server eduroam Sending Access-Challenge of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x01050041190014030100010116030100305a7b9877876923768d3f6b8ddffb2a49d7c701b35c74a0c803a5c99b9b632fcb4eeb6ef635de4e8994feef3c84f828ff Message-Authenticator = 0x00000000000000000000000000000000 State = 0xb667f4e0b262ed0567b6ebba8e637a5c Finished request 4. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=144 Cleaning up request 4 ID 0 with timestamp +107 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 State = 0xb667f4e0b262ed0567b6ebba8e637a5c NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020500061900 Message-Authenticator = 0xc5648cb005eb7be3dcd512844c73fc53 server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 5 length 6 [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 [peap] Received TLS ACK [peap] ACK handshake is finished [peap] eaptls_verify returned 3 [peap] eaptls_process returned 3 [peap] EAPTLS_SUCCESS ++[eap] returns handled } # server eduroam Sending Access-Challenge of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x0106002b190017030100204911606b54a92f837428b80e62f8fd2eaa9def9e14ca28d915ccc4e1718e421e Message-Authenticator = 0x00000000000000000000000000000000 State = 0xb667f4e0b361ed0567b6ebba8e637a5c Finished request 5. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=234 Cleaning up request 5 ID 0 with timestamp +107 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 State = 0xb667f4e0b361ed0567b6ebba8e637a5c NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020600601900170301002084f81dbeee164be0d004166b849fec7362852574d78846dad2b62b39b08cf6a51703010030825c7db26910cfcc090ad6f9edf862db3bf8a16401564750eb0bcf77857da0fdb7de955192557ac83755357f816949b9 Message-Authenticator = 0xa9e56e06a53d4769e832e0f8cee70a4d server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 6 length 96 [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 [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] eaptls_process returned 7 [peap] EAPTLS_OK [peap] Session established. Decoding tunneled attributes. [peap] Identity - du(a)mytest.fi [peap] Got tunneled request EAP-Message = 0x02060011016475406d79746573742e6669 server eduroam { PEAP: Got tunneled identity of du(a)mytest.fi PEAP: Setting default EAP type for tunneled EAP session. PEAP: Setting User-Name to du(a)mytest.fi Sending tunneled request EAP-Message = 0x02060011016475406d79746573742e6669 FreeRADIUS-Proxied-To = 127.0.0.1 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 server eduroam-inner-tunnel { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [files] users: Matched entry du(a)mytest.fi at line 206 ++[files] returns ok ++[mschap] returns noop [pap] Normalizing NT-Password from hex encoding [pap] No clear-text password in the request. Not performing PAP. ++[pap] returns noop No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server eduroam-inner-tunnel [peap] Got tunneled reply code 3 [peap] Got tunneled reply RADIUS code 3 [peap] Tunneled authentication was rejected. [peap] FAILURE ++[eap] returns handled } # server eduroam Sending Access-Challenge of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x0107003b19001703010030998319d6fd8e167dc17373bdbd74ff90ed3b3565f1eeec9f48a3fabf8022e8a3f0d84d04fed1507c2be2696c67f0591b Message-Authenticator = 0x00000000000000000000000000000000 State = 0xb667f4e0b060ed0567b6ebba8e637a5c Finished request 6. Going to the next request Waking up in 4.9 seconds. rad_recv: Access-Request packet from host 193.166.6.179 port 2048, id=0, length=234 Cleaning up request 6 ID 0 with timestamp +107 User-Name = "du(a)mytest.fi" NAS-IP-Address = 193.166.6.179 Called-Station-Id = "000d0b6cd027" Calling-Station-Id = "001de01a9a47" NAS-Identifier = "000d0b6cd027" NAS-Port = 7 Framed-MTU = 1400 State = 0xb667f4e0b060ed0567b6ebba8e637a5c NAS-Port-Type = Wireless-802.11 EAP-Message = 0x02070060190017030100206a2891cc8d712812216d36fc9a6aafafcfa02faf5c3746b46c8b5bd3fec306071703010030bb13eb9f3a5a8808db75cf59c22d50994ae45e0ecc1f7b91c3e00de1e70e8e45a98adbe3b2d7a7e15547c50362d7fdda Message-Authenticator = 0x534b7bb55532f1fde1e5c3205e83ecae server eduroam { +- entering group authorize {...} [auth_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] /var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/auth-detail-20110222 [auth_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[auth_log] returns ok [suffix] Looking up realm "mytest.fi" for User-Name = "du(a)mytest.fi" [suffix] Found realm "mytest.fi" [suffix] Adding Realm = "mytest.fi" [suffix] Authentication realm is LOCAL. ++[suffix] returns ok [eap] EAP packet type response id 7 length 96 [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 [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] eaptls_process returned 7 [peap] EAPTLS_OK [peap] Session established. Decoding tunneled attributes. [peap] Received EAP-TLV response. [peap] Had sent TLV failure. User was rejected earlier in this session. [eap] Handler failed in EAP/peap [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. } # server eduroam Using Post-Auth-Type Reject +- entering group REJECT {...} [reply_log] expand: /var/log/radius/radacct/%{Client-IP-Address}/reply-detail-%Y%m%d -> /var/log/radius/radacct/193.166.6.179/reply-detail-20110222 [reply_log] /var/log/radius/radacct/%{Client-IP-Address}/reply-detail-%Y%m%d expands to /var/log/radius/radacct/193.166.6.179/reply-detail-20110222 [reply_log] expand: %t -> Tue Feb 22 12:17:12 2011 ++[reply_log] returns ok Delaying reject of request 7 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 7 Sending Access-Reject of id 0 to 193.166.6.179 port 2048 EAP-Message = 0x04070004 Message-Authenticator = 0x00000000000000000000000000000000 Waking up in 4.9 seconds. Cleaning up request 7 ID 0 with timestamp +107 Ready to process requests. Wenche Backman Tietoliikenneasiantuntija CSC - Tieteen tietotekniikan keskus Oy PL 405, 02101 Espoo (09) 457 2737, Wenche.Backman(a)csc.fi Ms. Wenche Backman Data Communications Specialist CSC - IT Center for Science Ltd. P.O. BOX 405, FI-02101 Espoo, Finland +358 9 457 2737, Wenche.Backman(a)csc.fi

2 2

Logging the matched SQL-Group
by Brian Candler 24 Feb '11

24 Feb '11

When rlm_sql is running through each of a user's groups, the value %{SQL-Group} is set for each iteration. However it's cleared at the end. I would like to be able to capture the value of SQL-Group which was successfully matched (if any), so that I can log it in rlm_sql_log. Is there a straightforward way of doing this? Because I can't see one right now... Thanks, Brian.

2 2

non-standard authentication
by Travis Dimmig 24 Feb '11

24 Feb '11

I have a problem scenario where I need to be able to handle the authentication of users myself. I am looking into using either rlm_perl or (preferably) rlm_jradius to be able to write my own piece to do authentication. I believe this is possible with either module (please correct me if I'm wrong on that, it would stop me in my tracks). What I need to know is if when writing my own authenticator there is a terribly complicated process of requests and responses that I have to honor in order to make the supplicant happy, or if I can trivially accept or reject based on the parameters of my business problem. As a test case, I wrote a Java class for rlm_jradius that just replaced reject packets with accept packets, to see if it would work. I found that if I hooked into it at the 'post_auth' stage it didn't matter what my reply was, freeRadius remembered that auth had failed and stripped all the attributes from the response packet. That was long winded, here is a summary of my questions. Can I write my own piece to do authentication? Where in the freeRadius process do I list that listener? Is there a series of requests and responses that I have to honor? -Travis

4 5