I am trying to install freeRADIUS on a CentOS 5.3 machine with PostgreSQL-8.3.7. My plan is to first install freeRADIUS and test it then setup PostgreSQL as the backend to store data. Is there any freeRADIUS RPMS V#2.1.4 or newer for CentOS? Jennifer
Just E. Mail wrote:
I am trying to install freeRADIUS on a CentOS 5.3 machine with PostgreSQL-8.3.7. My plan is to first install freeRADIUS and test it then setup PostgreSQL as the backend to store data.
Is there any freeRADIUS RPMS V#2.1.4 or newer for CentOS?
No, the version in RHEL and CentOS is 1.1.3. The following link explains why and also explains how to acquire and build a current FreeRADIUS RPM for RHEL/CentOS (but read the rest of this email, pre-built versions are coming). http://wiki.freeradius.org/Red_Hat_FAQ Please note, the wiki will direct you to download the most current SRPM from koji (the Fedora build system) to build yourself on RHEL/CentOS, the most current SRPM is 2.1.3, we did not and will not release 2.1.4 nor 2.1.5 for Fedora. However on tomorrow on Monday the 2.1.6 release is scheduled to go public from the FreeRADIUS project. Shortly thereafter I will have posted 2.1.6 SRPM and RPM's on koji (will probably show up by Tuesday). You may want to wait to pick up these RPM's instead of the 2.1.3. In the past I had been prohibited from providing current FreeRADIUS pre-built packages for RHEL/CentOS because it would have conflicted with the official version in the distribution (thus it was incumbent for RHEL/CentOS users to build their own version). However, just recently I have been granted permission to post pre-built current versions of FreeRADIUS for RHEL/CentOS. The new 2.1.6 version will be the first release this will occur for. Therefore sometime shortly after the 2.1.6 release becomes official I will post an announcement here on this list and update the aforementioned wiki page with links to the pre-built 2.1.6 release for RHEL/CentOS. I expect this will probably happen by Tuesday but no guarantees. It is critical to note for RHEL customers the updated RPMS are considered "tech preview" and do not come with any official RHEL support. We expect to provide an official update to RHEL with a 2.x version of FreeRADIUS in the next update cycle which would be RHEL 5.5, once included in an official update RHEL customers will receive support for the updated version. However RHEL 5.5 is almost a year away, thus this is the reason why I've been given permission to post current RHEL/CentOS packages on a "tech preview" basis, in anticipation of it's official inclusion in RHEL 5 but with a long incubation period. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
John Dennis wrote:
It is critical to note for RHEL customers the updated RPMS are considered "tech preview" and do not come with any official RHEL support.
If they want support for *any* version of the server, it's available. See http://networkradius.com But that's specific to FreeRADIUS, and not to the entire RHEL package. Alan DeKok.
On Sun, May 17, 2009 at 11:33 PM, John Dennis <jdennis@redhat.com> wrote:
We expect to provide an official update to RHEL with a 2.x version of FreeRADIUS in the next update cycle which would be RHEL 5.5,
So how do you plan to provide seamless upgrade for RHEL 5 users? Is freeradius 1.1.3 config compatible with 2.x? Or do we have to do a clean install? -- Fajar
Fajar A. Nugraha wrote:
So how do you plan to provide seamless upgrade for RHEL 5 users?
Upgrades across a major version number of software require manual changes to the configuration.
Is freeradius 1.1.3 config compatible with 2.x? Or do we have to do a clean install?
The configuration is *similar*, but not identical. I would suggest a clean install, followed by a manual migration of the configuration. It shouldn't take too long. An hour to a day, at most. Alan DeKok.
Fajar A. Nugraha wrote:
On Sun, May 17, 2009 at 11:33 PM, John Dennis <jdennis@redhat.com> wrote:
We expect to provide an official update to RHEL with a 2.x version of FreeRADIUS in the next update cycle which would be RHEL 5.5,
So how do you plan to provide seamless upgrade for RHEL 5 users? Is freeradius 1.1.3 config compatible with 2.x? Or do we have to do a clean install?
Please note what Alan said about upgrades across major versions requiring manual configuration. Also, the package will have a different name, rather than freeradius it will be named freeradius2, however (and this is critical) it will conflict at the file level, in other words the both freeradius and freeradius2 cannot be simultaneously installed. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
Hi,
Also, the package will have a different name, rather than freeradius it will be named freeradius2, however (and this is critical) it will conflict at the file level, in other words the both freeradius and freeradius2 cannot be simultaneously installed.
why not? /etc/raddb2 and seperate library path? ;-) I've got freeradius, freeradius2 and RADIATOR all on one box alan
Hi,
A.L.M.Buxey@lboro.ac.uk wrote:
I've got freeradius, freeradius2 and RADIATOR all on one box
What do we need to do so that Radiator can go away?
RADSEC :-) well, I've got radsecproxy but currently I need to run RADIATOR to keep my skillsets with that software up to date and check configurations and debugging/stats. alan
A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
Also, the package will have a different name, rather than freeradius it will be named freeradius2, however (and this is critical) it will conflict at the file level, in other words the both freeradius and freeradius2 cannot be simultaneously installed.
why not? /etc/raddb2 and seperate library path? ;-)
I've got freeradius, freeradius2 and RADIATOR all on one box
Sure, and that's fine for you, an expert ;-) This user list is proof positive a large proportion of users can't even read the config documentation, I can only imagine the confusion which would ensue if there were two config directories and sets of modules. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
Hi,
Sure, and that's fine for you, an expert ;-) This user list is proof positive a large proportion of users can't even read the config documentation, I can only imagine the confusion which would ensue if there were two config directories and sets of modules.
well, its possible....however there are 2 main issues. 1 - migration from v1 to v2 - which has to be undertaken at some point anyway. i did ponder about a semantic config parser to upgrade..but then having seen many peoples configs that isnt going to work. suggest a script that reads the config and points them to relevant modules??? 2 - only one RADIUS server can listen to UDP 1812/1813/1814 - therefore which one is it to be, radiusd v1 or radiusd v2? i think this is the show stopper anyway. alan
John Dennis wrote:
Just E. Mail wrote:
I am trying to install freeRADIUS on a CentOS 5.3 machine with PostgreSQL-8.3.7. My plan is to first install freeRADIUS and test it then setup PostgreSQL as the backend to store data.
Is there any freeRADIUS RPMS V#2.1.4 or newer for CentOS?
No, the version in RHEL and CentOS is 1.1.3. The following link explains why and also explains how to acquire and build a current FreeRADIUS RPM for RHEL/CentOS (but read the rest of this email, pre-built versions are coming).
I read response from John Dennis and looked at the web site URL he provided. I am ready to install FR and I have one more question! In my setup, I plan to (1) Install FR and test it and if everything works, then (2) setup PostgreSQL backend at a SQL server and test it again. I noticed that at the URL listed by John Dennis, there are two files; freradius-2.2.1.6-1.el5.i386.rpm freradius-postgresql-2.2.1.6-1.el5.i386.rpm I am pretty new to FR so please advice; do I need to install both of these RPMs or just the second for my setup to work?
Hi,
freradius-2.2.1.6-1.el5.i386.rpm freradius-postgresql-2.2.1.6-1.el5.i386.rpm
I am pretty new to FR so please advice; do I need to install both of these RPMs or just the second for my setup to work?
both. the second one adds the postgres support. alan
Just E. Mail wrote:
John Dennis wrote:
I read response from John Dennis and looked at the web site URL he provided. I am ready to install FR and I have one more question!
In my setup, I plan to (1) Install FR and test it and if everything works, then (2) setup PostgreSQL backend at a SQL server and test it again. I noticed that at the URL listed by John Dennis, there are two files;
freradius-2.2.1.6-1.el5.i386.rpm freradius-postgresql-2.2.1.6-1.el5.i386.rpm
I am pretty new to FR so please advice; do I need to install both of these RPMs or just the second for my setup to work?
Did you read the FAQ listed at the top. The section "Why are there optional subpackages instead of just one package?" should have explained it, was it not clear? If so I'll update it to make it clearer if you explain what was not clear. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
John Dennis wrote:
Did you read the FAQ listed at the top. The section "Why are there optional subpackages instead of just one package?" should have explained it, was it not clear? If so I'll update it to make it clearer if you explain what was not clear.
Yes I read it and read it again after receiving the above email.Missed it both times. Thank for your HELP. Jennifer
On Sun, May 17, 2009 at 11:33 PM, John Dennis <jdennis@redhat.com> wrote:
However on tomorrow on Monday the 2.1.6 release is scheduled to go public from the FreeRADIUS project. Shortly thereafter I will have posted 2.1.6 SRPM and RPM's on koji (will probably show up by Tuesday). You may want to wait to pick up these RPM's instead of the 2.1.3.
I just rebuilt 2.1.6 SRPM on RHEL5. I didnt' use packages from http://people.redhat.com/jdennis/freeradius-rhel-centos since I already have freeradius 2.1.3 installed as freeradius RPM, not freeradius2. I was hoping that upgrading from 2.1.3 would require a simple "rpm -Uvh". It didn't work :P After some troubleshooting, I found out that /etc/raddb/sites-available/* is NOT marked as %config(noreplace). Since sites-enabled only have symlinks to sites-available files, this effectively means RPM upgrade wiped out my customization (the relevant files I used was default and inner-tunnel) Is this intentional? Or perhaps I did something wrong? -- Fajar
Fajar A. Nugraha wrote:
I just rebuilt 2.1.6 SRPM on RHEL5.
Using which spec file?
After some troubleshooting, I found out that /etc/raddb/sites-available/* is NOT marked as %config(noreplace). Since sites-enabled only have symlinks to sites-available files, this effectively means RPM upgrade wiped out my customization (the relevant files I used was default and inner-tunnel)
The spec file distributed with the server marks /etc/raddb/* as config(noreplace). This might not be sufficient for sub-directories, though. Alan DeKok.
On Tue, Jun 2, 2009 at 1:48 PM, Alan DeKok <aland@deployingradius.com> wrote:
Fajar A. Nugraha wrote:
I just rebuilt 2.1.6 SRPM on RHEL5.
Using which spec file?
After some troubleshooting, I found out that /etc/raddb/sites-available/* is NOT marked as %config(noreplace). Since sites-enabled only have symlinks to sites-available files, this effectively means RPM upgrade wiped out my customization (the relevant files I used was default and inner-tunnel)
The spec file distributed with the server marks /etc/raddb/* as config(noreplace). This might not be sufficient for sub-directories, though.
Thanks for the info. -- Fajar
Fajar A. Nugraha wrote:
On Sun, May 17, 2009 at 11:33 PM, John Dennis <jdennis@redhat.com> wrote:
However on tomorrow on Monday the 2.1.6 release is scheduled to go public from the FreeRADIUS project. Shortly thereafter I will have posted 2.1.6 SRPM and RPM's on koji (will probably show up by Tuesday). You may want to wait to pick up these RPM's instead of the 2.1.3.
I just rebuilt 2.1.6 SRPM on RHEL5. I didnt' use packages from http://people.redhat.com/jdennis/freeradius-rhel-centos since I already have freeradius 2.1.3 installed as freeradius RPM, not freeradius2. I was hoping that upgrading from 2.1.3 would require a simple "rpm -Uvh". It didn't work :P
After some troubleshooting, I found out that /etc/raddb/sites-available/* is NOT marked as %config(noreplace). Since sites-enabled only have symlinks to sites-available files, this effectively means RPM upgrade wiped out my customization (the relevant files I used was default and inner-tunnel)
Is this intentional? Or perhaps I did something wrong?
It looks like this was a packaging bug in the spec file. You are indeed correct /etc/raddb/sites-available/* should have been %config(noreplace). I'm in the process of pushing out a new set of packages with your suggested fix. Thank you for reporting this. -- John Dennis <jdennis@redhat.com> Looking to carve out IT costs? www.redhat.com/carveoutcosts/
On Tue, 2009-06-02 at 16:27 -0400, John Dennis wrote:
It looks like this was a packaging bug in the spec file. You are indeed correct /etc/raddb/sites-available/* should have been %config(noreplace).
I'm in the process of pushing out a new set of packages with your suggested fix. Thank you for reporting this.
This is fantastic! I won't have to maintain my own freeradius package for CentOS 5. Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.27.21-170.2.56.fc10.x86_64 x86_64 GNU/Linux 00:29:20 up 10 days, 1:39, 2 users, load average: 0.09, 0.22, 0.24
participants (6)
-
A.L.M.Buxey＠lboro.ac.uk -
Alan DeKok -
Fajar A. Nugraha -
John Dennis -
Just E. Mail -
Kanwar Ranbir Sandhu