- Freeradius-Users - lists.freeradius.org

authing clients - Debug Mode !!!!
by emerson 26 May '06

26 May '06

Pessoal, i have a server linux running slackware 10.1, with freeradius 1.1.1 with auth eap/tls/ttls + openssl-0.97d + mysql. My freeradius client is a ap wl-5460AP. When i try to authenticate any user on my freeradius, in debug MODE appear this messages: I'm can not to stabilished connections..... Message-Authenticator = 0x59373d130f801019b116e042690ff3e1 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 2 modcall[authorize]: module "preprocess" returns ok for request 2 rlm_eap: EAP packet type response id 2 length 106 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 2 radius_xlat: 'mobile' rlm_sql (sql): sql_set_user escaped user --> 'mobile' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radcheck WHERE Username = 'mobile' ORDER BY id' rlm_sql (sql): Reserving sql socket id: 2 radius_xlat: 'SELECT radgroupcheck.id,radgroupcheck.GroupName,radgroupcheck.Attribute,radgroupcheck.Value,radgroupcheck.op FROM radgroupcheck,usergroup WHERE usergroup.Username = 'mobile' AND usergroup.GroupName = radgroupcheck.GroupName ORDER BY radgroupcheck.id' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radreply WHERE Username = 'mobile' ORDER BY id' radius_xlat: 'SELECT radgroupreply.id,radgroupreply.GroupName,radgroupreply.Attribute,radgroupreply.Value,radgroupreply.op FROM radgroupreply,usergroup WHERE usergroup.Username = 'mobile' AND usergroup.GroupName = radgroupreply.GroupName ORDER BY radgroupreply.id' rlm_sql (sql): Released sql socket id: 2 modcall[authorize]: module "sql" returns ok for request 2 modcall: leaving group authorize (returns updated) for request 2 rad_check_password: Found Auth-Type EAP auth: type "EAP" Processing the authenticate section of radiusd.conf modcall: entering group authenticate for request 2 rlm_eap: Request found, released from the list rlm_eap: EAP/tls rlm_eap: processing type tls rlm_eap_tls: Authenticate rlm_eap_tls: processing TLS rlm_eap_tls: Length Included eaptls_verify returned 11 (other): before/accept initialization TLS_accept: before/accept initialization rlm_eap_tls: <<< TLS 1.0 Handshake [length 005b], ClientHello TLS_accept: SSLv3 read client hello A rlm_eap_tls: >>> TLS 1.0 Handshake [length 004a], ServerHello TLS_accept: SSLv3 write server hello A rlm_eap_tls: >>> TLS 1.0 Handshake [length 0694], Certificate TLS_accept: SSLv3 write certificate A rlm_eap_tls: >>> TLS 1.0 Handshake [length 00b1], CertificateRequest TLS_accept: SSLv3 write certificate request A TLS_accept: SSLv3 flush data TLS_accept:error in SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode eaptls_process returned 13 modcall[authenticate]: module "eap" returns handled for request 2 modcall: leaving group authenticate (returns handled) for request 2 Sending Access-Challenge of id 112 to 10.254.0.2 port 2048 Password == "teste" Framed-Protocol := PPP EAP-Message = 0x0103040a0dc00000079e160301004a020000460301447767ef3e6132404c0c6c02a315774554397970ac027074a9f45e5248c032e820822e232b79be2b75ef379cf751e7d12d6b25d4b841b1c2655efa85382cc1e66000350016030106940b00069000068d0002cd308202c930820232a003020102020102300d06092a864886f70d010104050030819f310b30090603550406130243413111300f0603550408130850726f76696e63653112301006035504071309536f6d65204369747931153013060355040a130c4f7267616e697a6174696f6e31123010060355040b13096c6f63616c686f7374311b301906035504031312436c69656e74206365 EAP-Message = 0x7274696669636174653121301f06092a864886f70d0109011612636c69656e74406578616d706c652e636f6d301e170d3034303132353133323631305a170d3035303132343133323631305a30819b310b30090603550406130243413111300f0603550408130850726f76696e63653112301006035504071309536f6d65204369747931153013060355040a130c4f7267616e697a6174696f6e31123010060355040b13096c6f63616c686f73743119301706035504031310526f6f74206365727469666963617465311f301d06092a864886f70d0109011610726f6f74406578616d706c652e636f6d30819f300d06092a864886f70d010101050003 EAP-Message = 0x818d0030818902818100dac525422bfedb082629a2cba44b3449c90d0ab462fb72c8434a782098863d7eb7d7e70028c2b7ad555a51cc756cf4fa1d7091615ab450d5289553ae6616aff014a55085d6b8fb4aee98638e426175cdd36c665c63cda177d34920eb30585edc8773999c2980f81ad4638bbbea1c82d054023db7ef24a3ec1c3f6241a903d7f30203010001a317301530130603551d25040c300a06082b06010505070301300d06092a864886f70d0101040500038181007a2d921b1cf13bf2982a9178ec9ede6d88edc178a2e8bd40a0a06fb6f0769957884cd7084537083496fd184165293f583c8e8240eb68e042c94b15752e4c07e80d09 EAP-Message = 0x779afa3dd55c24fa54ac292d77205d1c2477ed30d59f57caf9bd21ff2a8d16cc0911c50e4f295763fcb60efa3c3d2d0e43850f6e6fbe284902f6e83503650003ba308203b63082031fa003020102020100300d06092a864886f70d010104050030819f310b30090603550406130243413111300f0603550408130850726f76696e63653112301006035504071309536f6d65204369747931153013060355040a130c4f7267616e697a6174696f6e31123010060355040b13096c6f63616c686f7374311b301906035504031312436c69656e742063657274696669636174653121301f06092a864886f70d0109011612636c69656e74406578616d706c EAP-Message = 0x652e636f6d301e170d3034303132353133323630375a Message-Authenticator = 0x00000000000000000000000000000000 State = 0xcbde73c73ebd72307d8bcd5336508bf1 Finished request 2 Going to the next request Thread 3 waiting to be assigned a request rad_recv: Access-Request packet from host 10.254.0.2:2048, id=113, length=176 Waking up in 31 seconds... Thread 4 got semaphore Thread 4 handling request 3, (1 handled so far) User-Name = "mobile" NAS-IP-Address = 10.254.0.2 NAS-Port = 0 Called-Station-Id = "004f6207b40c" Calling-Station-Id = "0014a53c478d" NAS-Identifier = "Realtek Access Point. 8181" NAS-Port-Type = Wireless-802.11 Service-Type = Framed-User Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x020300060d00 State = 0xcbde73c73ebd72307d8bcd5336508bf1 Message-Authenticator = 0xf8b549edcba04ccf14c3a35cd5e00886 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 3 modcall[authorize]: module "preprocess" returns ok for request 3 rlm_eap: EAP packet type response id 3 length 6 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 3 radius_xlat: 'mobile' rlm_sql (sql): sql_set_user escaped user --> 'mobile' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radcheck WHERE Username = 'mobile' ORDER BY id' rlm_sql (sql): Reserving sql socket id: 1 radius_xlat: 'SELECT radgroupcheck.id,radgroupcheck.GroupName,radgroupcheck.Attribute,radgroupcheck.Value,radgroupcheck.op FROM radgroupcheck,usergroup WHERE usergroup.Username = 'mobile' AND usergroup.GroupName = radgroupcheck.GroupName ORDER BY radgroupcheck.id' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radreply WHERE Username = 'mobile' ORDER BY id' radius_xlat: 'SELECT radgroupreply.id,radgroupreply.GroupName,radgroupreply.Attribute,radgroupreply.Value,radgroupreply.op FROM radgroupreply,usergroup WHERE usergroup.Username = 'mobile' AND usergroup.GroupName = radgroupreply.GroupName ORDER BY radgroupreply.id' rlm_sql (sql): Released sql socket id: 1 modcall[authorize]: module "sql" returns ok for request 3 modcall: leaving 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/tls rlm_eap: processing type tls rlm_eap_tls: Authenticate rlm_eap_tls: processing TLS rlm_eap_tls: Received EAP-TLS ACK message rlm_eap_tls: ack handshake fragment handler eaptls_verify returned 1 eaptls_process returned 13 modcall[authenticate]: module "eap" returns handled for request 3 modcall: leaving group authenticate (returns handled) for request 3 Sending Access-Challenge of id 113 to 10.254.0.2 port 2048 Password == "teste" Framed-Protocol := PPP EAP-Message = 0x010403a80d800000079e170d3036303132343133323630375a30819f310b30090603550406130243413111300f0603550408130850726f76696e63653112301006035504071309536f6d65204369747931153013060355040a130c4f7267616e697a6174696f6e31123010060355040b13096c6f63616c686f7374311b301906035504031312436c69656e742063657274696669636174653121301f06092a864886f70d0109011612636c69656e74406578616d706c652e636f6d30819f300d06092a864886f70d010101050003818d0030818902818100d4c5b19724f164acf1ffb189db1c8fbff4f14396ea7cb1e90f78d69451725377895dfe52cc EAP-Message = 0xb99b41e80ddeb58b127a943f4f58cbc562878192fbdc6fece9f871e7c130d35cf5188817e9b133249edd2a1c75d31043ae87553cec7a77ef26aa7d74281db9b77e17c6446c5dd9b188b43250ca0229963722a123a726b00b4027fd0203010001a381ff3081fc301d0603551d0e0416041468d36d3e1ee7bc9d5a057021c363da1365d1ade33081cc0603551d230481c43081c1801468d36d3e1ee7bc9d5a057021c363da1365d1ade3a181a5a481a230819f310b30090603550406130243413111300f0603550408130850726f76696e63653112301006035504071309536f6d65204369747931153013060355040a130c4f7267616e697a6174696f6e EAP-Message = 0x31123010060355040b13096c6f63616c686f7374311b301906035504031312436c69656e742063657274696669636174653121301f06092a864886f70d0109011612636c69656e74406578616d706c652e636f6d820100300c0603551d13040530030101ff300d06092a864886f70d01010405000381810033c00b66b1e579ef73a06798252dab8d5e5511fc00fd276d80d12f834777c6743fdc2743fca1507704e4bc0979e4f60ac3ad9ee83e6f347369229d1f77229ba2e982359da563024a00163dba6d6c986c0bad28af85132ff8f0d76501bf1b7c2dff658ce1e62c01997b6e64e3e8d4373354ce9912847651539063b85bbc5485c516030100b1 EAP-Message = 0x0d0000a902010200a400a230819f310b30090603550406130243413111300f0603550408130850726f76696e63653112301006035504071309536f6d65204369747931153013060355040a130c4f7267616e697a6174696f6e31123010060355040b13096c6f63616c686f7374311b301906035504031312436c69656e742063657274696669636174653121301f06092a864886f70d0109011612636c69656e74406578616d706c652e636f6d0e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0x125b8a5ad0f76e326bbc4e2087260bbe Finished request 3 Going to the next request Thread 4 waiting to be assigned a request rad_recv: Access-Request packet from host 10.254.0.2:2048, id=114, length=187 Waking up in 31 seconds... Thread 5 got semaphore Thread 5 handling request 4, (1 handled so far) User-Name = "mobile" NAS-IP-Address = 10.254.0.2 NAS-Port = 0 Called-Station-Id = "004f6207b40c" Calling-Station-Id = "0014a53c478d" NAS-Identifier = "Realtek Access Point. 8181" NAS-Port-Type = Wireless-802.11 Service-Type = Framed-User Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x020400110d800000000715030100020230 State = 0x125b8a5ad0f76e326bbc4e2087260bbe Message-Authenticator = 0x1c5b117a3ea7e7026abb5ec89890adc2 Processing the authorize section of radiusd.conf modcall: entering group authorize for request 4 modcall[authorize]: module "preprocess" returns ok for request 4 rlm_eap: EAP packet type response id 4 length 17 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 4 radius_xlat: 'mobile' rlm_sql (sql): sql_set_user escaped user --> 'mobile' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radcheck WHERE Username = 'mobile' ORDER BY id' rlm_sql (sql): Reserving sql socket id: 0 radius_xlat: 'SELECT radgroupcheck.id,radgroupcheck.GroupName,radgroupcheck.Attribute,radgroupcheck.Value,radgroupcheck.op FROM radgroupcheck,usergroup WHERE usergroup.Username = 'mobile' AND usergroup.GroupName = radgroupcheck.GroupName ORDER BY radgroupcheck.id' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radreply WHERE Username = 'mobile' ORDER BY id' radius_xlat: 'SELECT radgroupreply.id,radgroupreply.GroupName,radgroupreply.Attribute,radgroupreply.Value,radgroupreply.op FROM radgroupreply,usergroup WHERE usergroup.Username = 'mobile' AND usergroup.GroupName = radgroupreply.GroupName ORDER BY radgroupreply.id' rlm_sql (sql): Released sql socket id: 0 modcall[authorize]: module "sql" returns ok for request 4 modcall: leaving 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/tls rlm_eap: processing type tls rlm_eap_tls: Authenticate rlm_eap_tls: processing TLS rlm_eap_tls: Length Included eaptls_verify returned 11 rlm_eap_tls: <<< TLS 1.0 Alert [length 0002], fatal unknown_ca TLS Alert read:fatal:unknown CA TLS_accept:failed in SSLv3 read client certificate A 22289:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:s3_pkt.c:1052:SSL alert number 48 22289:error:140940E5:SSL routines:SSL3_READ_BYTES:ssl handshake failure:s3_pkt.c:837: rlm_eap_tls: SSL_read failed in a system call (-1), TLS session fails. In SSL Handshake Phase In SSL Accept mode rlm_eap_tls: BIO_read failed in a system call (-1), TLS session fails. eaptls_process returned 13 rlm_eap: Freeing handler modcall[authenticate]: module "eap" returns reject for request 4 modcall: leaving group authenticate (returns reject) for request 4 auth: Failed to validate the user. Login incorrect: [mobile/<no User-Password attribute>] (from client mslink-radius port 0 cli 0014a53c478d) Delaying request 4 for 1 seconds Finished request 4 Going to the next request Thread 5 waiting to be assigned a request --- Walking the entire request list --- Cleaning up request 0 ID 110 with timestamp 447767ef Cleaning up request 1 ID 111 with timestamp 447767ef Cleaning up request 2 ID 112 with timestamp 447767ef Cleaning up request 3 ID 113 with timestamp 447767ef Sending Access-Reject of id 114 to 10.254.0.2 port 2048 EAP-Message = 0x04040004 Message-Authenticator = 0x00000000000000000000000000000000 Cleaning up request 4 ID 114 with timestamp 447767ef Nothing to do. Sleeping until we see a request.

