NEW Package: freeRADIUS 2.x

michaelschefczyk

Dear Package Developers & Experts,

please consider, if the settings unter "EAP" and then "CERTIFICATES FOR TLS" do work as intended in the freeradius2, 2.1.12_1/2.2.4 pkg v. 1.6.7_3 package. My aim is to use EAP-TLS.

The settings suggest that one can choose between the FreeRADIUS Cert-Manager (not recommended) and Firewall Cert-Manager (recommended). To use the recommended variant, one has to check the box in "Choose Cert-Manager". As indicated, the Firewall Cert-Manager generates certificates with no private key passwords. Correspondingly, the instructions on "Private Key Password" are "… The certificates created by the firewall's built-in Cert Manager are not protected so you must leave this field empty.". However, the eap.conf file - as far as I can tell - always contains either the password that one does actively enter into the field or the default password (private_key_password = whatever). I think that a configuration with an empty password cannot be generated. With a private_key_password set to anything or "whatever" or at least not nothing at all, the configuration does not seem to work with keyless certificates of the Firewall Cert-Manager. What happens if it does not work is described in more detail under https://forum.pfsense.org/index.php?topic=78684.msg429199#msg429199.

Regards,

Michael Schefczyk

Nachtfalke

Hi,

try to modify the line 899 from this:

$vareapconfprivatekeypassword = ($eapconf['vareapconfprivatekeypassword']?$eapconf['vareapconfprivatekeypassword']:'whatever');

to this:

$vareapconfprivatekeypassword = ($eapconf['vareapconfprivatekeypassword']?$eapconf['vareapconfprivatekeypassword']:'');

Then try again with an empty field on the freeradius EAP GUI.
If it works - consider making a change on github.

michaelschefczyk

Dear Nachtfalke,

Thank you very much! I am generally able to edit files on the pfSense server using Diagnostics->edit file or via ssh. I can also see the freeradius.inc-file on github. However, I lack the skills required to connect both sides. In particular, I did have a hard time locating the file to be edited on the pfsense server, if this is what you imply. I assume that it may be in /user/pbi/freeradius-amd64, however, there is a large directory structure with many files there. Could you plese tell me where to find the file in question?

Regards,

Michael Schefczyk

athurdent

Hi Nachtfalke,

do you have plans to make freeradius2 work on 2.2? Sadly it still refuses to start with the following output, I just updated my system to the latest Alpha release.

Jul 8 11:18:27	root: /usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: /usr/local/etc/raddb is not a directory.
Jul 8 11:18:27	root: /usr/pbi/freeradius-amd64/etc/rc.d/radiusd: WARNING: failed precmd routine for radiusd

Nachtfalke

@michaelschefczyk

You can go to shell a do a search for the files you are looking for like this:


find / -iname "*freeradius*"

This shows you all files which contain "freeradius" within with any letters before or behind.
The file you are looking for is "freeradius.inc" You will find this file here:


/usr/local/pkg/

@athurdent
I left my old company more than 6 months ago and the new company does not use pfsense nor are there plans to do so :(
So I personally will not do any changes on this package anymore but everyone who is able to do so and has time please feel free to do it!

I only built this package in the past because I needed it and I had the hardware to test all or most of these features in my environment.

michaelschefczyk

Dear Nachtfalke, dear all,

It turns out that a change in freeradius.inc is not required to solve the underlying problem.

The real cause is that the CRL does not work, when using the pfsense cert manager with freeradius. The CRL stays – unlike all my other CRLs on the machine – marked as not in use (“NO” in the “In Use” column) while selected in the freeradius package. This does not depend on the CRL beeing empty or containing at least one certificate. If one selects “none” for “SSL Revocation List”, things (including advanced features, such as VLAN ID assignment per user) do work, albeit without a CRL.

Beyond that, I did notice the following issues with EAP-TLS – comments would be appreciated a lot:

The end user device connecting needs to provide an identity which is equivalent to the client certificate CN and the freeradius user name. The identity can be typed in at most end user devices, e.g, Android. Other identities cannot be spoofed, I think. But without the identity (i.e., if the user leaves it blank), the items listed for the user (e.g., VLAN ID) will not apply. Hence, if certain VLANs are giving escalated rights, they should not be made the default VLAN. Given the issues below, if one seriously wants to use the items specified per user, one will probably need to assign a mute VLAN as default to avoid the user getting access without specifying the identity – not an elegant solution.
Without a CRL it is difficult to block users, once they are in possession of a certificate. It seems that only user settings can prevent a user from being authenticated. That is problematic given the previous comment. I had no luck adding “DEFAULT Auth-Type = Reject” to the “Additional RADIUS Attributes on the TOP” field or similar attempts.
Assuming that the end user has control of the certificate, i.e., he has the file and knows the install password, if applicable, it would be nice to be able to limit the certificate / user to a set of devices identified by MAC addresses. Limiting a user to one device works by adding “Calling-Station-Id := AA-BB-CC-DD-EE-FF” to “Additional RADIUS Attributes (CHECK-ITEM)”. What I did not manage is to specify a set of IPs permissible either for an individual user or for all users at large.

I would like to thank Nachtfalke very much for his contributions. I hope that the package freeradius will not disappear in future versions of pfsense despite Nachtfalke’s departure from the package!

Regards,

Michael Schefczyk

kallegr

Now, one year later: Is Active Directory Authentication working via GUI-Configuration out of the box?

or do i still need to install a selfcompiled samba package and tweak?

@Nachtfalke:

@klokslag:

Hi all,

I read the entire topic, because i wanna use Freeradius to authenticate against AD.
In the topic there are suggestions to make it possible via the gui.

My question is. Is it now possible to authencate against AD without the tweaking?
Or do i have to use the tutorial from MatSim (Nachtfalke, marcelloc)

Thanx in advance.

Unfortunately my last info is that it does not work without any tweaks and only with GUI.
I do not know which topic/tutorial you mean but probably it is the correct one ;-)

