I have 0.5 deployed in production using postgresql as the backend.  Only
thing I don't have currently working in sql that I should is accounting.
I still have that going to files.  When I upgrade to 0.6, I plan on
using sql accounting as well.  I still have some ms-chap/mppe/pptp
issues to work out.

I believe the usergroup table is used as well.  I saw some talk about
loading the dictionaries into the dictionary table, but haven't verified
if it really makes use of that table or not.  

Tables I currently have data in are:
   radcheck
   usergroup
   radgroupreply



Charlie



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Alan Bunch
Sent: Sunday, July 07, 2002 10:50 AM
To: [EMAIL PROTECTED]
Subject: What is needed and what is used ...


First off thanks to all of the developers (especially Alan), you guys
rock !

I am using freeradius 0.5.   RedHat 7.2 and postgresql 7.1.3  I'll go to
0.6 after the 0.6.x release.

I have freeradius working using files.  I have a test instance mostly
working with postgesql.  My question is: What tables does freeradius
currently use in the database. It looks like it only uses rad* tables
and not any of the other tables.

Porying works as long as I have the files, proxy.conf and clients.conf,
configured.  I have not tested the dictionary file as yet.  I have the
realname, nas, and authport populated in the realms table.  I have what
I think are the correct values in the nas table, I am guessing about the
meaning of the snmp field in the nas table, I have yes as the value.

I do not have records in the dictionary table.

What tables is freeradius using and what files are being used.  It looks
like the schema is not being used completely and will be used to a
larger extent as development progresses.

Any discussion on this would be helpful.

alabun

Alan Bunch
[EMAIL PROTECTED]



- 
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html


- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to