2 1

authing clients - Debug Mode - More Output!!!!
by emerson 26 May '06

26 May '06

Ready to process requests. rad_recv: Access-Request packet from host 10.254.0.2:2048, id=115, length=165 --- Walking the entire request list --- Waking up in 31 seconds... Threads: total/active/spare threads = 5/0/5 Thread 1 got semaphore Thread 1 handling request 0, (1 handled so far) User-Name = "joao" NAS-IP-Address = 10.254.0.2 NAS-Port = 0 Called-Station-Id = "004f6207b40c" Calling-Station-Id = "0014a53c478d" NAS-Identifier = "Realtek Access Point. 8181" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 Service-Type = Framed-User Connect-Info = "CONNECT 11Mbps 802.11b" EAP-Message = 0x02000009016a6f616f Message-Authenticator = 0xdcc560812d6c0bad0bc665744157e53a Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 rlm_eap: EAP packet type response id 0 length 9 rlm_eap: No EAP Start, assuming it's an on-going EAP conversation modcall[authorize]: module "eap" returns updated for request 0 radius_xlat: 'joao' rlm_sql (sql): sql_set_user escaped user --> 'joao' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radcheck WHERE Username = 'joao' ORDER BY id' rlm_sql (sql): Reserving sql socket id: 4 radius_xlat: 'SELECT radgroupcheck.id,radgroupcheck.GroupName,radgroupcheck.Attribute,radgroupcheck.Value,radgroupcheck.op FROM radgroupcheck,usergroup WHERE usergroup.Username = 'joao' AND usergroup.GroupName = radgroupcheck.GroupName ORDER BY radgroupcheck.id' radius_xlat: 'SELECT id, UserName, Attribute, Value, op FROM radreply WHERE Username = 'joao' ORDER BY id' radius_xlat: 'SELECT radgroupreply.id,radgroupreply.GroupName,radgroupreply.Attribute,radgroupreply.Value,radgroupreply.op FROM radgroupreply,usergroup WHERE usergroup.Username = 'joao' AND usergroup.GroupName = radgroupreply.GroupName ORDER BY radgroupreply.id' rlm_sql (sql): Released sql socket id: 4 modcall[authorize]: module "sql" returns ok for request 0 modcall: leaving group authorize (returns updated) for request 0 rad_check_password: Found Auth-Type Local auth: type Local auth: No User-Password or CHAP-Password attribute in the request auth: Failed to validate the user. Login incorrect: [joao/<no User-Password attribute>] (from client mslink-radius port 0 cli 0014a53c478d) Delaying request 0 for 1 seconds Finished request 0

