- Freeradius-Users - lists.freeradius.org

eap peap
by Daniel Romero 29 Nov '06

29 Nov '06

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 tls: rsa_key_exchange = no tls: dh_key_exchange = yes tls: rsa_key_length = 512 tls: dh_key_length = 512 tls: verify_depth = 0 tls: CA_path = "(null)" tls: pem_file_type = yes tls: private_key_file = "/usr/local/etc/raddb/certs/cert- srv.pem" tls: certificate_file = "(null)" tls: CA_file = "/usr/local/etc/raddb/certs/demoCA/cacert.pem" tls: private_key_password = "radiusUDP" tls: dh_file = "/usr/local/etc/raddb/certs/dh" tls: random_file = "/usr/local/etc/raddb/certs/random" tls: fragment_size = 1024 tls: include_length = yes tls: check_crl = yes tls: check_cert_cn = "(null)" tls: cipher_list = "(null)" tls: check_cert_issuer = "(null)" rlm_eap_tls: Loading the certificate file as a chain rlm_eap: SSL error error:0200100E:system library:fopen:Bad address rlm_eap_tls: Error reading certificate file rlm_eap: Failed to initialize type tls radiusd.conf[1]: eap: Module instantiation failed. radiusd.conf[399] Unknown module "eap". radiusd.conf[382] Failed to parse authenticate section. any ideas??? certificates created with certs.sh radius:/home/dromero/radius/freeradius-1.1.3/scripts# sh certs.sh Generating DH parameters, 512 bit long safe prime, generator 2 This is going to take a long time ............+....+........................+..................+...............+............................+...............+.......+.+.....................++*++*++*++*++*++* See the 'certs' directory for the certificates. The 'certs' directory should be copied to .../etc/raddb/ All passwords have been set to 'whatever'

2 1

LDAP authentication... Help Me...
by Maurizio Pederneschi 29 Nov '06

29 Nov '06

Hi, I'm a newbie for Freeradius. I've implemented this type of structure: APPLICATION --> PAM --> FREERADIUS --> SQL I want substitute SQL with a LDAP backend; I don't need any type of accounting; I just want that application check userid and password on my LDAP server. How can I accomplish that? MySql seem to work but frequently I get this type of error in radiusd.log: Nov 29 18:04:11 public20 safesquid: pam_radius_auth: RADIUS server 212.80.192.120 failed to respond Nov 29 18:04:11 public20 safesquid: pam_radius_auth: All RADIUS servers failed to respond. Nov 29 18:04:11 public20 safesquid: pam_radius_auth: RADIUS server 212.80.192.120 failed to respond Nov 29 18:04:11 public20 safesquid: pam_radius_auth: All RADIUS servers failed to respond. Nov 29 18:04:15 public20 safesquid: pam_radius_auth: RADIUS server 212.80.192.120 failed to respond Nov 29 18:04:15 public20 safesquid: pam_radius_auth: All RADIUS servers failed to respond. And I don't know why this error appear. Can anybody help me? Thank's, Maury76

1 0

RE: Unable to authenticate freeradius using PostgreSQL
by Ross McOwat 29 Nov '06

29 Nov '06

