NEW Package: freeRADIUS 2.x

reggie14

What did resolve the problem described by reggie14 in my case was to download the configuration, edit the xml-file by deleting the sections dealing with freeradius and then uploading the result again.

I was able to resolve it by doing another clean install. The first thing I did (before restoring config) was to install freeradius2. Then I restored a backup config that had several packages disabled.

With your method, did you lose your radius config?

michaelschefczyk

Dear Reggie14,

Doing it my way did keep most of the configuration except - for reasons I do not understand completely - the interfaces and the EAP settings. I was able to copy them (both manually and via HASync are possible as it seems) easily from another system. I found that simpler than unplugging cables, reassigning interfaces and link aggregation groups and similar consequences of installing from scratch. For my remaining systems, I plainly uninstalled freeradius before the upgrade to install it again afterwards. That has not been necessary with any 2.x upgrade before. This time, it was probably mandatory to upgrade without any losses.

Regards,

Michael Schefczyk

thetrevster

Does the amount of traffic counter bug still exist in the latest version of FreeRADIUS on pfSense 2.3 or am I most likely going to have to wait until FreeRADIUS 3 is released?

jimp

@thetrevster:

Does the amount of traffic counter bug still exist in the latest version of FreeRADIUS on pfSense 2.3 or am I most likely going to have to wait until FreeRADIUS 3 is released?

Which bug specifically? There have been fixes recently to both time and data counting.

thetrevster

Sorry for not being specific, see post 602 of mine in this thread :)

jimp

That looks like a traffic counting bug a fixed a while back in the package (In November), FreeRADIUS2 pkg version 1.6.17 or later should be OK.

thetrevster

Awesome!! This is excellent news - thank you!

thetrevster

After further testing the bug unfortunately still seems to be present (see attachment). In the system logs, I can still see the data counting up for a specific user even though that client has absolutely no traffic (or extremely minimal) passing through. Does anybody know if there's any workaround for this? :-\

Capture.PNG_thumb

thetrevster

Who and how much do I have to pay to get this fixed or a workaround for this? :D or does anybody else have another solution for weekly bandwidth capping by registered MAC address on a network?

werter

Hi!
pfsense 2.2.5-i386

I want to use wpa2-ent with latest freeradius2 + MS AD (Win 2008). But I can't configure :(

Can anybody show working screenshots of FreeRADIUS: Interfaces, FreeRADIUS: EAP , FreeRADIUS: LDAP ?

Thank you, guys.

![FreeRADIUS_ EAP.jpg](/public/imported_attachments/1/FreeRADIUS_ EAP.jpg)
![FreeRADIUS_ EAP.jpg_thumb](/public/imported_attachments/1/FreeRADIUS_ EAP.jpg_thumb)
![FreeRADIUS_ LDAP.jpg](/public/imported_attachments/1/FreeRADIUS_ LDAP.jpg)
![FreeRADIUS_ LDAP.jpg_thumb](/public/imported_attachments/1/FreeRADIUS_ LDAP.jpg_thumb)

epek

I think, I have found a bug...

	freeradius3 0.15.5_2 dependencies

bash-4.4.12_3 freeradius3-3.0.15_4 python27-2.7.14_1

on pfsense 2.4.3-RELEASE-p1 (amd64):

Occurance: When adding an account for a new user, when changing a user's password

condition: if the user's password contains a double quote ('"'), freeradius will not start anymore.

Cause: The unescaped double quote is written directly to the config files, which invalidates freeradius config's syntax.

johnpoz

You should most likely create a new thread if you feel you have found a bug, and if can duplicate it then please open a redmine on it. Locking this thread since it is 7 years old.

And freerad 2.x is no longer a new package anyway.