1 0

May be of interest to some (or many)?
by Laker Netman 26 May '06

26 May '06

I found these two links while digging for something else. They are both pertinent to [free]RADIUS and someone may find them useful for their environment: http://www.pgina.org/ https://wpsynch.dev.java.net/ Cheers, Laker __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

802.11 AP Access-Accept problem
by Drew Linsalata 26 May '06

26 May '06

We have a working freeradius install authenticating clients via a Proxim/Orinoco AP-700 access point. The AP is configured to do EAP authentication via the radius server. No problem with that. Freeradius is authenticating users as per our requirements, and is and sending Access-Accept to the AP. rad_recv: Access-Request packet from host W.X.Y.Z:6001, id=3, length=154 User-Name = "testuser" NAS-IP-Address = W.X.Y.Z Called-Station-Id = "00-20-a6-5d-9c-d1:ourSSID" Calling-Station-Id = "00-06-25-2f-8c-4e" NAS-Identifier = "ORiNOCO-AP-700-5d-9c-d1" Framed-MTU = 1400 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0204000c01746573746f6e65 Message-Authenticator = 0x75e8339aab77b394dab2beef5e9228dd Sending Access-Accept of id 3 to W.X.Y.Z port 6001 Problem is, the AP isn't getting the accepts. The EAP request counter increments on the AP when we attempt a connection. The EAP reject counter increments on the AP when we connect with bad credentials. The EAP accept counter never increments even with successful authentication. The Windows client is left in "Validating Identity" state. -- Drew Linsalata The Gotham Bus Company, Inc. Dedicated Servers and Colocation Solutions Long Island, New York http://www.gothambus.com

