Freeradius is unable to read NAS table in mysql db
Hi all. I'm pretty new with Freeradius, but it seems matching my targets :-) I set Freeradius with mysql server and Daloradius Management. After some troubles to install FR, it worked fine, at least as basical startup: i can authenticate remote users! For real it works if i use /raddb/clients.conf file, setting readclients = yes in /raddb/sql.conf. Once i set it to "no", autentication fails. I checked nas table structure and it's ok, the same as in /usr/local/etc/raddb/sql/mysql/nas.sql User are instead loaded fine from mysql users table. How could i solve it? Thanks in advance Here my configuration. Fedora Core 10 Freeradius 2.1.9 Daloradius 0.9-7 MySQL 5.0.88 Remote NAS: ZyXEL USG100 (2.21) Superataru --
I set Freeradius with mysql server and Daloradius Management. After some troubles to install FR, it worked fine, at least as basical startup: i can authenticate remote users! OK. For real it works if i use /raddb/clients.conf file, setting readclients = yes in /raddb/sql.conf. Once i set it to "no", autentication fails. I checked nas table structure and it's ok, the same as in /usr/local/etc/raddb/sql/mysql/nas.sql User are instead loaded fine from mysql users table. Your message doesn't have enough information to troubleshoot your problem. Run FreeRADIUS in debug mode (radiusd -X) and read the error messages. If you still can't solve your problem, send the debug output to the mailing list. Tim
I bag your pardon . . . i forget to turn to "no" the value in sql .conf. Once i did . . . non authentication . . . What i obtain with radiusd -X is . . . *Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Ready to process requests. Ignoring request to authentication address * port 1812 from unknown client 89.aa.bb.cc port 19556 Ready to process requests*. *89.aa.bb.cc is NAS address i set on mysql NAS table.* So no problems with tables structure, but some misconfiguration with data. What do you think?
I bag your pardon . . . i forget to turn to "no" the value in sql .conf. Once i did . . . non authentication . . .
What i obtain with radiusd -X is . . .
*Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Ready to process requests. Ignoring request to authentication address * port 1812 from unknown client 89.aa.bb.cc port 19556 Ready to process requests*.
*89.aa.bb.cc is NAS address i set on mysql NAS table.*
So no problems with tables structure, but some misconfiguration with data.
What do you think?
Hi,
So no problems with tables structure, but some misconfiguration with data.
as per previous email sent to you from another perosn helping you radiusd -X it will show you where the problem is - or send the output to the list because otherwise we can do little but make random guesses :-( alan
I bag your pardon . . . i forget to turn to "no" the value in sql .conf. Which value did you set to "no"? Once i did . . . non authentication . . . What i obtain with radiusd -X is . . . Listening on authentication address * port 1812 Listening on accounting address * port 1813 Listening on command file /usr/local/var/run/radiusd/radiusd.sock Ready to process requests. Ignoring request to authentication address * port 1812 from unknown client 89.aa.bb.cc port 19556 Ready to process requests. 89.aa.bb.cc is NAS address i set on mysql NAS table. Send the following information to the mailing list: 1. Copy of sql.conf - the entire file. 2. Copy of debug output for radiusd -X - everything from the radiusd -X command on down. 3. Copy of information in SQL table - output from "select * from nas/G" You have not sent us enough information to troubleshoot your problem. More information is better than less. Tim
participants (3)
-
Alan Buxey -
superataru - -
Tim Sylvester