unixaccent

Hi zlyzwy;
Hi Nachtfalke;
Hi Everyone;
Your conversation on the following thread makes my learning curve easier.
https://forum.pfsense.org/index.php?topic=43675.msg235475#msg235475
I want to thank you both for this.
I hope I am not asking too much. I have a question about how to setup sqlcounter in reference to zlyzwy and if I understand it right, the setup is "pfsense+freeradius" + "external databse." Its like after connecting "pfsense+freeradius" to "external database", all accounting stuffs will be logged to the "radacct" table of the external database. I wonder how to setup the counter in pfsense box and how does pfsense send a "disconnect message" if a user has reached a quota like the "download size" in a day or "maximum session" in a day.
Regards;

jetberrocal

@Nachtfalke:

Updates pkg v1.4.3:

Added: GUI to configure FreeRADIUS2 with LDAP. This will only work if we can use the new binaries.

Updated: FreeRADIUS 2.x package documentation on http://doc.pfsense.org/index.php/FreeRADIUS_2.x_package

Reference Version: pfsense 2.1.5 Freeradius 2.2.5_3 pkg v1.6.11

I think there is a misunderstanding on LDAP Authorization and Authentication. When I uncheck "Enable LDAP For Authorization", the General Configuration fields are disabled and emptied. Without this values the Authentication does not know how to connect to LDAP, so it fails. The way is working in my reference Version, you have to Authorize to be able to Authenticate, and that is not correct for all the cases.

I had to modify manually the sites-enable file in order to disable LDAP Authorize for my configuration to work correctly. If you want, follow the freeradius user mailing list for the detail in my situation.

http://freeradius.1045715.n5.nabble.com/Authenticating-users-on-LDAP-based-on-Group-name-td5732701i20.html

reggie14

I set up FreeRADIUS for use on my guest wifi network with EAP. At this time I'm not planning on using Captive Portal- I just wanted to be able to provide per-user passwords and bandwidth limits.