All sorted! I copied a fresh-install postgresql.conf file from another server, and bingo, all is working fine. Must have made a mistake while editing this file - note to self, make copies of the file BEFORE editing it! Thanks for everyones help. Ross -----Original Message----- From: freeradius-users-bounces+ross.mcowat=first-utility.com(a)lists.freeradius. org [mailto:freeradius-users-bounces+ross.mcowat=first-utility.com@lists.fre eradius.org] On Behalf Of Ross McOwat Sent: 29 November 2006 10:53 To: FreeRadius users mailing list Subject: RE: Unable to authenticate freeradius using PostgreSQL OK, I've made progress. I now appear to be connecting to my Postgres database, as I'm receiving syntax errors in the database log file when trying a freeRadius authentication. The debug radius output is as follows (I now have queries against the radius_xlat line): rad_recv: Access-Request packet from host 10.150.19.134:1115, id=5, length=49 User-Name = "ROSStest4" User-Password = "nntlpa401" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "ROSStest4", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0 users: Matched DEFAULT at 156 modcall[authorize]: module "files" returns ok for request 0 radius_xlat: 'ROSStest4' rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' radius_xlat: 'SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = ' rlm_sql (sql): Reserving sql socket id: 4 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): Attempting to connect rlm_sql_postgresql #4 rlm_sql (sql): Connected new DB handle, #4 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): failed after re-connect rlm_sql_getvpdata: database query error rlm_sql (sql): SQL query error; rejecting user rlm_sql (sql): Released sql socket id: 4 modcall[authorize]: module "sql" returns fail for request 0 modcall: group authorize returns fail for request 0 Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 10.150.19.134:1115, id=5, length=49 Discarding duplicate request from client ROSSpc:1115 - ID: 5 --- Walking the entire request list --- Waking up in 2 seconds... --- Walking the entire request list --- Cleaning up request 0 ID 5 with timestamp 456d62ae Nothing to do. Sleeping until we see a request. rad_recv: Access-Request packet from host 10.150.19.134:1115, id=5, length=49 User-Name = "ROSStest4" User-Password = "nntlpa401" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 1 modcall[authorize]: module "preprocess" returns ok for request 1 modcall[authorize]: module "chap" returns noop for request 1 modcall[authorize]: module "mschap" returns noop for request 1 rlm_realm: No '@' in User-Name = "ROSStest4", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 1 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 1 users: Matched DEFAULT at 156 modcall[authorize]: module "files" returns ok for request 1 radius_xlat: 'ROSStest4' rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' radius_xlat: 'SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = ' rlm_sql (sql): Reserving sql socket id: 3 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): Attempting to connect rlm_sql_postgresql #3 rlm_sql (sql): Connected new DB handle, #3 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): failed after re-connect rlm_sql_getvpdata: database query error rlm_sql (sql): SQL query error; rejecting user rlm_sql (sql): Released sql socket id: 3 modcall[authorize]: module "sql" returns fail for request 1 modcall: group authorize returns fail for request 1 Finished request 1 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... --- Walking the entire request list --- Cleaning up request 1 ID 5 with timestamp 456d62b5 Nothing to do. Sleeping until we see a request. The following is what is logged in my /var/log/pgsql trace when trying the above query: LOG: statement: SELECT id, UserName, Attribute, Value, Op # authorize_check_query = ERROR: syntax error at end of input at character 69 (repeated 4 times) So I suspect now that my user data is incorrect. The output from my database files is as follows: radius=# select * from radcheck; id | username | attribute | value | op ----+-----------+-----------+-----------+---- 1 | ROSStest3 | Password | bdwnlc274 | == 2 | ROSStest4 | Password | nntlpa401 | == (2 rows) radius=# select * from radreply; id | username | attribute | value | op ----+-----------+-------------------+---------------+---- 1 | ROSStest3 | Framed-IP-Address | 10.150.19.134 | := 2 | ROSStest4 | Framed-IP-Address | 10.150.19.134 | := (2 rows) I have changed the 'value' and 'op' columns around, as the authentication sql query within postgresql.conf appears to try and retrieve 'value' before 'op'. Using the supplied database schema, the op column appears BEFORE value. Not sure if this is significant or not? Or possibly the actual data format I've entered is incorrect? I suspect (hope) it's something as simple as that. -----Original Message----- From: freeradius-users-bounces+ross.mcowat=first-utility.com(a)lists.freeradius. org [mailto:freeradius-users-bounces+ross.mcowat=first-utility.com@lists.fre eradius.org] On Behalf Of Alan DeKok Sent: 28 November 2006 16:53 To: FreeRadius users mailing list Subject: Re: Unable to authenticate freeradius using PostgreSQL "Ross McOwat" <ross.mcowat(a)first-utility.com> wrote: > rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' > radius_xlat: '' > rlm_sql (sql): Reserving sql socket id: 4 > rlm_sql (sql): SQL query error; rejecting user It looks like you haven't configured the SQL queries needed by the server. The "radius_xlat" line SHOULD be printing out the query it's going to use. The default postgresql.conf has queries that work for Postgres. Are you using those, or have you edited the file? Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

2 1

RE: Unable to authenticate freeradius using PostgreSQL
by Ross McOwat 29 Nov '06

29 Nov '06

