- Freeradius-Users - lists.freeradius.org

EAP/TLS PEAP on Suse 9.3 Ldap backend eDirectory
by Daniel Hesse 21 Sep '05

21 Sep '05

I am succesfully doing this but with one glitch. It only works with WinXP as the supplicant. The problem I can tell is with Certs, but I cannot figure out how to fix it. So far the chipsets on the adapters is Atheros 5211 and Ralink rt2500. The ralinks authenticate fine using WinXP as supplicant, but fail using the ralink client software in Win2k and WinXP. The GN-WPEAG chipsets also fail using the supplied clients. Is there something special to know or do to get certs.sh to work properly in Suse 9.3, so far I have only been able to get it to work by installing OpenSSL in USR/Local even though Suse 93 says it is already installed. I am including two log peices, the 1st with WinXP as Authenticating and 2nd is Ralink utility on same machine failing to authenticate. WINXP TLS_accept: SSLv3 read client key exchange A rlm_eap_tls: <<< TLS 1.0 ChangeCipherSpec [length 0001] rlm_eap_tls: <<< TLS 1.0 Handshake [length 0010], Finished TLS_accept: SSLv3 read finished A rlm_eap_tls: >>> TLS 1.0 ChangeCipherSpec [length 0001] TLS_accept: SSLv3 write change cipher spec A rlm_eap_tls: >>> TLS 1.0 Handshake [length 0010], Finished TLS_accept: SSLv3 write finished A TLS_accept: SSLv3 flush data (other): SSL negotiation finished successfully SSL Connection Established eaptls_process returned 13 rlm_eap_peap: EAPTLS_HANDLED modcall[authenticate]: module eap returns handled for request 2 modcall: group authenticate returns handled for request 2 Sending Access-Challenge of id 180 to 10.10.4.20:2500 EAP-Message = 0x0104003119001403010001011603010020fb444951ea0360a043b79a34ac4ca533ae9744e6dc6fd7cda10c7b0470fbc55b Message-Authenticator = 0x00000000000000000000000000000000 State = 0xd86ec63a7680f4308aeb922aa999e201 Finished request 2 Going to the next request --- Walking the entire request list --- Waking up in 5 seconds... rad_recv: Access-Request packet from host 10.10.4.20:2501, id=181, length=136 NAS-IP-Address = 10.10.4.20 NAS-Port-Type = Wireless-802.11 NAS-Port = 0 Framed-MTU = 1400 User-Name = dhesse Calling-Station-Id = 001109229950 Called-Station-Id = 000e6acd7ff5 NAS-Identifier = dhlab_3com State = 0xd86ec63a7680f4308aeb922aa999e201 EAP-Message = 0x020400061900 Message-Authenticator = 0x76ad5ea260dbcc6ec8c011c9c7faa527 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 3 modcall[authorize]: module preprocess returns ok for request 3 modcall[authorize]: module chap returns noop for request 3 modcall[authorize]: module mschap returns noop for request 3 rlm_realm: No '@' in User-Name = dhesse, looking up realm NULL rlm_realm: No such realm NULL modcall[authorize]: module suffix returns noop for request 3 rlm_eap: EAP packet type response id 4 length 6 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module eap returns updated for request 3 users: Matched entry DEFAULT at line 152 modcall[authorize]: module files returns ok for request 3 rlm_ldap: - authorize rlm_ldap: performing user authorization for dhesse radius_xlat: '(uid=dhesse)' radius_xlat: 'o=StormLake' rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in o=StormLake, with filter (uid=dhesse) rlm_ldap: Added the eDirectory password in check items rlm_ldap: looking for check items in directory... rlm_ldap: looking for reply items in directory... rlm_ldap: user dhesse authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 modcall[authorize]: module ldap returns ok for request 3 modcall: group authorize returns updated for request 3 rad_check_password: Found Auth-Type EAP auth: type EAP Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 3 rlm_eap: Request found, released from the list rlm_eap: EAP/peap rlm_eap: processing type peap rlm_eap_peap: Authenticate rlm_eap_tls: processing TLS rlm_eap_tls: Received EAP-TLS ACK message rlm_eap_tls: ack handshake is finished eaptls_verify returned 3 eaptls_process returned 3 rlm_eap_peap: EAPTLS_SUCCESS modcall[authenticate]: module eap returns handled for request 3 modcall: group authenticate returns handled for request 3 Sending Access-Challenge of id 181 to 10.10.4.20:2501 EAP-Message = 0x0105002019001703010015bc0c8b230b6818687fdf49953a86ea2a7c92d8f0be Message-Authenticator = 0x00000000000000000000000000000000 State = 0x34fc3101d2597dcae9f02eb68c529953 Finished request 3 Going to the next request Waking up in 5 seconds... rad_recv: Access-Request packet from host 10.10.4.20:2502, id=182, length=164 NAS-IP-Address = 10.10.4.20 NAS-Port-Type = Wireless-802.11 NAS-Port = 0 Framed-MTU = 1400 User-Name = dhesse Calling-Station-Id = 001109229950 Called-Station-Id = 000e6acd7ff5 NAS-Identifier = dhlab_3com State = 0x34fc3101d2597dcae9f02eb68c529953 EAP-Message = 0x02050022190017030100171d156bb7f6783f7d189e1907099a9fa7309a04e469c5b1 Message-Authenticator = 0xe538669776929af733db5ebd93558b24 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 4 modcall[authorize]: module preprocess returns ok for request 4 modcall[authorize]: module chap returns noop for request 4 modcall[authorize]: module mschap returns noop for request 4 rlm_realm: No '@' in User-Name = dhesse, looking up realm NULL rlm_realm: No such realm NULL modcall[authorize]: module suffix returns noop for request 4 rlm_eap: EAP packet type response id 5 length 34 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module eap returns updated for request 4 users: Matched entry DEFAULT at line 152 modcall[authorize]: module files returns ok for request 4 rlm_ldap: - authorize rlm_ldap: performing user authorization for dhesse radius_xlat: '(uid=dhesse)' radius_xlat: 'o=StormLake' rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in o=StormLake, with filter (uid=dhesse) rlm_ldap: Added the eDirectory password in check items rlm_ldap: looking for check items in directory... rlm_ldap: looking for reply items in directory... rlm_ldap: user dhesse authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 modcall[authorize]: module ldap returns ok for request 4 modcall: group authorize returns updated for request 4 rad_check_password: Found Auth-Type EAP auth: type EAP Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 4 rlm_eap: Request found, released from the list rlm_eap: EAP/peap rlm_eap: processing type peap rlm_eap_peap: Authenticate rlm_eap_tls: processing TLS eaptls_verify returned 7 rlm_eap_tls: Done initial handshake eaptls_process returned 7 rlm_eap_peap: EAPTLS_OK rlm_eap_peap: Session established. Decoding tunneled attributes. rlm_eap_peap: Identity - dhesse rlm_eap_peap: Tunneled data is valid. PEAP: Got tunneled identity of dhesse PEAP: Setting default EAP type for tunneled EAP session. PEAP: Setting User-Name to dhesse Processing the authorize section of radiusd.conf modcall: entering group authorize for request 4 modcall[authorize]: module preprocess returns ok for request 4 modcall[authorize]: module chap returns noop for request 4 modcall[authorize]: module mschap returns noop for request 4 rlm_realm: No '@' in User-Name = dhesse, looking up realm NULL rlm_realm: No such realm NULL modcall[authorize]: module suffix returns noop for request 4 rlm_eap: EAP packet type response id 5 length 11 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module eap returns updated for request 4 users: Matched entry DEFAULT at line 152 modcall[authorize]: module files returns ok for request 4 rlm_ldap: - authorize rlm_ldap: performing user authorization for dhesse radius_xlat: '(uid=dhesse)' radius_xlat: 'o=StormLake' rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in o=StormLake, with filter (uid=dhesse) rlm_ldap: Added the eDirectory password in check items rlm_ldap: looking for check items in directory... rlm_ldap: looking for reply items in directory... rlm_ldap: user dhesse authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 modcall[authorize]: module ldap returns ok for request 4 modcall: group authorize returns updated for request 4 rad_check_password: Found Auth-Type EAP auth: type EAP Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 4 rlm_eap: EAP Identity rlm_eap: processing type mschapv2 rlm_eap_mschapv2: Issuing Challenge modcall[authenticate]: module eap returns handled for request 4 modcall: group authenticate returns handled for request 4 PEAP: Got tunneled Access-Challenge modcall[authenticate]: module eap returns handled for request 4 modcall: group authenticate returns handled for request 4 Sending Access-Challenge of id 182 to 10.10.4.20:2502 EAP-Message = 0x010600371900170301002c2e60ef6cbaeb243c56acedee7a7f10fd837170ff8a7cf9db7376f6b80f3978e34405f8355b645ec66f716d00 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x5658e0fa40025a64a9c21e91575b399d Finished request 4 Going to the next request Waking up in 5 seconds... rad_recv: Access-Request packet from host 10.10.4.20:2503, id=183, length=218 NAS-IP-Address = 10.10.4.20 NAS-Port-Type = Wireless-802.11 NAS-Port = 0 Framed-MTU = 1400 User-Name = dhesse Calling-Station-Id = 001109229950 Called-Station-Id = 000e6acd7ff5 NAS-Identifier = dhlab_3com State = 0x5658e0fa40025a64a9c21e91575b399d EAP-Message = 0x020600581900170301004dde7841f54a1023bc51de5b1049a3f40bc6a3885985ce3a25d2bb4eccc1b5750fb81735d317f01cdf5be04fa5ffb8d4ba2d8c4797bcc127929b672758a2ffe8fc4618d3ac27af90766780edb361 Message-Authenticator = 0xb1ca667f588b5c0be2ebe759ba2d3d71 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 5 modcall[authorize]: module preprocess returns ok for request 5 modcall[authorize]: module chap returns noop for request 5 modcall[authorize]: module mschap returns noop for request 5 rlm_realm: No '@' in User-Name = dhesse, looking up realm NULL rlm_realm: No such realm NULL modcall[authorize]: module suffix returns noop for request 5 rlm_eap: EAP packet type response id 6 length 88 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module eap returns updated for request 5 users: Matched entry DEFAULT at line 152 modcall[authorize]: module files returns ok for request 5 rlm_ldap: - authorize rlm_ldap: performing user authorization for dhesse radius_xlat: '(uid=dhesse)' radius_xlat: 'o=StormLake' rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in o=StormLake, with filter (uid=dhesse) rlm_ldap: Added the eDirectory password in check items rlm_ldap: looking for check items in directory... rlm_ldap: looking for reply items in directory... rlm_ldap: user dhesse authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 modcall[authorize]: module ldap returns ok for request 5 modcall: group authorize returns updated for request 5 rad_check_password: Found Auth-Type EAP auth: type EAP Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 5 rlm_eap: Request found, released from the list rlm_eap: EAP/peap rlm_eap: processing type peap rlm_eap_peap: Authenticate rlm_eap_tls: processing TLS eaptls_verify returned 7 rlm_eap_tls: Done initial handshake eaptls_process returned 7 rlm_eap_peap: EAPTLS_OK rlm_eap_peap: Session established. Decoding tunneled attributes. rlm_eap_peap: EAP type mschapv2 rlm_eap_peap: Tunneled data is valid. PEAP: Setting User-Name to dhesse PEAP: Adding old state with 27 d7 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 5 modcall[authorize]: module preprocess returns ok for request 5 modcall[authorize]: module chap returns noop for request 5 modcall[authorize]: module mschap returns noop for request 5 rlm_realm: No '@' in User-Name = dhesse, looking up realm NULL rlm_realm: No such realm NULL modcall[authorize]: module suffix returns noop for request 5 rlm_eap: EAP packet type response id 6 length 65 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module eap returns updated for request 5 users: Matched entry DEFAULT at line 152 modcall[authorize]: module files returns ok for request 5 rlm_ldap: - authorize rlm_ldap: performing user authorization for dhesse radius_xlat: '(uid=dhesse)' radius_xlat: 'o=StormLake' rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in o=StormLake, with filter (uid=dhesse) rlm_ldap: Added the eDirectory password in check items rlm_ldap: looking for check items in directory... rlm_ldap: looking for reply items in directory... rlm_ldap: user dhesse authorized to use remote access rlm_ldap: ldap_release_conn: Release Id: 0 modcall[authorize]: module ldap returns ok for request 5 modcall: group authorize returns updated for request 5 rad_check_password: Found Auth-Type EAP auth: type EAP Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 5 rlm_eap: Request found, released from the list rlm_eap: EAP/mschapv2 rlm_eap: processing type mschapv2 Processing the authenticate section of radiusd.conf modcall: entering group Auth-Type for request 5 rlm_mschap: Told to do MS-CHAPv2 for dhesse with NT-Password rlm_mschap: adding MS-CHAPv2 MPPE keys modcall[authenticate]: module mschap returns ok for request 5 modcall: group Auth-Type returns ok for request 5 MSCHAP Success modcall[authenticate]: module eap returns handled for request 5 modcall: group authenticate returns handled for request 5 PEAP: Got tunneled Access-Challenge modcall[authenticate]: module eap returns handled for request 5 modcall: group authenticate returns handled for request 5 Sending Access-Challenge of id 183 to 10.10.4.20:2503 EAP-Message = 0x0107004a1900170301003f0226fad9a3d3afef959674ecb3b3414541310676070004398f63d7a5bba3441ee2a3dfcdbbbde73f91f7312051a0f5b579bf9193eb090630c7be88de6d4dee Message-Authenticator = 0x00000000000000000000000000000000 State = 0x0c24a22194018da936facb78fe3ceaf8 Finished request 5 Going to the next request Waking up in 5 seconds... rad_recv: Access-Request packet from host 10.10.4.20:2504, id=184, length=159 NAS-IP-Address = 10.10.4.20 NAS-Port-Type = Wireless-802.11 NAS-Port = 0 Framed-MTU = 1400 User-Name = dhesse Calling-Station-Id = 001109229950 Called-Station-Id = 000e6acd7ff5 NAS-Identifier = dhlab_3com State = 0x0c24a22194018da936facb78fe3ceaf8 EAP-Message = 0x0207001d19001703010012f1bdeccdf36c88896d25284d609126cdf8ac Message-Authenticator = 0x48bcf0174488515db7aab6c2b9615e3d Processing the authorize section of radiusd.conf modcall: entering group authorize for request 6 modcall[authorize]: module preprocess returns ok for request 6 modcall[authorize]: module chap returns noop for request 6 modcall[authorize]: module mschap returns noop for request 6 rlm_realm: No '@' in User-Name = dhesse, looking up realm NULL rlm_realm: No such realm NULL modcall[authorize]: module suffix returns noop for request 6 rlm_eap: EAP packet type response id 7 length 29 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module eap returns updated for request 6 users: Matched entry DEFAULT at line 152 modcall[authorize]: module files returns ok for request 6 rlm_ldap: - authorize rlm_ldap: performing user authorization for dhesse radius_xlat: '(uid=dhesse)' radius_xlat: 'o=StormLake' rlm_ldap: ldap_get_conn: Checking Id: 0 rlm_ldap: ldap_get_conn: Got Id: 0 rlm_ldap: performing search in o=StormLake, with filter (uid=dhesse) rlm_ldap: Added the eDirectory password in check items