2 2

dict_addvalue: Duplicate value name
by Alan 26 May '06

26 May '06

I am trying to compile Freeradius Version 1.1.0 on a Sunfire 20z running RH3 enterprise 3 (AMD x86_64 Architecture). I am stumped in result of many errors I cannot find a fix for. Are there any special environment configurations or compile options to use before compiling FreeRadius on a 64 bit machine? Please advise. ~Alan dict_addvalue: Duplicate value name Route-IPX-No for attribute X-Ascend Route-IPX dict_addvalue: Duplicate value name Local for attribute Post-Auth-Type dict_addvalue: Duplicate value name PAP for attribute Auth-Type dict_addvalue: Duplicate value name LAC-Only for attribute Tunnel-Function dict_addvalue: Duplicate value name unix for attribute Auth-Type dict_addvalue: Duplicate value name MS-CHAP for attribute Auth-Type

2 3

authing clients !!!
by emerson 26 May '06

26 May '06

Pessoal, i have a server linux running slackware 10.1, with freeradius 1.1.1 with auth eap/tls/ttls + openssl-0.97d + mysql. My freeradius client is a ap wl-5460AP. When i try to authenticate any user on my freeradius, in logs appear this messages: Fri May 26 09:06:07 2006 : Info: rlm_sql_mysql: Starting connect to MySQL server for #4 Fri May 26 09:06:07 2006 : Info: Ready to process requests. Fri May 26 09:10:56 2006 : Info: rlm_eap_md5: Issuing Challenge Fri May 26 09:10:56 2006 : Error: TLS_accept:error in SSLv3 read client certificate A Fri May 26 09:10:56 2006 : Error: TLS Alert read:fatal:unknown CA Fri May 26 09:10:56 2006 : Error: TLS_accept:failed in SSLv3 read client certificate A Fri May 26 09:10:56 2006 : Error: rlm_eap_tls: SSL_read failed in a system call (-1), TLS session fails. Fri May 26 09:10:56 2006 : Error: rlm_eap_tls: BIO_read failed in a system call (-1), TLS session fails. Fri May 26 09:10:56 2006 : Auth: Login incorrect: [mobile/<no User-Password attribute>] (from client mslink-radius port 0 cli 0014a53c478d) Fri May 26 09:35:44 2006 : Auth: Login incorrect: [joao/<no User-Password attribute>] (from client mslink-radius port 0 cli 0014a53c478d) what it can be ? thanks... Emerson