Thanks Kevin - you were right, the issue was with the SQL query in postgresql.conf. I replaced my existing file with a default file on another server, and everything worked fine. Many thanks for your help! Ross -----Original Message----- From: freeradius-users-bounces+ross.mcowat=first-utility.com(a)lists.freeradius. org [mailto:freeradius-users-bounces+ross.mcowat=first-utility.com@lists.fre eradius.org] On Behalf Of Kevin Bonner Sent: 29 November 2006 16:16 To: FreeRadius users mailing list Subject: Re: Unable to authenticate freeradius using PostgreSQL On Wednesday 29 November 2006 05:52, Ross McOwat wrote: > radius_xlat: 'SELECT id, UserName, Attribute, Value, Op > #?authorize_check_query = ' > rlm_sql (sql): Reserving sql socket id: 4 > rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op > #?authorize_check_query = > rlm_sql_postgresql: Status: PGRES_FATAL_ERROR radius_xlat now shows the query, but "SELECT id, UserName, Attribute, Value, Op" is not a valid SQL query. The "authorize_check_query" being listed in the radius_xlat line means that you haven't properly quoted the SQL query in the config file. Look at the default postgresql.conf to see what you're missing... paying close attention to quotation marks. > I have changed the 'value' and 'op' columns around, as the > authentication sql query within postgresql.conf appears to try and > retrieve 'value' before 'op'. Using the supplied database schema, the > op column appears BEFORE value. Not sure if this is significant or not? > Or possibly the actual data format I've entered is incorrect? I suspect > (hope) it's something as simple as that. It doesn't matter how the table columns are arranged, as long as your query asks for them in the correct order. Kevin Bonner

1 0

RE: Unable to authenticate freeradius using PostgreSQL
by Ross McOwat 29 Nov '06

29 Nov '06

OK, I've made progress. I now appear to be connecting to my Postgres database, as I'm receiving syntax errors in the database log file when trying a freeRadius authentication. The debug radius output is as follows (I now have queries against the radius_xlat line): rad_recv: Access-Request packet from host 10.150.19.134:1115, id=5, length=49 User-Name = "ROSStest4" User-Password = "nntlpa401" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "ROSStest4", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0 users: Matched DEFAULT at 156 modcall[authorize]: module "files" returns ok for request 0 radius_xlat: 'ROSStest4' rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' radius_xlat: 'SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = ' rlm_sql (sql): Reserving sql socket id: 4 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): Attempting to connect rlm_sql_postgresql #4 rlm_sql (sql): Connected new DB handle, #4 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): failed after re-connect rlm_sql_getvpdata: database query error rlm_sql (sql): SQL query error; rejecting user rlm_sql (sql): Released sql socket id: 4 modcall[authorize]: module "sql" returns fail for request 0 modcall: group authorize returns fail for request 0 Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 10.150.19.134:1115, id=5, length=49 Discarding duplicate request from client ROSSpc:1115 - ID: 5 --- Walking the entire request list --- Waking up in 2 seconds... --- Walking the entire request list --- Cleaning up request 0 ID 5 with timestamp 456d62ae Nothing to do. Sleeping until we see a request. rad_recv: Access-Request packet from host 10.150.19.134:1115, id=5, length=49 User-Name = "ROSStest4" User-Password = "nntlpa401" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 1 modcall[authorize]: module "preprocess" returns ok for request 1 modcall[authorize]: module "chap" returns noop for request 1 modcall[authorize]: module "mschap" returns noop for request 1 rlm_realm: No '@' in User-Name = "ROSStest4", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 1 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 1 users: Matched DEFAULT at 156 modcall[authorize]: module "files" returns ok for request 1 radius_xlat: 'ROSStest4' rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' radius_xlat: 'SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = ' rlm_sql (sql): Reserving sql socket id: 3 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): Attempting to connect rlm_sql_postgresql #3 rlm_sql (sql): Connected new DB handle, #3 rlm_sql_postgresql: query: SELECT id, UserName, Attribute, Value, Op #?authorize_check_query = rlm_sql_postgresql: Status: PGRES_FATAL_ERROR rlm_sql_postgresql: affected rows = rlm_sql_postgresql: Postgresql check_error: PGRES_FATAL_ERROR, returning SQL_DOWN rlm_sql (sql): failed after re-connect rlm_sql_getvpdata: database query error rlm_sql (sql): SQL query error; rejecting user rlm_sql (sql): Released sql socket id: 3 modcall[authorize]: module "sql" returns fail for request 1 modcall: group authorize returns fail for request 1 Finished request 1 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... --- Walking the entire request list --- Cleaning up request 1 ID 5 with timestamp 456d62b5 Nothing to do. Sleeping until we see a request. The following is what is logged in my /var/log/pgsql trace when trying the above query: LOG: statement: SELECT id, UserName, Attribute, Value, Op # authorize_check_query = ERROR: syntax error at end of input at character 69 (repeated 4 times) So I suspect now that my user data is incorrect. The output from my database files is as follows: radius=# select * from radcheck; id | username | attribute | value | op ----+-----------+-----------+-----------+---- 1 | ROSStest3 | Password | bdwnlc274 | == 2 | ROSStest4 | Password | nntlpa401 | == (2 rows) radius=# select * from radreply; id | username | attribute | value | op ----+-----------+-------------------+---------------+---- 1 | ROSStest3 | Framed-IP-Address | 10.150.19.134 | := 2 | ROSStest4 | Framed-IP-Address | 10.150.19.134 | := (2 rows) I have changed the 'value' and 'op' columns around, as the authentication sql query within postgresql.conf appears to try and retrieve 'value' before 'op'. Using the supplied database schema, the op column appears BEFORE value. Not sure if this is significant or not? Or possibly the actual data format I've entered is incorrect? I suspect (hope) it's something as simple as that. -----Original Message----- From: freeradius-users-bounces+ross.mcowat=first-utility.com(a)lists.freeradius. org [mailto:freeradius-users-bounces+ross.mcowat=first-utility.com@lists.fre eradius.org] On Behalf Of Alan DeKok Sent: 28 November 2006 16:53 To: FreeRadius users mailing list Subject: Re: Unable to authenticate freeradius using PostgreSQL "Ross McOwat" <ross.mcowat(a)first-utility.com> wrote: > rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' > radius_xlat: '' > rlm_sql (sql): Reserving sql socket id: 4 > rlm_sql (sql): SQL query error; rejecting user It looks like you haven't configured the SQL queries needed by the server. The "radius_xlat" line SHOULD be printing out the query it's going to use. The default postgresql.conf has queries that work for Postgres. Are you using those, or have you edited the file? Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

