> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > Peter Nixon > Sent: Saturday, July 12, 2003 6:34 AM > To: [EMAIL PROTECTED] > Subject: Re: Dictionary and NAS tables > > > > > > This sounds like a resonable solution to me. I already have > a table listing > > my NASes anyway for reporting and query purposes, it would > certainly make > > things neater if radius could use the same table. > Especially for cases > > where you have more than radius server accessing a single > DB backend. > > I have modified the postgres schema in CVS to have the following: > > CREATE TABLE nas ( > id SERIAL PRIMARY KEY, > nasname VARCHAR(128), > shortname VARCHAR(32) NOT NULL, > ipaddr inet NOT NULL, > type VARCHAR(30), > ports int4, > secret VARCHAR(60) NOT NULL, > community VARCHAR(50), > snmp VARCHAR(10), > naslocation VARCHAR(32) > ); > > This now has the capability of being a useful table for > reporting (I use a > similar table to run reports per city by listing City in > naslocation and then > doing a JOIN against the accounts table on ipaddr then a GROUP BY > naslocation. >
Who is inserting/updating data in this table? Unless you change the SQL statment in sql.conf file, I do not see anywhere the radius server is touching this table. Is there other process/daemon monitoring the protocol stream and update the table in the background? - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