However, I'd like to be able to disable users without deleting them. I don't see a "disable" button, but I figure there might be a way to do something similar. I tried setting "Number of simultaneous connections" to 0 and wasn't overly surprised when it didn't work (I'm just using a Asus consumer-grade AP).

Is there a way to effectively disable a user without deleting it?

l.capriotti

I need to customise freeradius with a custom site file and a custom script for the authentication, where should I place these files in order for them to survive a pfsense upgrade?
Until now I saved these files in /usr/pbi/freeradius/etc/raddb but they are not restored after a system upgrade.
I saw reference to /usr/local/etc/raddb, chall I use that directory instead?

Nachtfalke

@reggie14:

I set up FreeRADIUS for use on my guest wifi network with EAP. At this time I'm not planning on using Captive Portal- I just wanted to be able to provide per-user passwords and bandwidth limits.

However, I'd like to be able to disable users without deleting them. I don't see a "disable" button, but I figure there might be a way to do something similar. I tried setting "Number of simultaneous connections" to 0 and wasn't overly surprised when it didn't work (I'm just using a Asus consumer-grade AP).

Is there a way to effectively disable a user without deleting it?

Hi,

bandwidth limit and number of connections are features that must be supported by your Wireless AP. If the AP does not support it it will not work. A chance that it could work is if your AP supports "accounting" but then you need the coresponding RADIUS attributes from your vendor.

To disable a user there is no "disable" button but I think you can workaround with the "Expiration date". Thi will only work for a specific date.
If you need to disable an account for a specific time then you should add possible time ranges with the "Possiblöe Time Ranges" option. Using both together should allow you to disable a user.

Nachtfalke

@l.capriotti:

I need to customise freeradius with a custom site file and a custom script for the authentication, where should I place these files in order for them to survive a pfsense upgrade?
Until now I saved these files in /usr/pbi/freeradius/etc/raddb but they are not restored after a system upgrade.
I saw reference to /usr/local/etc/raddb, chall I use that directory instead?

Hi,
I would give you a suggestion to use the additional package "System Patches". The make a "diff" of the original and your new file and paste the diff into the "System Patches" package and then you can enable "auto apply" so it should apply after upgrades - unless there is no change on the original file.

For complete new custom scripts - don't know where the best place on pfsense is. Here is a path where freeradius stores custom scripts:
/usr/pbi/freeradius-amd64/etc/raddb/scripts
or you add your script to the freeradius.inc so it will be created on specific action:

https://github.com/pfsense/pfsense-packages/blob/master/config/freeradius2/freeradius.inc

Have a look at lines 4143 - 4180


function freeradius_datacounter_auth_resync() {
	global $config;
	$conf = '';

	$conf .= <<<eod<br>#!/bin/sh
### USAGE: datacounter_auth.sh USERNAME TIMERANGE
### We need this parameters from freeradius users file and ../raddb/modules/datacounter_acct
USERNAME=`echo -n "\\$1" | sed 's/[^0-9a-zA-Z._:-]/X/g' `
TIMERANGE=`echo -n "\\$2" | sed 's/[^a-z]//g' `

### This is to make sure there is a used-octets file after the cronjob resetted the counter
if [ -e "/var/log/radacct/datacounter/\$TIMERANGE/max-octets-\$USERNAME" ] && [ ! -e "/var/log/radacct/datacounter/\$TIMERANGE/used-octets-\$USERNAME" ]; then
	echo 0 > "/var/log/radacct/datacounter/\$TIMERANGE/used-octets-\$USERNAME"
fi

### The next two lines are just for getting values for logging output
MAXOCTETSUSERNAMEMB=$((`cat "/var/log/radacct/datacounter/\$TIMERANGE/max-octets-\$USERNAME"`/1024/1024))
USEDOCTETSUSERNAMEMB=$((`cat "/var/log/radacct/datacounter/\$TIMERANGE/used-octets-\$USERNAME"`/1024/1024))

### We check if MAX-OCTETS-USERNAME is greater than USED-OCTETS-USERNAME and accept or reject the user
if [ `cat "/var/log/radacct/datacounter/\$TIMERANGE/max-octets-\$USERNAME"` -gt `cat "/var/log/radacct/datacounter/\$TIMERANGE/used-octets-\$USERNAME"` ]; then
	logger -f /var/log/system.log "FreeRADIUS: Used amount of \$TIMERANGE traffic by \$USERNAME is \$USEDOCTETSUSERNAMEMB MB of \$MAXOCTETSUSERNAMEMB MB! The user was accepted!!!"
	exit 0
else
	logger -f /var/log/system.log "FreeRADIUS: Credentials are probably correct but the user \$USERNAME has reached the \$TIMERANGE Amount of Upload and Download Traffic which is \$USEDOCTETSUSERNAMEMB MB of \$MAXOCTETSUSERNAMEMB MB! The user was rejected!!!"
	exit 99
fi
EOD;

	$filename = FREERADIUS_ETC . '/raddb/scripts/datacounter_auth.sh';
	conf_mount_rw();
	file_put_contents($filename, $conf);
	chmod($filename, 0750);
	conf_mount_ro();

}</eod<br>

You can replace the /bin/bash script there with your own and then give the function an new name, edit the path where you want to save the script and if you want add the function below line 422 so that it will be executed every time you click "Save" on the Freeradius "Settings" menu in the GUI.

biGdada

Hi.
Is it possible to use mOTP with MSCHAPv2?
I am getting a reject, while PAP with mOTP works.

sisko212

Good day to everybody,
As you maybe know, latest package Freeradius2 1.6.15 that contains a Freeradius 2.2.6 daemon, has a trouble on EAP-TLS authentication.
Above all with latest Android 6.0 Marshmallow.
Some tech details are available here:
https://code.google.com/p/android/issues/detail?id=188867#c29
Someone known if it exists a workaround, perhaps editing some configuration files on freeradius, or also on Android with some apps, in order to avoid this issue ?
Thanks a lot in advance for your time and for any suggestion.

David_W

The issues you mention should be fixed in FreeRADIUS 2.2.9, which is now in FreeBSD ports.

FreeRADIUS 2.x is now end of life. Hopefully someone will come forward to develop a FreeRADIUS 3.x package, though I would suggest any development efforts target the forthcoming pfSense 2.3.

thetrevster

I'm on the latest version of pfSense (2.2.4 - 64 bit) with Captive Portal and the FreeRADIUS 2.x package setup for traffic capping. Everything is working properly to re-authenticate users every minute and I'm using the MAC address as the username. I'm currently capping users at 6000MB (total upload and download) per day. I added a test machine in and noticed that the traffic counter isn't working correctly. I was aware of this issue on older version of pfSense, but it seems that I am having a similar issue in the latest build. Any thoughts? See below an output from the system logs.

Oct 30 15:37:56 root: FreeRADIUS: Used amount of daily traffic by 247703xxxxxx is 35 MB of 6000 MB! The user was accepted!!!
Oct 30 15:38:58 root: FreeRADIUS: Used amount of daily traffic by 247703xxxxxx is 70 MB of 6000 MB! The user was accepted!!!

I have a local counter on the test machine, counting all traffic in/out of the wireless NIC. Within that time period, it shows I've only transferred 800KB, but the logs are showing 30+ MB. Thanks in advance for any input.

tamersherif

@thetrevster:

I'm on the latest version of pfSense (2.2.4 - 64 bit) with Captive Portal and the FreeRADIUS 2.x package setup for traffic capping. Everything is working properly to re-authenticate users every minute and I'm using the MAC address as the username. I'm currently capping users at 6000MB (total upload and download) per day. I added a test machine in and noticed that the traffic counter isn't working correctly. I was aware of this issue on older version of pfSense, but it seems that I am having a similar issue in the latest build. Any thoughts? See below an output from the system logs.

Oct 30 15:37:56 root: FreeRADIUS: Used amount of daily traffic by 247703xxxxxx is 35 MB of 6000 MB! The user was accepted!!!
Oct 30 15:38:58 root: FreeRADIUS: Used amount of daily traffic by 247703xxxxxx is 70 MB of 6000 MB! The user was accepted!!!

I have a local counter on the test machine, counting all traffic in/out of the wireless NIC. Within that time period, it shows I've only transferred 800KB, but the logs are showing 30+ MB. Thanks in advance for any input.

Yes the the problem still exists int 2.2.4 i tried every thing and every tutorial on the internet but it's confirmed that this is a bug.

thetrevster

That is unfortunate, I could really use this feature. Is the bug actively being worked on / any idea on when it will be fixed? Thanks.

@sisko212:

Good day to everybody,
As you maybe know, latest package Freeradius2 1.6.15 that contains a Freeradius 2.2.6 daemon, has a trouble on EAP-TLS authentication.
Above all with latest Android 6.0 Marshmallow.
Some tech details are available here:
https://code.google.com/p/android/issues/detail?id=188867#c29
Someone known if it exists a workaround, perhaps editing some configuration files on freeradius, or also on Android with some apps, in order to avoid this issue ?
Thanks a lot in advance for your time and for any suggestion.

Just got Marshmallow OTA update myself and smacked into this same problem. EAP-TLS configuration that has been working fine for quite a while, now no longer works on upgraded Nexus 7.

Symptoms are that the device appears to negotiate authentication, FreeRADIUS logs indicate the device was authenticated, but the device never finishes joining the network, and just keeps repeating.

From the Google thread, the issue is tied to the use of TLSv1.2 and downgrading to TLSv1.1 or 1.0, the final keying is correct. But downgrading to broken encryption standards is not what I'd consider a workaround.

From other forum reading, it sounds like this is going to be a quickly growing problem as Marshmallow is currently being rolled out OTA to all Nexus devices and expected to hit OEM devices soon.

So really the only question then is how soon an updated release that contains a fix for this issue can be made available.