1.x to 2.x Upgrade Howto available?
Is there a 'howto' on upgrade from Freeradius 1.x to 2.x, one that lists what configs were moved where, etc. that would allow a person to do the upgrade as smoothly and quickly as possible (I can't seem to find one). Or better yet, are there any perl or python scripts available that automate the config conversions (or am I just dreaming :) )? Thanks, John This message is confidential to Prodea Systems, Inc unless otherwise indicated or apparent from its nature. This message is directed to the intended recipient only, who may be readily determined by the sender of this message and its contents. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient:(a)any dissemination or copying of this message is strictly prohibited; and(b)immediately notify the sender by return message and destroy any copies of this message in any form(electronic, paper or otherwise) that you have.The delivery of this message and its information is neither intended to be nor constitutes a disclosure or waiver of any trade secrets, intellectual property, attorney work product, or attorney-client communications. The authority of the individual sending this message to legally bind Prodea Systems is neither apparent nor implied,and must be independently verified.
On 22 June 2009, at 10:41, John Kane wrote:
Is there a 'howto' on upgrade from Freeradius 1.x to 2.x, one that lists what configs were moved where, etc. that would allow a person to do the upgrade as smoothly and quickly as possible (I can't seem to find one).
One place that really helped me with that is raddb/sites-available/ README.
John Kane wrote:
Is there a 'howto' on upgrade from Freeradius 1.x to 2.x, one that lists what configs were moved where, etc. that would allow a person to do the upgrade as smoothly and quickly as possible (I can't seem to find one).
By and large, the configurations are compatible. You could *almost* take a configuration from 0.9.3, and use it in 2.1.6. They're that close. Many of the configuration items have move (log_foo=bar to log{ foo=bar} ), but the old syntax is still accepted. That being said, it's always worth reading the configs in 2.x, and *migrating* the configuration. This means making it work the new way, rather than simply copying the old way. It's not hard, and it won't take a long time.
Or better yet, are there any perl or python scripts available that automate the config conversions (or am I just dreaming :) )?
Sure... write one, and we'll add it in. Alan DeKok.
participants (3)
-
Alan DeKok -
Doug Hardie -
John Kane