2 1

Blank Password and Recommeded RFC standard
by Craig T. Hancock 26 May '06

26 May '06

Question, The RFC seems to have a provision on how to handle a Radius request with a blank password. As an option the Radius Server can send a request back to a client to stating that a password is needed enter password. However what I am trying to figure out is that is this a requirement of a the RFC or a recommendation. Thanks -- ****************************************************** Craig T. Hancock Systems Engineer, Infrastructure Services Office of Information Technology University of Notre Dame ******************************************************

2 3

Inserting Cisco AVPairs from accounting request into database
by vignesh 26 May '06

26 May '06

Hello all I want to insert cisco AV Pairs from accounting request packet into database. Here is the accounting request packet for a single leg. Acct-Session-Id = "00000B93" Calling-Station-Id = "216" Called-Station-Id = "9833515315" Cisco-AVPair = "call-id=19421006761822000202723(a)202.80.61.42" h323-setup-time = "h323-setup-time=*14:42:31.708 PCTime Fri May 26 2006" h323-conf-id = "h323-conf-id=989CA2C5 EBCE11DA 81EF9672 750B1B97" h323-call-type = "h323-call-type=VoIP" Cisco-AVPair = "h323-incoming-conf-id=989CA2C5 EBCE11DA 81EF9672 750B1B97" Cisco-AVPair = "session-protocol=sipv2" h323-connect-time = "h323-connect-time=*14:42:34.904 PCTime Fri May 26 2006" Acct-Session-Time = 4 h323-disconnect-time = "h323-disconnect-time=*14:42:39.020 PCTime Fri May 26 2006" h323-disconnect-cause = "h323-disconnect-cause=10" h323-remote-address = "h323-remote-address=202.80.61.42" h323-voice-quality = "h323-voice-quality=0" Cisco-AVPair = "remote-media-address=202.80.61.42" Cisco-AVPair = "gw-rxd-cgn=ton:0,npi:0,pi:0,si:0,#:216" User-Name = "202.80.61.42" Acct-Status-Type = Stop Service-Type = Login-User NAS-IP-Address = 202.80.61.1 Acct-Delay-Time = 0 I changed the default table structure to include the extra columns. Also made changes in sql.conf to add values in the respective columns. Here is my problem. I insert h323-remote-address by adding '%{h323-remote-address}' in the insert query But I get the value as h323-remote-address=202.80.61.42 whereas I wanted only the ip address not the complete string after the '=' sign. Also I want to insert other fields like callid, remote-media-address both of which are Cisco AVPair. So how do I include them into my database coz I cant refer them direcly by their attribute name like '%{remote-media-address}. I tried that but it doesn't return any value. So how do I insert all these values. Thanks Vignesh

