Upgrading FreeRadius
We have FreeRadius v2.2.0 running on Centos 6 VMs and want to upgrade to v2.2.5. Various files in /usr/local/etc/raddb have been customised for use with our eduroam network. Is there a recommended upgrade method for v2.2.5? Thanks for any advice forthcoming. Martin.
Martin Ubank wrote:
We have FreeRadius v2.2.0 running on Centos 6 VMs and want to upgrade to v2.2.5.
Various files in /usr/local/etc/raddb have been customised for use with our eduroam network.
Is there a recommended upgrade method for v2.2.5?
Install 2.2.5. It will *not* over-write your existing configuration. Alan DeKok.
Hi,
We have FreeRadius v2.2.0 running on Centos 6 VMs and want to upgrade to v2.2.5.
Various files in /usr/local/etc/raddb have been customised for use with our eduroam network.
Is there a recommended upgrade method for v2.2.5?
do what you did to build/install 2.2.0 before you 'make install' you should do a backup copy *just in case* eg cp -R /usr/local/etc/raddb /usr/local/etc/raddb.backup FreeRADIUS installer should not touch any files that already exist - however, note that this means some files (eg dictionary files) might not have newer entries in..and any FreeRADIUS config files that use new features/expose new features wont be seen in your config - so read/compare the new 2.2.5 src raddb entries to see what you are missing out on :-) alan
Hi Alan, Thanks for your reply. I have made a backup of the v2.2.0 configuration files. To ensure I get the new features of v2.2.5 and the custom changes that were in place for v2.2.0, how would you suggest I go about the integration of the configuration files? Should I start with all the v2.2.0 files and ensure the new version works with them, then integrate the v2.2.5 changes, testing them one-by-one? Or is there a better method? For v2.2.0, I upgraded from a package install, so everything was in a different location. I added the previous custom changes into the v2.2.0 configuration files and it worked pretty much first time. That approach hasn't worked this time. Thanks Martin.
-----Original Message----- From: freeradius-users- bounces+martin.ubank=uwe.ac.uk@lists.freeradius.org [mailto:freeradius- users-bounces+martin.ubank=uwe.ac.uk@lists.freeradius.org] On Behalf Of A.L.M.Buxey@lboro.ac.uk Sent: 15 August 2014 13:30 To: FreeRadius users mailing list Subject: Re: Upgrading FreeRadius
Hi,
We have FreeRadius v2.2.0 running on Centos 6 VMs and want to upgrade to v2.2.5.
Various files in /usr/local/etc/raddb have been customised for use with our eduroam network.
Is there a recommended upgrade method for v2.2.5?
do what you did to build/install 2.2.0
before you 'make install' you should do a backup copy *just in case* eg cp -R /usr/local/etc/raddb /usr/local/etc/raddb.backup
FreeRADIUS installer should not touch any files that already exist - however, note that this means some files (eg dictionary files) might not have newer entries in..and any FreeRADIUS config files that use new features/expose new features wont be seen in your config - so read/compare the new 2.2.5 src raddb entries to see what you are missing out on :-)
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
To ensure I get the new features of v2.2.5 and the custom changes that were in place for v2.2.0, how would you suggest I go about the integration of the configuration files?
install the new version over the old, then look at your config files and see the differences. your custom changes will still be there - and the new files will contain the new things heres were you say that theold configs had all the stuff stripped out of them....at which point I say 'then you've now got a bigger comparison job to do' (why do people strip their configs bare? it doesnt slow the speed of the server and means you lose visibilty of things you dont use....if you want to see your config 'clean' then grab the initial output of radiusd -X or just cat configfileyoucareabout | egrep -v "(^#|+.#|^$)" ;-) alan PS if you are building your own and over-riding a package version, then ensure you build your own with same arguments as the packaged version (get its SPEC file and see what their ./configure arguments were etc)
Hi Alan (Buxey), Thank you for your help. The new version of FreeRadius is now working after I (just) installed it over the old version. Best wishes Martin.
-----Original Message----- From: freeradius-users- bounces+martin.ubank=uwe.ac.uk@lists.freeradius.org [mailto:freeradius- users-bounces+martin.ubank=uwe.ac.uk@lists.freeradius.org] On Behalf Of A.L.M.Buxey@lboro.ac.uk Sent: 15 August 2014 16:29 To: FreeRadius users mailing list Subject: Re: Upgrading FreeRadius
Hi,
To ensure I get the new features of v2.2.5 and the custom changes that were in place for v2.2.0, how would you suggest I go about the integration of the configuration files?
install the new version over the old, then look at your config files and see the differences.
your custom changes will still be there - and the new files will contain the new things
heres were you say that theold configs had all the stuff stripped out of them....at which point I say 'then you've now got a bigger comparison job to do'
(why do people strip their configs bare? it doesnt slow the speed of the server and means you lose visibilty of things you dont use....if you want to see your config 'clean' then grab the initial output of radiusd -X or just
cat configfileyoucareabout | egrep -v "(^#|+.#|^$)"
;-)
alan
PS if you are building your own and over-riding a package version, then ensure you build your own with same arguments as the packaged version (get its SPEC file and see what their ./configure arguments were etc)
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Martin Ubank wrote:
To ensure I get the new features of v2.2.5 and the custom changes that were in place for v2.2.0, how would you suggest I go about the integration of the configuration files?
There are minimal new features in v2.2.5. Just upgrade, and everything will continue working.
Should I start with all the v2.2.0 files and ensure the new version works with them, then integrate the v2.2.5 changes, testing them one-by-one?
Or is there a better method?
I already said you could just upgrade.
For v2.2.0, I upgraded from a package install, so everything was in a different location. I added the previous custom changes into the v2.2.0 configuration files and it worked pretty much first time. That approach hasn't worked this time.
I guess the error messages are secret. Alan DeKok.
participants (3)
-
A.L.M.Buxey@lboro.ac.uk -
Alan DeKok -
Martin Ubank