2 1

Different accounting based on avpair
by Nuno Pais Fernandes 29 Nov '06

29 Nov '06

Hi, I've been searching the ML for something related to this without any success. I don't know if freeradius does what i need and correct me if i'm wrong. I want to freeradius insert/update different sql tables using a avpair from my custom dictionary. What i would like is somthing like this: "if avpair Wireless = yes use accounting module sql1 else use accounting module sql2" accounting { acct_unique sql1 if (Wireless = yes) sql2 if (Wireless != yes) } Could it be done with users file? Thanks, -- Nuno Miguel Pais Fernandes <npf(a)eurotux.com> Cisco Certified Network Associate Oracle Certified Professional Eurotux Informática, S.A. [http://eurotux.com] Rua Rosalvo de Almeida, 5. 4710-429 BRAGA PORTUGAL Tel: (+351) 253 257395 - Fax: (+351) 253 257396

2 3

freeRadius auth. with Active Directory and LDAP
by Robert 29 Nov '06

29 Nov '06

Hi I want that my freeRadius validates users against Active Directory with LDAP. For configuration reasons, I can't use NTLM. Did any of you guys already configured a freeRADIUS and AD with LDAP ? Is this posible? Thanks in advance ,

3 2

Freeradius, EAP-TTLS ans eDirectory
by Mariano Morano 29 Nov '06

29 Nov '06

Hi all, We are working in a RFP and one of the customer's requirement is that we must support EAP-TTLS with Freeradius integrated with eDirectory as back-end. We were reading the Novell documentation and at the Novell page, there appears "How to integrate Novell® eDirectoryTM 8.7.1 or later with FreeRADIUS 1.0.2 on wards to allow wireless authentication for eDirectory users." and it not mntions EAP-TTLS (only EAP-TLS) SO, Some questions: 1) First, can we use Freeradius with EAP-TTLS and eDirectory as back end ? 2) if we can waht version of frereadius should we use ? 3) Ca someone send us information about how do that? I would appreciate any hel ASAP Thanks in advance.

2 3

RE: RADIUS PAP-SecurID Access-Challenge
by david＠mitton.com 29 Nov '06

29 Nov '06

