Procautions on upgrading FR from 2.1.10 to 2.2.0
Hello, I am planning to upgrade our FR from 2.1.10 to 2.2.0 to address increasing NTLM authentication failures using EAP-MSCHAPv2 in our wireless systems. I would welcome and appreciate advice on precautions I should take before, during, and after upgrade. Any issue did you run into in your upgrade, what impacts it had, and how did you resolve it? Thank you for your time. Yu Wang Network Architect Core Networking, FSU
Wang, Yu wrote:
I am planning to upgrade our FR from 2.1.10 to 2.2.0 to address increasing NTLM authentication failures using EAP-MSCHAPv2 in our wireless systems. I would welcome and appreciate advice on precautions I should take before, during, and after upgrade. Any issue did you run into in your upgrade, what impacts it had, and how did you resolve it?
You should be able to upgrade without any issues. Version 2.2.0 is backwards compatible with version 2.1.10. It wouldn't hurt to keep a backup just in case. It's 2013... disk space is pretty much free. Alan DeKok.
Thanks for the advice. I'll make a backup copy as we do have some customized scripts. Yu Wang Network Architect Core Networking, FSU -----Original Message----- From: freeradius-users-bounces+ywang10=fsu.edu@lists.freeradius.org [mailto:freeradius-users-bounces+ywang10=fsu.edu@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, April 23, 2013 10:15 AM To: FreeRadius users mailing list Subject: Re: Procautions on upgrading FR from 2.1.10 to 2.2.0 Wang, Yu wrote:
I am planning to upgrade our FR from 2.1.10 to 2.2.0 to address increasing NTLM authentication failures using EAP-MSCHAPv2 in our wireless systems. I would welcome and appreciate advice on precautions I should take before, during, and after upgrade. Any issue did you run into in your upgrade, what impacts it had, and how did you resolve it?
You should be able to upgrade without any issues. Version 2.2.0 is backwards compatible with version 2.1.10. It wouldn't hurt to keep a backup just in case. It's 2013... disk space is pretty much free. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
This is indeed a very considerate design, much better than some other software, like dhcp, that overwrites conf files every time. Thanks, Yu Wang -----Original Message----- From: freeradius-users-bounces+ywang10=fsu.edu@lists.freeradius.org [mailto:freeradius-users-bounces+ywang10=fsu.edu@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, April 23, 2013 11:46 AM To: FreeRadius users mailing list Subject: Re: Procautions on upgrading FR from 2.1.10 to 2.2.0 Wang, Yu wrote:
Thanks for the advice. I'll make a backup copy as we do have some customized scripts.
Installing a new version will *never* over-write your existing configuration files, scripts, etc. It *will* over-write binaries and libraries. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 04/23/2013 11:38 AM, Wang, Yu wrote:
Thanks for the advice. I'll make a backup copy as we do have some customized scripts.
As has been stated numerous times on this list you should keep any FR config file you modify or any file you add under source code control. Your repository located somewhere outside the raddb directory so you don't accidentally remove it during an upgrade and the repository should be backed up. This is a much better solution than keeping backup copies.
Yu Wang Network Architect Core Networking, FSU
-----Original Message----- From: freeradius-users-bounces+ywang10=fsu.edu@lists.freeradius.org [mailto:freeradius-users-bounces+ywang10=fsu.edu@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, April 23, 2013 10:15 AM To: FreeRadius users mailing list Subject: Re: Procautions on upgrading FR from 2.1.10 to 2.2.0
Wang, Yu wrote:
I am planning to upgrade our FR from 2.1.10 to 2.2.0 to address increasing NTLM authentication failures using EAP-MSCHAPv2 in our wireless systems. I would welcome and appreciate advice on precautions I should take before, during, and after upgrade. Any issue did you run into in your upgrade, what impacts it had, and how did you resolve it?
You should be able to upgrade without any issues. Version 2.2.0 is backwards compatible with version 2.1.10.
It wouldn't hurt to keep a backup just in case. It's 2013... disk space is pretty much free.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
Hi,
I am planning to upgrade our FR from 2.1.10 to 2.2.0 to address increasing NTLM authentication failures using EAP-MSCHAPv2 in our wireless systems. I would welcome and appreciate advice on precautions I should take before, during, and after upgrade. Any issue did you run into in your upgrade, what impacts it had, and how did you resolve it?
straight forward install from source over the old one.... you can compare recursively the 2.1.10 raddb directory against the 2.2.0 raddb directory - which is essential to note the new features/options as if you do an install over the top, then only new (unedited) files get created, all old files are untouched...which means that your config files dont contain comments/options for new features alan
hi, docs/ChangeLog * 100% configuration file compatible with 2.1.x. The only fix needed is to disallow "hashsize=0" for rlm_passwd so..if you havent played around with modules/passwd you'll find it just runs. alan
participants (4)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
John Dennis -
Wang, Yu