Closed drkhosla closed 3 years ago
alandekok
commented
3 years ago The latest version of FreeRADIUS is 3.0.21. The next release will be 3.0.22, which is in the v3.0.x branch.
You're building the "master" branch, which will become version 4 at some point. I suspect that this isn't what you want to do. We do not recommend running v4 unless you're fully aware of it's limitations.
alandekok
commented
3 years ago Further, something seems to be wrong with your local system. It says:
=== configuring in ./src/lib/ldap (/home/drkhosla/rpmbuild/BUILD/freeradius-server-4.0.0/./src/lib/ldap)
...
config.status: creating config.hExcept later there's no config.h in the src/lib/ldap directory. That seems fairly broken. It works here.
drkhosla
commented
3 years ago Problem is not with default compilation. I am able to compile and run independently but unable to make rpm. I am unable to find troubling option or configuration parameter or lib or include directory location in freeradius.spec file. Spec file is recently change for making LDAP as an optional.On 30 Dec 2020 20:34, Alan DeKok notifications@github.com wrote: Further, something seems to be wrong with your local system. It says: === configuring in ./src/lib/ldap (/home/drkhosla/rpmbuild/BUILD/freeradius-server-4.0.0/./src/lib/ldap) ... config.status: creating config.h
Except later there's no config.h in the src/lib/ldap directory. That seems fairly broken. It works here.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
drkhosla
commented
3 years ago The version 4.0.0 is given to tar fille. As it is already coded in free radius.spec file. On 30 Dec 2020 20:28, Alan DeKok notifications@github.com wrote: The latest version of FreeRADIUS is 3.0.21. The next release will be 3.0.22, which is in the v3.0.x branch. You're building the "master" branch, which will become version 4 at some point. I suspect that this isn't what you want to do. We do not recommend running v4 unless you're fully aware of it's limitations.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
alandekok
commented
3 years ago While we want to have the v4 RPMs build, let me be very clear. You should not be using the "master" branch.
Use v3. Full packages are available at http://packages.networkradius.com/
If you absolutely need v4, then please explain why. Otherwise I will be closing this PR as not relevant to any current release.
drkhosla
commented
3 years ago I think our time zone have lot of difference. Before I replied you in early morning, ticket is already closed. We already running v3 to our production system and it is running from last 20 years, Freeradius is defacto radius for most of the ISPs.
Your question is valid, why we want to use master branch, when stable branch is available. We are not using master branch for production. But now ISP market dynamic to look into the system where current freeradius doesn't fit as it is.
We are migrating our existing monolithic user management system, which is written in PHP to stateless microservice API based distributed system. Now we are using React and Golang to migrating system with backend as Cassandra db. We are also using Kubernetes and try to run Cassandra and Freeradius multiple instances in each and every POP and remove the dependency to centralised monolithic system.
The freeradius support Mysql, Postgresql, which are not distributed db. This is the reason we want to integrate to master less cassandra db. The problem with freeradius does not fully support cassandra or other nosql yet. We face lot of issues with compatibility with driver of Cassandra and now able to workaround and compile with commenting few lines and few changes in code.
To make it modular, we first build rpm and use these rpm to build docker images. These images are deployed in multiple replica distributed in geographically separated Kubernetes cluster. Each instance of freeradius connect to nearest Cassandra db node.
Though we are able to compile with cassandra, but writing sql counter is little bit tricky. We are in the process of designing, writing and testing sqlcounters. It is also challenging to integrate Oauth2 and OpenID with current setup as users also want Social login to their Wi-Fi captive portal.
I think current master version is best for development as there no support for cassandra in v3.
alandekok
commented
3 years ago I think current master version is best for development as there no support for cassandra in v3.
Your best bet is to add Cassandra support to v3.
The "master" branch is in active development. It may or may not build on a daily basis. It has large changes to its configuration, pretty much every month. The server core is being reworked, and may behave differently from time to time. EAP-TTLS doesn't work. PEAP doesn't work.
When I said that you should not be using "master", I meant it. Using v4 for Cassandra support is like wanting a better radio for your car, so you take a half-built car off of the assembly line. And then noticing that it doesn't have tires.
If you still insist on using v4 in production, we will generally ignore / close issues for it. In most cases, the issue will be already known to the development team, and is being worked on. In other cases, the issue is not relevant, as that part of the code is going away.
I really don't know how to be any more clear than this: v4 is not released. Don't use it.
drkhosla
commented
3 years ago Thanks for the clarification. It will help us a lot.On 31 Dec 2020 19:29, Alan DeKok notifications@github.com wrote:
I think current master version is best for development as there no support for cassandra in v3.
Your best bet is to add Cassandra support to v3. The "master" branch is in active development. It may or may not build on a daily basis. It has large changes to its configuration, pretty much every month. The server core is being reworked, and may behave differently from time to time. EAP-TTLS doesn't work. PEAP doesn't work. When I said that you should not be using "master", I meant it. Using v4 for Cassandra support is like wanting a better radio for your car, so you take a half-built car off of the assembly line. And then noticing that it doesn't have tires. If you still insist on using v4 in production, we will generally ignore / close issues for it. In most cases, the issue will be already known to the development team, and is being worked on. In other cases, the issue is not relevant, as that part of the code is going away. I really don't know how to be any more clear than this: v4 is not released. Don't use it.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.
Issue type
Unable to build rpm files using command
rpmbuild -ba rpmbuild/SPEC/freeradius.spec, it fail during compiling the code. I am using Centos 8Defect/Feature description
I am using CentOS 8 and trying to build rpms files for latest freeradius.
I clone the latest git of freeradius-server and try to build rpm files using command rpmbuild -ba rpmbuild/SPEC/freeradius.spec I get following error
How to reproduce issue
Clone latest freeradius-server and change directory name to freeradius-server-4.0.0
build tar file using following command
Copy freeradius-server-4.0.0.tar.bz2 to SOURCE directory of rpmbuild directory structure.
Copy all freeradius redhat source file to rpmbuild/SOURCE directory
Copy freeradius.spec file to rpmbuild/SPEC directory
Build rpm files using following command
Output