1 0

RE: cannot return access accept from proxy to client
by Wilson Lie 21 Sep '05

21 Sep '05

Yes, as Host B is used as both proxy and also authentication server depending on the realm received. When host B acts as a authentication server, the [sql] in post-auth is used to log some message for that particular username. When host B acts as a proxy, the [sql] failed as the username from access-accept is missing. Therefore, any method that can avoid the case such that [sql] won't be invoked when host B acts as a proxy ? -----Original Message----- From: Paolo Rotela [mailto:paolo.rotela@bluetelecom.com] Sent: 2005/9/21 [星期三] 下午 08:28 To: FreeRadius users mailing list Cc: Subject: Re: cannot return access accept from proxy to client Seeing your output, it says that it's failing because "post-auth" module is failing due to the fail of the "sql" module invoked. Lookup your radiusd.conf file, and see why you are using sql in post-auth, and see if this setup is correct. ----- Original Message ----- From: Wilson Lie <mailto:wilson.lie@ithlgroup.com> To: freeradius-users(a)lists.freeradius.org Sent: Wednesday, September 21, 2005 5:58 AM Subject: cannot return access accept from proxy to client Hi all, I encountered a problem during authentication request. Would you give me a hand ? Many thanks! Configuration: Host A ( Radius server) Host B ( proxy all requests to host A ) Problem: 1) Access-Request is sent to Host B from client 2) Host B proxy request to Host A 3) Host A sends Access-Accept to Host B 4) Host B receive Access-Accept from Host A 5) Host B sends Access-Reject to client ( log message comes below) *My question is how can I set radius such that it can send the access-accept to client ? ================================================================ rad_recv: Access-Accept packet from host xxx.xxx.xxx.xxx:1812, id=3, length=156 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 3 hints: Matched DEFAULT at 81 modcall[authorize]: module "preprocess" returns ok for request 3 radius_xlat: '/usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/auth-detail-20050921' rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/auth-detail-20050921 modcall[authorize]: module "auth_log" returns ok for request 3 rlm_realm: Proxy reply, or no User-Name. Ignoring. modcall[authorize]: module "suffix" returns noop for request 3 users: Matched entry DEFAULT at line 168 modcall[authorize]: module "files" returns ok for request 3 modcall: group authorize returns ok for request 3 rad_check_password: Found Auth-Type SQL rad_check_password: Auth-Type = Accept, accepting the user Login OK: [99009900@realm/8F4Lf0T] (from client ivrs port 0 cli 00-0C-41-2F-00-71) Processing the post-auth section of radiusd.conf modcall: entering group post-auth for request 3 radius_xlat: '/usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/reply-detail-20050921' rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/reply-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/reply-detail-20050921 modcall[post-auth]: module "reply_log" returns ok for request 3 rlm_sql (sql): Processing sql_postauth radius_xlat: '' modcall[post-auth]: module "sql" returns fail for request 3 modcall: group post-auth returns fail for request 3 Delaying request 3 for 1 seconds Finished request 3 ======================================================================= ___________________________________________________ (c) 2005 Interactive Technology Holdings Limited Group. All rights reserved. CONFIDENTIALITY: This communication and any attachment(s) is intended solely for the person or organisation to which it is addressed and it may be confidential. This communication may contain confidential or legally privileged material and may not be copied, redistributed or published (in whole or in part) without our prior written consent. This communication may have been intercepted, partially destroyed, arrive late, incomplete or contain viruses and no liability is accepted by any member of the Interactive Technology Holdings Limited Group as a result. If you are not the intended recipient, employee or agent responsible for delivering the message to the intended recipient you must not copy, disclose, distribute or take any action in reliance on it. If you have received this communication in error, please immediately reply and highlight the error to the sender immediately and destroy the original from your computer. _____ - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ____________________________________________________________ (c) 2005 Interactive Technology Holdings Limited Group. All rights reserved. CONFIDENTIALITY: This communication and any attachment(s) is intended solely for the person or organisation to which it is addressed and it may be confidential. This communication may contain confidential or legally privileged material and may not be copied, redistributed or published (in whole or in part) without our prior written consent. This communication may have been intercepted, partially destroyed, arrive late, incomplete or contain viruses and no liability is accepted by any member of the Interactive Technology Holdings Limited Group as a result. If you are not the intended recipient, employee or agent responsible for delivering the message to the intended recipient you must not copy, disclose, distribute or take any action in reliance on it. If you have received this communication in error, please immediately reply and highlight the error to the sender immediately and destroy the original from your computer.