I'm sorry, The other day I said that there is nothing "unusual" about SecurID RADIUS authentication. I'm so used to EAP, I forgot about the PAP auth with a SecurID value as a password. If the RSA Authentication Manager, finds that the token is in New Pin or Next Tokencode mode, it will issue an Access-Challenge message with the Reply-Message attribute explaining the next step. The client is expected to display the text, and prompt the user, then send another Access-Request with the response in the password attribute. This exchange can continue through several steps, until an Access-Accepted or -Rejected is received. Only a few RADIUS test clients can actually deal with this. I don't know (off the top of my head) which production clients we recommend. Of course, for the best security the EAP-POTP method is our recommended authentication protocol. Dave.

3 2

RE: Unable to authenticate freeradius using PostgreSQL
by Ross McOwat 28 Nov '06

28 Nov '06

Hi Kevin, I am running debug with the -X flag - in this instance, I only included the output I thought relevant (probably a mistake). Complete output from the radius authentication request (with 3 attempts set) is as follows: rad_recv: Access-Request packet from host 10.150.19.134:2250, id=0, length=49 User-Name = "ROSStest4" User-Password = "nntlpa401" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 0 modcall[authorize]: module "preprocess" returns ok for request 0 modcall[authorize]: module "chap" returns noop for request 0 modcall[authorize]: module "mschap" returns noop for request 0 rlm_realm: No '@' in User-Name = "ROSStest4", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 0 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 0 users: Matched DEFAULT at 156 modcall[authorize]: module "files" returns ok for request 0 radius_xlat: 'ROSStest4' rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' radius_xlat: '' rlm_sql (sql): Reserving sql socket id: 4 rlm_sql (sql): SQL query error; rejecting user rlm_sql (sql): Released sql socket id: 4 modcall[authorize]: module "sql" returns fail for request 0 modcall: group authorize returns fail for request 0 Finished request 0 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... rad_recv: Access-Request packet from host 10.150.19.134:2250, id=0, length=49 Discarding duplicate request from client ROSSpc:2250 - ID: 0 --- Walking the entire request list --- Waking up in 3 seconds... --- Walking the entire request list --- Cleaning up request 0 ID 0 with timestamp 456c68e0 Nothing to do. Sleeping until we see a request. rad_recv: Access-Request packet from host 10.150.19.134:2250, id=0, length=49 User-Name = "ROSStest4" User-Password = "nntlpa401" Processing the authorize section of radiusd.conf modcall: entering group authorize for request 1 modcall[authorize]: module "preprocess" returns ok for request 1 modcall[authorize]: module "chap" returns noop for request 1 modcall[authorize]: module "mschap" returns noop for request 1 rlm_realm: No '@' in User-Name = "ROSStest4", looking up realm NULL rlm_realm: No such realm "NULL" modcall[authorize]: module "suffix" returns noop for request 1 rlm_eap: No EAP-Message, not doing EAP modcall[authorize]: module "eap" returns noop for request 1 users: Matched DEFAULT at 156 modcall[authorize]: module "files" returns ok for request 1 radius_xlat: 'ROSStest4' rlm_sql (sql): sql_set_user escaped user --> 'ROSStest4' radius_xlat: '' rlm_sql (sql): Reserving sql socket id: 3 rlm_sql (sql): SQL query error; rejecting user rlm_sql (sql): Released sql socket id: 3 modcall[authorize]: module "sql" returns fail for request 1 modcall: group authorize returns fail for request 1 Finished request 1 Going to the next request --- Walking the entire request list --- Waking up in 6 seconds... --- Walking the entire request list --- Cleaning up request 1 ID 0 with timestamp 456c68e7 Nothing to do. Sleeping until we see a request. I may be missing something obvious, but for the life of me I cannot see what it is. My head is starting to hurt now! Ross -----Original Message----- From: freeradius-users-bounces+ross.mcowat=first-utility.com(a)lists.freeradius. org [mailto:freeradius-users-bounces+ross.mcowat=first-utility.com@lists.fre eradius.org] On Behalf Of Kevin Bonner Sent: 28 November 2006 16:40 To: FreeRadius users mailing list Subject: Re: Unable to authenticate freeradius using PostgreSQL On Tuesday 28 November 2006 11:00, Ross McOwat wrote: > Other tables are empty. Running freeradius in debug mode, the following > output is given when attempting an authentication request using > NTRadPing: That output is very brief for "debug" mode. You are using the -X flag, right? If not, do so and you'll see why it's dying in the rlm_sql module. Kevin Bonner

2 1