Upgrading from 1.17 to 2.14 MySQL schema

Steve Bertrand iaccounts at ibctech.ca
Fri Jun 5 14:30:00 CEST 2009


Marinko Tarlac wrote:
> Also, instead of usergroup table in dialup.conf file you'll find
> radusergroup as table name. You can solve this "issue". Just delete
> "rad" and leave "usergroup"... Also, you have priority fields and you
> can comment them in dialup.conf if you don't need them.

Thanks Alan and Marinko,

After reviewing the entire situation, it doesn't appear that it's going
to be as big an issue as I first thought.

The only table that I use that is different in structure is the radacct
table.

At first, I thought I would have to migrate all of that data into the
new database. However, because I aggregate daily and monthly totals into
a different table, I *should* be able to switch over to the new RADIUS
servers around midnight, and then thereafter, migrate my daily/monthly
aggregate total tables over.

I've got many custom applications that dip into the RADIUS database
across the network, but I think there is only one that accesses the
radacct table directly, so that's easily fixed.

Thanks for the help,

Steve



More information about the Freeradius-Users mailing list