NAS list with MySQL
Hi there... i am new to free radius. I already successfully installed freeradius 1.1.7 with mysql5.1. The point is NAS's IPs and secrets are configured in clients.conf. I cannot find anything how to put those data to SQL database. Sql.conf doesn't describe any table or value for clients, can anyone give any clue how to store those data in SQL database Pawel Cieplinski
the script nas.sql has the mysql table schema. the file sql.conf at the end you can see : # Set to 'yes' to read radius clients from the database ('nas' table) # Clients will ONLY be read on server startup. For performance # and security reasons, finding clients via SQL queries CANNOT # be done "live" while the server is running. # #readclients = yes # Table to keep radius client info nas_table = "nas" As you can see the default table name is nas ( can you imagine :-) ). Uncoment readclients = yes Make configuration changes at radiusd.conf and enable sql module. On 19/01/2008, Pawel Cieplinski <pawel@parkandmarine.com> wrote:
Hi there... i am new to free radius. I already successfully installed freeradius 1.1.7 with mysql5.1. The point is NAS's IPs and secrets are configured in clients.conf. I cannot find anything how to put those data to SQL database. Sql.conf doesn't describe any table or value for clients, can anyone give any clue how to store those data in SQL database
Pawel Cieplinski
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
Hi there... i am new to free radius. I already successfully installed freeradius 1.1.7 with mysql5.1. The point is NAS's IPs and secrets are configured in clients.conf. I cannot find anything how to put those data to SQL database. Sql.conf doesn't describe any table or value for clients, can anyone give any clue how to store those data in SQL database
sql.conf has the readclients directive and the sql schema clearly shows the nas table mysql>describe nas; simply populate. enable the readclients directive. with 1.1.x i believe you still need a single entry in clients.conf - a fake entry - eg 127.0.0.2 or it barfs. 2.0.0 doesnt have this issue alan
A.L.M.Buxey@lboro.ac.uk wrote: Hi
with 1.1.x i believe you still need a single entry in clients.conf - a fake entry - eg 127.0.0.2 or it barfs. 2.0.0 doesnt have this issue
alan -
Thanks i managed to sort that out Can u tell me about stability in freeradius 2.0.0. I am preparing a project for servers wchich will have to serve more than few milion entries (users) and i am concercn using "lastests" versions Pawel Cieplinski
Pawel Cieplinski wrote:
Can u tell me about stability in freeradius 2.0.0. I am preparing a project for servers wchich will have to serve more than few milion entries (users) and i am concercn using "lastests" versions
A number of very large sites have been using pre-releases of 2.0.0 for a long time. The final release has been out for almost 2 weeks, and I haven't heard of a single major problem. Just a few minor issues. Alan DeKok.
Hi,
Can u tell me about stability in freeradius 2.0.0. I am preparing a project for servers wchich will have to serve more than few milion entries (users) and i am concercn using "lastests" versions
personally I would go for 2.0.0 - its been in beta for a long long time, it handles the packets better, it has far better scalability and its does have the quirks that live in the 1.1.x branch alan
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
orion -
Pawel Cieplinski