2 1

Time based accounting
by Nirmal 21 Sep '05

21 Sep '05

Hi, Is there any way we can time based accounting Input/Output Octets in free radius ? Thanks in Advance Nirmal --------------------------------- Yahoo! for Good Click here to donate to the Hurricane Katrina relief effort.

3 3

cannot return access accept from proxy to client
by Wilson Lie 21 Sep '05

21 Sep '05

Hi all, I encountered a problem during authentication request. Would you give me a hand ? Many thanks! Configuration: Host A ( Radius server) Host B ( proxy all requests to host A ) Problem: 1) Access-Request is sent to Host B from client 2) Host B proxy request to Host A 3) Host A sends Access-Accept to Host B 4) Host B receive Access-Accept from Host A 5) Host B sends Access-Reject to client ( log message comes below) *My question is how can I set radius such that it can send the access-accept to client ? ================================================================ rad_recv: Access-Accept packet from host xxx.xxx.xxx.xxx:1812, id=3, length=156 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 3 hints: Matched DEFAULT at 81 modcall[authorize]: module "preprocess" returns ok for request 3 radius_xlat: '/usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/auth-detail-20050921' rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/auth-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/auth-detail-20050921 modcall[authorize]: module "auth_log" returns ok for request 3 rlm_realm: Proxy reply, or no User-Name. Ignoring. modcall[authorize]: module "suffix" returns noop for request 3 users: Matched entry DEFAULT at line 168 modcall[authorize]: module "files" returns ok for request 3 modcall: group authorize returns ok for request 3 rad_check_password: Found Auth-Type SQL rad_check_password: Auth-Type = Accept, accepting the user Login OK: [99009900@realm/8F4Lf0T] (from client ivrs port 0 cli 00-0C-41-2F-00-71) Processing the post-auth section of radiusd.conf modcall: entering group post-auth for request 3 radius_xlat: '/usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/reply-detail-20050921' rlm_detail: /usr/local/var/log/radius/radacct/%{Client-IP-Address}/reply-detail-%Y%m%d expands to /usr/local/var/log/radius/radacct/xxx.xxx.xxx.xxx/reply-detail-20050921 modcall[post-auth]: module "reply_log" returns ok for request 3 rlm_sql (sql): Processing sql_postauth radius_xlat: '' modcall[post-auth]: module "sql" returns fail for request 3 modcall: group post-auth returns fail for request 3 Delaying request 3 for 1 seconds Finished request 3 ======================================================================= ____________________________________________________________ (c) 2005 Interactive Technology Holdings Limited Group. All rights reserved. CONFIDENTIALITY: This communication and any attachment(s) is intended solely for the person or organisation to which it is addressed and it may be confidential. This communication may contain confidential or legally privileged material and may not be copied, redistributed or published (in whole or in part) without our prior written consent. This communication may have been intercepted, partially destroyed, arrive late, incomplete or contain viruses and no liability is accepted by any member of the Interactive Technology Holdings Limited Group as a result. If you are not the intended recipient, employee or agent responsible for delivering the message to the intended recipient you must not copy, disclose, distribute or take any action in reliance on it. If you have received this communication in error, please immediately reply and highlight the error to the sender immediately and destroy the original from your computer.

