NEW Package: freeRADIUS 2.x
-
It does work like a charm now!
Thanks.So, is this small modification something you will be including in the next freeradius package or not ? Or something which has to stay there for other purposes?
As you could read in my last pkg Updates post here on the forum ;o)
I have included that. You now can choose if you want to enable or disable the SoH server and - thats the main part - I correctet the servername from "soh" which was wrong to "soh-server" which is correct.So it shpuld work with and without but in future you will have the decision ;-)
-
This is great stuff!
-
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
-
-
Nice one!
One more question for you if you don't mind: are the settings for freeradius2 package kept in xml files within the OS?
cause I noticed if you reinstall the package after you removed it does keep old settings. Is there a quick way to purge the config? -
Nice one!
One more question for you if you don't mind: are the settings for freeradius2 package kept in xml files within the OS?
cause I noticed if you reinstall the package after you removed it does keep old settings. Is there a quick way to purge the config?Yes, all settings, users, clients are saved in the config. The only thing which is NOT stored there are the CA and certs which you created with the freeradius cert-manager. If you use the pfsense cert-manager then these are saved in the config, too.
To cleanup the config from old freeradius entries there are two ways:
1.) Diagnostics -> Backup/Restore -> Backup the config.xml and then delete the freeradius2 entries and restore the config. A reboot is needed.
2.) SSH to your pfsense and edit /config/config.xml and delete the freeradius2 entries. A reboot is needed. -
@gettons
Not sure if this is an problem of freeradius or a configuration "problem" of your AP or freeradius-EAP setup.
The package offers the default settings which are in the eap.conf file. I am unsure what you have to change as I need to read the docs and wikis on freeradius first.You could try with "copy reply to tunnel".
You further did not post the output of what "radiusd -X" is showing. radius.log and system.log do not offer all "errors".
@Nachfalke
This is the output of radiusd -X once I try to connect with my android mobile phone.
Again, it might be useful for you to know. With the previous version of your package it used to work fine. What I did was just to uninstall the package and install it again. I also rebooted in between just to be double sure.The log is http://pastebin.com/XAsPjDSD It;s quite long and I didn't want to mess the thread
Hi,
the reason why I asked you between which version the error comes up was to find out what I changed and what could cause the problem.
I think I could reproduce your problem with my hardware and it is pointing to the "soh" server.Lines ~470
[peap] server soh { No such virtual server "soh" Invalid user: [gettons/<no user-password="" attribute="">] (from client wifi-ap port 0 via TLS tunnel) [peap] } # server soh [peap] Got SoH reply [peap] SoH was rejected [peap] FAILURE</no>
You could try the following until the pfsense server offers the new version:
- SSH to your pfsense
- Kill radiusd service
- edit /usr/local/etc/raddb/eap.conf
- scroll down where you find these two lines:
soh = yes soh_virtual_server = "soh-server"
Delete these lines, save the file and restart freeradius FROM CONSOLE
/usr/local/sbin/etc/rc.d/radiusd onestart
Then it should work.
Although It worked, after a reboot the changes I made in /usr/local/etc/raddb/eap.conf get reverted.
-
That is the behaviour of files which are configured by GUI. They will be overwritten in many situations.
You have to wait until the freeradius pkg 1.4.3 or higher is available. There is nothing I can do now - you could ask the pfsense developers why the repo isn't syncing. -
Updates pkg v1.4.4:
- Added: LDAP GUI -> We need to wait until we can use the freeradius2 package compiled with the missing dependencies and modules (rlm_ldap) but the GUI is working
Updates pkg v1.4.5:
-
Added: Ability to do use first 802.1X auth and if this fails check the Access-Request against a plain mac auth file (authorized_macs). This will help us if we use a NAS which does not support converting the mac address into a "username/password"-802.1X like Access-Request.
-
Added: Plain MAC Auth entries could now be synced with XMLRPC
-
TO-DO: Check/Test how we could place check and reply-items the beste way in authorized_macs.
-
Updated: Documentation on docs.pfsense.org
-
Hi,
Very useful package!!! Thanks a lot!
My question is:-
Does this package support Mysql now? Actually I can see the option in the PF Menu but it seems not working.
-
I would like to create a Hotspot by using this package + Captive Portal + MySQL + DDWRT Router. (eg:http://www.wiwiz.com/)
It would be great appreciated if there is any references for setting these matters?
Sorry for the poor English.
Thanks again for any reply! -
-
Hi,
Very useful package!!! Thanks a lot!
My question is:-
Does this package support Mysql now? Actually I can see the option in the PF Menu but it seems not working.
-
I would like to create a Hotspot by using this package + Captive Portal + MySQL + DDWRT Router. (eg:http://www.wiwiz.com/)
It would be great appreciated if there is any references for setting these matters?
Sorry for the poor English.
Thanks again for any reply!Hi,
-
LDAP and SQL isn't supported at the moment. The GUI is ready but we first have to compile freeradius with MySQL, PostgreSQL and LDAP support. This takes some time but it will be supported in the - hopefully - near future.
-
I didn't use that but as far as I know the CaptivePortal in pfsense supports connecting to a RADIUS. An if this package has MySQL support this should be possible for you to realize.
-
-
Hi,
Very useful package!!! Thanks a lot!
My question is:-
Does this package support Mysql now? Actually I can see the option in the PF Menu but it seems not working.
-
I would like to create a Hotspot by using this package + Captive Portal + MySQL + DDWRT Router. (eg:http://www.wiwiz.com/)
It would be great appreciated if there is any references for setting these matters?
Sorry for the poor English.
Thanks again for any reply!Hi,
-
LDAP and SQL isn't supported at the moment. The GUI is ready but we first have to compile freeradius with MySQL, PostgreSQL and LDAP support. This takes some time but it will be supported in the - hopefully - near future.
-
I didn't use that but as far as I know the CaptivePortal in pfsense supports connecting to a RADIUS. An if this package has MySQL support this should be possible for you to realize.
Thanks for the quick reply!
Looking forward to the update version:)
-
-
zlyzwy,
If you know how to handle with packages at console and want to help on testing these new features, follow Nachtfalke posts on how to update to test version
http://forum.pfsense.org/index.php/topic,43675.msg232220.html#msg232220
http://forum.pfsense.org/index.php/topic,43675.msg232312.html#msg232312
-
Updates pkg v1.4.6:
- Fixed: When Plain MAC Auth is enabled we are now able to not only check against EAP-X but against all other modules. The MAC check is now before all other checks and if it fails it proceeds with the rest.
-
Updates pkg v1.4.7:
-
Added: extended features for MySQL, PostgreSQL, LDAP, Kerberos support
-
Changed: Path to new packages and its dependencies
-
Updated: FreeRADIUS 2.x package documentation on doc.pfsense.org
And the oscar goes to:
marcelloc
Thank you for compiling freeradius2 with the extended features and hosting the packages! -
-
I'm trying to get LDAP working but I'm getting the following output:
[ldap] ldap_search() failed: Operations error [ldap] search failed [ldap] ldap_release_conn: Release Id: 0 ++[ldap] returns fail Invalid user: [USER/PASSW]
Does anyone know why this is happening? When I manually do an ldap search with another program with the same user I do get a result back.
-
Hello!
So Nachtfalke and marcelloc, thank you for great job!I've done the same job about two weeks ago and I regret now not sharing my work :/
I've compiled ldap, kerberos modules (don't needed mysql and other db's).So now to make AD integration possible it is necessary to have Samba and Kerberos packages.
why?
simple version, maybe little mixed up. samba has winbind, which allow kerberos to authenticate in windows domain.
winbind has module ntlm_auth which can ask server about the user, but we have to be member of domain.so what am I doing is tryin' to compile Samba 3 for Pfsense, next Kerberos and will post here about results
-
I'm trying to get LDAP working but I'm getting the following output:
[ldap] ldap_search() failed: Operations error [ldap] search failed [ldap] ldap_release_conn: Release Id: 0 ++[ldap] returns fail Invalid user: [USER/PASSW]
Does anyone know why this is happening? When I manually do an ldap search with another program with the same user I do get a result back.
you didn't give anything about your config, but I'll try guess:
If you have MS AD try to filter:
(sAMAccountName=%{mschap:User-Name})
otherwise maybe:
(uid=%{mschap:User-Name})I don't know if you have your Identity configured properly, show it for us
-
Hi,
Sorry, its indeed MS AD (2008R2). I already tried with the sAMAccountName but didn't had the MSCHAP in it, tried it again, but still no luck:
radtest nas PASSW localhost 1 testpass
[ldap] performing user authorization for nas [ldap] expand: (sAMAccountName=%{mschap:User-Name}) -> (sAMAccountName=nas) [ldap] expand: o=intersui,c=local -> o=intersui,c=local [ldap] ldap_get_conn: Checking Id: 0 [ldap] ldap_get_conn: Got Id: 0 [ldap] attempting LDAP reconnection [ldap] (re)connect to 10.10.1.1:389, authentication 0 [ldap] bind as WDSINST/***** to 10.10.1.1:389 [ldap] waiting for bind result ... [ldap] Bind was successful [ldap] performing search in o=intersui,c=local, with filter (sAMAccountName=nas) [ldap] ldap_search() failed: Operations error [ldap] search failed [ldap] ldap_release_conn: Release Id: 0 ++[ldap] returns fail Invalid user: [nas/****] (from client pfsense2 port 1)
Base Filter: (objectclass=*)
Filter: (sAMAccountName=%{mschap:User-Name})
Basedn: o=intersui,c=local -
Hi,
Sorry, its indeed MS AD (2008R2). I already tried with the sAMAccountName but didn't had the MSCHAP in it, tried it again, but still no luck:
radtest nas PASSW localhost 1 testpass
[ldap] performing user authorization for nas [ldap] expand: (sAMAccountName=%{mschap:User-Name}) -> (sAMAccountName=nas) [ldap] expand: o=intersui,c=local -> o=intersui,c=local [ldap] ldap_get_conn: Checking Id: 0 [ldap] ldap_get_conn: Got Id: 0 [ldap] attempting LDAP reconnection [ldap] (re)connect to 10.10.1.1:389, authentication 0 [ldap] bind as WDSINST/***** to 10.10.1.1:389 [ldap] waiting for bind result ... [ldap] Bind was successful [ldap] performing search in o=intersui,c=local, with filter (sAMAccountName=nas) [ldap] ldap_search() failed: Operations error [ldap] search failed [ldap] ldap_release_conn: Release Id: 0 ++[ldap] returns fail Invalid user: [nas/****] (from client pfsense2 port 1)
Base Filter: (objectclass=*)
Filter: (sAMAccountName=%{mschap:User-Name})
Basedn: o=intersui,c=localchange basedn to
basedn: cn=Users,dc=intersui,dc=local
as far as I know if you want filter sAMAccountName you have to use Microsoft style, so dc, dc ;) -
That did the trick :) BUT he still doesn't give me an accept message:
++[files] returns noop [ldap] performing user authorization for nas [ldap] expand: (sAMAccountName=%{mschap:User-Name}) -> (sAMAccountName=nas) [ldap] expand: ou=Accounts,dc=intersui,dc=local -> ou=Accounts,dc=intersui,dc=local [ldap] ldap_get_conn: Checking Id: 0 [ldap] ldap_get_conn: Got Id: 0 [ldap] performing search in ou=Accounts,dc=intersui,dc=local, with filter (sAMAccountName=nas) [ldap] looking for check items in directory... [ldap] looking for reply items in directory... WARNING: No "known good" password was found in LDAP. Are you sure that the user is configured correctly? [ldap] user nas authorized to use remote access [ldap] ldap_release_conn: Release Id: 0 ++[ldap] returns ok rlm_counter: Entering module authorize code rlm_counter: Could not find Check item value pair ++[daily] returns noop rlm_counter: Entering module authorize code rlm_counter: Could not find Check item value pair ++[weekly] returns noop rlm_counter: Entering module authorize code rlm_counter: Could not find Check item value pair ++[monthly] returns noop rlm_counter: Entering module authorize code rlm_counter: Could not find Check item value pair ++[forever] returns noop rlm_checkval: Could not find item named Calling-Station-Id in request rlm_checkval: Could not find attribute named Calling-Station-Id in check pairs ++[checkval] returns notfound ++[expiration] returns noop ++[logintime] returns noop [pap] WARNING! No "known good" password found for the user. Authentication may fail because of this. ++[pap] returns noop ERROR: No authenticate method (Auth-Type) found for the request: Rejecting the user Failed to authenticate the user. Login incorrect: [nas/*****] (from client pfsense2 port 1) Using Post-Auth-Type Reject
On Google this gives me lots of results but not really a solution. (The DN bind user is Administrator, so its not a permission issue - found some posts refering to this)
Also "set_auth_type = yes/no" as mentioned on Google doesn't help.