Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    NEW Package: freeRADIUS 2.x

    Scheduled Pinned Locked Moved pfSense Packages
    628 Posts 80 Posters 751.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nxsfan
      last edited by

      Just installed freeRADIUS on a relatively fresh (2.2.6) PFSense install. After minimal configuration clients were served with an expired (1/28/16) "Example Server Certificate". Is this intentional? I originally assumed that bootstrap was called after installing and starting freeRADIUS 2 the first time, but this isn't the case? After deleting the certificate and running bootstrap a new (temporally valid) certificate was generated. Perhaps this is expected? Thanks.

      1 Reply Last reply Reply Quote 0
      • T
        tux
        last edited by

        Will this freeradius work with mariadb?

        1 Reply Last reply Reply Quote 0
        • T
          tux
          last edited by

          @tux:

          Will this freeradius work with mariadb?

          To answer this question, yes as of the moment freeradius2 v1.6.19 under pfsense v2.2.6.  My DB server is mysqld 5.5.47-MariaDB-1ubuntu0.14.04.1.

          1 Reply Last reply Reply Quote 0
          • R
            reggie14
            last edited by

            Ias anyone able to install freeradius2 from the package manager in pfsense 2.3-rc?  After restoring my config, the radiusd service is running (and working), but the package manager says freeradius2 isn't installed. I've tried reinstalling (or uninstalling) the package, but nothing works.

            1 Reply Last reply Reply Quote 0
            • M
              michaelschefczyk
              last edited by

              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.

              1 Reply Last reply Reply Quote 0
              • R
                reggie14
                last edited by

                @michaelschefczyk:

                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?

                1 Reply Last reply Reply Quote 0
                • M
                  michaelschefczyk
                  last edited by

                  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

                  1 Reply Last reply Reply Quote 0
                  • T
                    thetrevster
                    last edited by

                    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?

                    1 Reply Last reply Reply Quote 0
                    • jimpJ
                      jimp Rebel Alliance Developer Netgate
                      last edited by

                      @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.

                      Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                      Need help fast? Netgate Global Support!

                      Do not Chat/PM for help!

                      1 Reply Last reply Reply Quote 0
                      • T
                        thetrevster
                        last edited by

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

                        1 Reply Last reply Reply Quote 0
                        • jimpJ
                          jimp Rebel Alliance Developer Netgate
                          last edited by

                          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.

                          Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                          Need help fast? Netgate Global Support!

                          Do not Chat/PM for help!

                          1 Reply Last reply Reply Quote 0
                          • T
                            thetrevster
                            last edited by

                            Awesome!! This is excellent news - thank you!

                            1 Reply Last reply Reply Quote 0
                            • T
                              thetrevster
                              last edited by

                              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
                              Capture.PNG_thumb

                              1 Reply Last reply Reply Quote 0
                              • T
                                thetrevster
                                last edited by

                                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?

                                1 Reply Last reply Reply Quote 0
                                • werterW
                                  werter
                                  last edited by

                                  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)

                                  E 1 Reply Last reply Reply Quote 0
                                  • E
                                    epek @werter
                                    last edited by

                                    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.

                                    1 Reply Last reply Reply Quote 0
                                    • johnpozJ
                                      johnpoz LAYER 8 Global Moderator
                                      last edited by

                                      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.

                                      An intelligent man is sometimes forced to be drunk to spend time with his fools
                                      If you get confused: Listen to the Music Play
                                      Please don't Chat/PM me for help, unless mod related
                                      SG-4860 24.11 | Lab VMs 2.8, 24.11

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post
                                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.