2 1

log_badlogins
by Evert Meulie 21 Sep '05

21 Sep '05

Hi all! What kind of logging level/options does the log_badlogins script require? Regards, Evert

1 0

freeradius EAP/PEAP and LDAP
by François Dagorn 21 Sep '05

21 Sep '05

Hello all, I'm trying to configure a secured Wireless network, so I want to use EAP/PEAP/LDAP for authentication and then try WPA to crypt sessions. As a beginner, I'm doing that step by step. So I've done the following : - set up a freeradius server and test it with a simple radius client. That's ok, the LDAP server is called to check authorizations and then authenticate. In this case I can see "Found Auth-Type LDAP" in the radiusd -x logs. - then try using the full stuffs (XP client, Aironet AP, freeradius) ... "Tunneled data is valid" , "Setting User-Name to ...", but unfortunately the process is unable to valid the password , the error is as follows : "rlm_mschap: Told to do MS-CHAPv2 for xxx with NT-PAssword" "FAILED: No NT/LM-Password". In this case before I can see "rad_check_password: Found Auth-Type EAP" looks like LDAP has been forgotten ? Any help would be appreciated ! -- François

3 2

Re: ntlm_auth multiple domains
by Jamie Crawford 20 Sep '05

20 Sep '05

First, Thanks for the help. I solved my own problem in my previous email and didn't realize it. Second, This got it working. change radiusd.conf /usr/bin/ntlm_auth --domain=%{realm} --request-nt-key --username=%{mschap:User-Name} add to proxy.conf realm DOMAINA { type = radius authhost = LOCAL accthost = LOCAL } realm DOMAINB { type = radius authhost = LOCAL accthost = LOCAL } realm DOMAINC { type = radius authhost = LOCAL accthost = LOCAL } >>>aland(a)ox.org 09/20/05 3:54 pm >>> Jamie Crawford <crawford(a)cmsu1.cmsu.edu> wrote: >I'm trying to validate a user from two trusted NT4 domains. I >cannot get ntlm_auth --username=domainb/domainbuser to work. How >are you supposed to validate a user with domain credentials, when >you can't pass along the domain information? I think it's more of a >limitation with ntlm_auth than anything. Have you tried reading the configuration files? There are examples of passing domains to ntlm_auth. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