1 0

mysql issue
by andy 26 May '06

26 May '06

Hi list, Fairly new to freeradius, just about to deploy a solution involving RedBack with data storage on the backend using MySQL. I am using NDBD MySQL clustering on the backend and I see the following error from FreeRadius: rlm_sql_mysql: MYSQL check_error: 2006, returning SQL_DOWN This seems to relate to a timeout issue but googling doesnt provide any answers for that specific error code. (too like the date 2006 I expect). I have fairly tweaked the mysql backend to be fairly resilant in a heavy load situation, and none of the other applications running against this cluster seem to have issues. I was wondering if anyone could enlighten me as to how to fix this error, or what threshholds would be recomended for running in this environment? It seems that when this error occurs, for the next few auth attempts, certain attributes are not passed back to the redback. This specifically being IP-Interface. any clues on this issue would be greatly appreciated. thanks -- andy andy(a)shady.org ----------------------------------------------- Never argue with an idiot. They drag you down to their level, then beat you with experience. -----------------------------------------------

4 6

Undefined symbol "cbtls_password"
by Mario Alberto Cruz Gartner 25 May '06

25 May '06

Hello! I'm installing Freeradius1.1.1 on a FreeBSD 4.11-RELEASE-p8 (from the ports system). I'm installing EAP/TLS support (with a mysql backend). The basic setup (and mysql) works fine. The EAP/TLS part it's the one witrh the problem that i have. I'd put the certs on their location, change the eap.conf to reflect this locations and try to start the server. I would thank any help that you can give to me so i can see where the problem lives ;) I'd tried making a pasword-less and a password-protected certificate for the server, but anyway the "cbtls_password" came on. I'm reading about and think that maybe the OpenSSL (OpenSSL 0.9.7d 17 Mar 2004) installation was getting the conflicts, but i reinstalled (both, the OpenSSL and Freeradius) and the problem persists. Again, thanks a lot guys! ----- BEGIN SERVER OUTPUT ----- [1451]virtuse03-{~}# /usr/local/sbin/radiusd -X Starting - reading configuration files ... reread_config: reading radiusd.conf Config: including file: /usr/local/etc/raddb/clients.conf Config: including file: /usr/local/etc/raddb/eap.conf Config: including file: /usr/local/etc/raddb/sql.conf main: prefix = "/usr/local" main: localstatedir = "/var" main: logdir = "/var/log" main: libdir = "/usr/local/lib" main: radacctdir = "/var/log/radacct" main: hostname_lookups = no main: max_request_time = 30 main: cleanup_delay = 5 main: max_requests = 1024 main: delete_blocked_requests = 0 main: port = 0 main: allow_core_dumps = no main: log_stripped_names = no main: log_file = "/var/log/radius.log" main: log_auth = no main: log_auth_badpass = no main: log_auth_goodpass = no main: pidfile = "/var/run/radiusd/radiusd.pid" main: user = "(null)" main: group = "(null)" main: usercollide = no main: lower_user = "no" main: lower_pass = "no" main: nospace_user = "no" main: nospace_pass = "no" main: checkrad = "/usr/local/sbin/checkrad" main: proxy_requests = no security: max_attributes = 200 security: reject_delay = 1 security: status_server = no main: debug_level = 0 read_config_files: reading dictionary read_config_files: reading naslist read_config_files: reading clients read_config_files: reading realms radiusd: entering modules setup Module: Library search path is /usr/local/lib Module: Loaded exec exec: wait = yes exec: program = "(null)" exec: input_pairs = "request" exec: output_pairs = "(null)" exec: packet_type = "(null)" rlm_exec: Wait=yes but no output defined. Did you mean output=none? Module: Instantiated exec (exec) Module: Loaded expr Module: Instantiated expr (expr) Module: Loaded MS-CHAP mschap: use_mppe = yes mschap: require_encryption = no mschap: require_strong = no mschap: with_ntdomain_hack = no mschap: passwd = "(null)" mschap: authtype = "MS-CHAP" mschap: ntlm_auth = "(null)" Module: Instantiated mschap (mschap) Module: Loaded eap eap: default_eap_type = "peap" eap: timer_expire = 60 eap: ignore_unknown_eap_types = no eap: cisco_accounting_username_bug = no rlm_eap: Failed to link EAP-Type/tls: /usr/local/lib/rlm_eap_tls-1.1.1.so: Undefined symbol "cbtls_password" radiusd.conf[9]: eap: Module instantiation failed. radiusd.conf[1893] Unknown module "eap". radiusd.conf[1840] Failed to parse authenticate section. ----- END SERVER OUTPUT ----- ----- BEGIN EAP FILE----- [1454]virtuse03-{~}# cat /usr/local/etc/raddb/eap.conf # # Whatever you do, do NOT set 'Auth-Type := EAP'. The server # is smart enough to figure this out on its own. The most # common side effect of setting 'Auth-Type := EAP' is that the # users then cannot use ANY other authentication method. # # $Id: eap.conf,v 1.4 2004/04/15 18:34:41 aland Exp $ # eap { # Invoke the default supported EAP type when # EAP-Identity response is received. # # The incoming EAP messages DO NOT specify which EAP # type they will be using, so it MUST be set here. # # For now, only one default EAP type may be used at a time. # # If the EAP-Type attribute is set by another module, # then that EAP type takes precedence over the # default type configured here. # default_eap_type = peap # A list is maintained to correlate EAP-Response # packets with EAP-Request packets. After a # configurable length of time, entries in the list # expire, and are deleted. # timer_expire = 60 # There are many EAP types, but the server has support # for only a limited subset. If the server receives # a request for an EAP type it does not support, then # it normally rejects the request. By setting this # configuration to "yes", you can tell the server to # instead keep processing the request. Another module # MUST then be configured to proxy the request to # another RADIUS server which supports that EAP type. # # If another module is NOT configured to handle the # request, then the request will still end up being # rejected. ignore_unknown_eap_types = no # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given # a User-Name attribute in an Access-Accept, it copies one # more byte than it should. # # We can work around it by configurably adding an extra # zero byte. cisco_accounting_username_bug = no # Supported EAP-types # # We do NOT recommend using EAP-MD5 authentication # for wireless connections. It is insecure, and does # not provide for dynamic WEP keys. # #md5 { #} # Cisco LEAP # # We do not recommend using LEAP in new deployments. See: # http://www.securiteam.com/tools/5TP012ACKE.html # # Cisco LEAP uses the MS-CHAP algorithm (but not # the MS-CHAP attributes) to perform it's authentication. # # As a result, LEAP *requires* access to the plain-text # User-Password, or the NT-Password attributes. # 'System' authentication is impossible with LEAP. # #leap { #} # Generic Token Card. # # Currently, this is only permitted inside of EAP-TTLS, # or EAP-PEAP. The module "challenges" the user with # text, and the response from the user is taken to be # the User-Password. # # Proxying the tunneled EAP-GTC session is a bad idea, # the users password will go over the wire in plain-text, # for anyone to see. # #gtc { # The default challenge, which many clients # ignore.. #challenge = "Password: " # The plain-text response which comes back # is put into a User-Password attribute, # and passed to another module for # authentication. This allows the EAP-GTC # response to be checked against plain-text, # or crypt'd passwords. # # If you say "Local" instead of "PAP", then # the module will look for a User-Password # configured for the request, and do the # authentication itself. # #auth_type = PAP #} ## EAP-TLS # # To generate ctest certificates, run the script # # ../scripts/certs.sh # # The documents on http://www.freeradius.org/doc # are old, but may be helpful. # # See also: # # http://www.dslreports.com/forum/remark,9286052~mode=flat # tls { private_key_password = whatever private_key_file = ${raddbdir}/certs/tls/cert-srv.pem # If Private key & Certificate are located in # the same file, then private_key_file & # certificate_file must contain the same file # name. certificate_file = ${raddbdir}/certs/tls/cert-srv.pem # Trusted Root CA list CA_file = ${raddbdir}/certs/tls/CA/cacert.pem dh_file = ${raddbdir}/certs/tls/dh random_file = ${raddbdir}/certs/tls/random # # This can never exceed the size of a RADIUS # packet (4096 bytes), and is preferably half # that, to accomodate other attributes in # RADIUS packet. On most APs the MAX packet # length is configured between 1500 - 1600 # In these cases, fragment size should be # 1024 or less. # fragment_size = 1024 # include_length is a flag which is # by default set to yes If set to # yes, Total Length of the message is # included in EVERY packet we send. # If set to no, Total Length of the # message is included ONLY in the # First packet of a fragment series. # include_length = yes # Check the Certificate Revocation List # # 1) Copy CA certificates and CRLs to same directory. # 2) Execute 'c_rehash <CA certs&CRLs Directory>'. # 'c_rehash' is OpenSSL's command. # 3) Add 'CA_path=<CA certs&CRLs directory>' # to radiusd.conf's tls section. # 4) uncomment the line below. # 5) Restart radiusd # check_crl = yes # # If check_cert_cn is set, the value will # be xlat'ed and checked against the CN # in the client certificate. If the values # do not match, the certificate verification # will fail rejecting the user. # # check_cert_cn = %{User-Name} } # The TTLS module implements the EAP-TTLS protocol, # which can be described as EAP inside of Diameter, # inside of TLS, inside of EAP, inside of RADIUS... # # Surprisingly, it works quite well. # # The TTLS module needs the TLS module to be installed # and configured, in order to use the TLS tunnel # inside of the EAP packet. You will still need to # configure the TLS module, even if you do not want # to deploy EAP-TLS in your network. Users will not # be able to request EAP-TLS, as it requires them to # have a client certificate. EAP-TTLS does not # require a client certificate. # #ttls { # The tunneled EAP session needs a default # EAP type which is separate from the one for # the non-tunneled EAP module. Inside of the # TTLS tunnel, we recommend using EAP-MD5. # If the request does not contain an EAP # conversation, then this configuration entry # is ignored. #default_eap_type = md5 #default_eap_type = mschapv2 # The tunneled authentication request does # not usually contain useful attributes # like 'Calling-Station-Id', etc. These # attributes are outside of the tunnel, # and normally unavailable to the tunneled # authentication request. # # By setting this configuration entry to # 'yes', any attribute which NOT in the # tunneled authentication request, but # which IS available outside of the tunnel, # is copied to the tunneled request. # # allowed values: {no, yes} #copy_request_to_tunnel = yes # The reply attributes sent to the NAS are # usually based on the name of the user # 'outside' of the tunnel (usually # 'anonymous'). If you want to send the # reply attributes based on the user name # inside of the tunnel, then set this # configuration entry to 'yes', and the reply # to the NAS will be taken from the reply to # the tunneled request. # # allowed values: {no, yes} #use_tunneled_reply = yes #} # # The tunneled EAP session needs a default EAP type # which is separate from the one for the non-tunneled # EAP module. Inside of the TLS/PEAP tunnel, we # recommend using EAP-MS-CHAPv2. # # The PEAP module needs the TLS module to be installed # and configured, in order to use the TLS tunnel # inside of the EAP packet. You will still need to # configure the TLS module, even if you do not want # to deploy EAP-TLS in your network. Users will not # be able to request EAP-TLS, as it requires them to # have a client certificate. EAP-PEAP does not # require a client certificate. # peap { #The tunneled EAP session needs a default #EAP type which is separate from the one for #the non-tunneled EAP module. Inside of the #PEAP tunnel, we recommend using MS-CHAPv2, #as that is the default type supported by #Windows clients. default_eap_type = mschapv2 copy_request_to_tunnel = no } # # This takes no configuration. # # Note that it is the EAP MS-CHAPv2 sub-module, not # the main 'mschap' module. # # Note also that in order for this sub-module to work, # the main 'mschap' module MUST ALSO be configured. # # This module is the *Microsoft* implementation of MS-CHAPv2 # in EAP. There is another (incompatible) implementation # of MS-CHAPv2 in EAP by Cisco, which FreeRADIUS does not # currently support. # mschapv2 { } } [1455]virtuse03-{~}# ----- END EAP FILE----- -- Mario Alberto Cruz Gartner mario.cruz(a)gmail.com

1 0