1 0

Re: ntlm_auth multiple domains
by Jamie Crawford 20 Sep '05

20 Sep '05

I'm trying to validate a user from two trusted NT4 domains. I cannot get ntlm_auth --username=domainb/domainbuser to work. How are you supposed to validate a user with domain credentials, when you can't pass along the domain information? I think it's more of a limitation with ntlm_auth than anything. tia, jamie >>> aland(a)ox.org 9/20/2005 11:45:49 AM >>> "Jamie Crawford" <crawford(a)cmsu1.cmsu.edu> wrote: > When I run ntlm_auth --username=domainauser everything works > great. When I run ntlm_auth --username=domainbuser it fails because > the user does not exist in domaina which the server is joined to. You need to point winbindd to a global catalog server, and then establish trust relationships between the GC and all of the domains. > Would setting up realms help? No. The limitation is due to Active Directory, not realms or FreeRADIUS. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

2 1

Cisco Privilege Level
by Ryan Sharpe 20 Sep '05

20 Sep '05

I finally figured it out. I apologize for my own stupidity. It was a syntax error > CiscoAVPair = "shell:priv-lvl=2" Should be cisco-avpair = "shell:priv-lvl2" -- Ryan Sharpe Junior Technical Analyst LARG*net (519) 661-2111 x86356 http://www.largnet.on.ca

1 0

default ip pools
by Ezequiel O. Block 20 Sep '05

20 Sep '05

Hi Folks, I'm trying to set up default ip pools and it is not working, if i set "Pool-Name :=" to any of the pools defined on radiusd.conf then it does work, but if i set Pool-Name := DEFAULT then the server doesn't send Framed-Ip-Address as expected. I did some searches on this list and found some posts where the "default" feature were not available on earlier versions of FreeRadius. I'm working in freeradius-1.0.5 compiled from sources, does this version have this feature? Any clue? These lines are from radiusd.conf ... ippool tasa1 { range-start = a.b.c.30 range-stop = a.b.c.40 netmask = 255.255.255.0 cache-size = 800 session-db = ${raddbdir}/dbtasa1.ippool ip-index = ${raddbdir}/dbtasa1.ipindex override = no maximum-timeout = 0 } ippool teco1 { range-start = a.b.d.150 range-stop = a.b.d.160 netmask = 255.255.255.0 cache-size = 800 session-db = ${raddbdir}/dbteco1.ippool ip-index = ${raddbdir}/dbteco1.ipindex override = no maximum-timeout = 0 } Thanks in advance. Ezequiel. Cooperativa La Lonja.

1 0