- Freeradius-Users - lists.freeradius.org

Updating Winbindd Privileged Socket Path
by Vertigo Altair 21 Jun '21

21 Jun '21

Hi FreeRADIUS, I'm running Winbindd on some other directory. I have to update winbindd prieveleged socket path on FreeRADIUS side. I've read some documents but I couldn't find a configuration for this. My samba config: # cat /etc/samba/smb.conf [global] winbindd socket directory = /mydir/var/run/winbindd state directory = / mydir /var/run/samba/locks/state pid directory = / mydir /var/run/ cache directory = / mydir /var/run/samba/locks/cache lock directory = / mydir /var/run/samba/locks FreeRADIUS looks for the default winbindd socket directory (/var/run/samba/winbindd), but actually it should look for /permanent/var/run/samba/winbindd, how can I configure FreeRADIUS for that? Thanks in advance..

3 4

linelog get quoted string on demand
by Lineconnect 21 Jun '21

21 Jun '21

Hi Folks, i've edited the linelog module(also with help from this forum) to get a json log file(sample): ``` linelog log_general_message { format = "%t Log for %{jsonquote:%{User-Name}}" filename = ${logfile} permissions = 0644 reference = "messages.%{%{Packet-Type}:-format}" messages { Access-Request = "{\"Datetime\": \"%t\",\"Packet-Type\": \"%{Packet-Type}\",\"TLS-Cert-Issuer\": \"%{jsonquote:%{TLS-Client-Cert-Issuer}}\"}" } } ``` which results in: ``` {"Datetime": "Fri Jun 18 15:18:30 2021","Packet-Type": "Access-Request","TLS-Cert-Issuer": "/O=sample/OU=sample/CN=sample"} ``` It works fine. I've also such entries to log the Access-Acecpt, Reject and challange with other variables. Those variables are not always filled so it would be perfect to set them to null to eayseli remove those entries in the later log parsing. It's in general also possible with the conditional syntax '%{%{Foo}:-bar}'. The problem comes when the variable is filled then because it don't get quotet. Sample to understand what i mean: ``` linelog log_general_message { format = "%t Log for %{jsonquote:%{User-Name}}" filename = ${logfile} permissions = 0644 reference = "messages.%{%{Packet-Type}:-format}" messages { Access-Request = "{\"Datetime\": \"%t\",\"Packet-Type\": \"%{Packet-Type}\",\"TLS-Cert-Issuer\": %{jsonquote:%{%{TLS-Client-Cert-Issuer}:-null}}" } } ``` results in ``` {"Datetime": "Fri Jun 18 15:18:30 2021","Packet-Type": "Access-Request","TLS-Cert-Issuer": null} ``` which is perfect. But when %{TLS-Client-Cert-Issuer} is filled it results in a not valid json file because it's not in quotes: ``` {"Datetime": "Fri Jun 18 15:18:30 2021","Packet-Type": "Access-Request","TLS-Cert-Issuer": /O=sample/OU=sample/CN=sample} ``` Does anyone have a idea how the contitional syntax could be used to get a quoted string when a variable is filled but a not quoted string 'null' when not? Best regards, lineconnect

3 2

Getting error only when *not* running in debug mode....
by Mark J. Bobak 18 Jun '21

18 Jun '21

Hi all, I've been a happy FreeRadius user for over 3 years now. I have had 3.0.13 running for that entire time with no complaints. (I've been using it w/ a Sonicwall to do 2-factor authentication for VPN login.) Recently, I've been revisiting the installation, and I thought, rather than making changes to a very stable and reliable system, I'd spin up a new installation with the latest version of FreeRadius (3.0.23). So, my new server is running Ubuntu 20.04 and using the NetworkRadius packages to install freeradius 3.0.23. I have also installed libpam-google-authenticatior, and integrated it according to these steps: https://networkjutsu.com/freeradius-google-authenticator/ This seems to have worked fine. I was running freeradius manually, with debug (-X) enabled, and everything seemed to be working fine. sudo /usr/sbin/freeradius -X So, I killed freeradius (CTRL-C), and tried: sudo service freeradius start It started up fine. But, now when I try authenticating (using radtest): radtest mbobak redacted123456 localhost:1812 0 'redacted' I get Access-Rejected Looking at the log file, /var/log/freeradius/radius.log, I see: Wed Jun 16 22:42:54 2021 : Info: Ready to process requests Wed Jun 16 22:43:27 2021 : ERROR: (0) pam: ERROR: PAM conversation failed Wed Jun 16 22:43:27 2021 : ERROR: (0) pam: ERROR: Error "Read-only file system" while writing config Wed Jun 16 22:43:27 2021 : ERROR: (0) pam: ERROR: pam_authenticate failed: Authentication failure Wed Jun 16 22:43:27 2021 : Auth: (0) Login incorrect (pam: PAM conversation failed): [mbobak/Akosama30404615] (from client localhost port 0) The only read-only filesystems do not appear to be relevant to the freeradius installation: mount | grep ro, tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) /var/lib/snapd/snaps/amazon-ssm-agent_3552.snap on /snap/amazon-ssm-agent/3552 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core18_1997.snap on /snap/core18/1997 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/lxd_19647.snap on /snap/lxd/19647 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/snapd_12057.snap on /snap/snapd/12057 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core18_2066.snap on /snap/core18/2066 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/lxd_20326.snap on /snap/lxd/20326 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/snapd_12159.snap on /snap/snapd/12159 type squashfs (ro,nodev,relatime,x-gdu.hide) But, even though it's reporting a read-only filesystem error, I'm thinking it could be a permission problem on some file? But, I'm really baffled by the system working when I run freeradius manually, but only errors when I run it from the service. Any help would be appreciated. Thanks, -Mark

3 6

freeradius with perl , have Discarding duplicate request from client nas_1 port 58159 - ID: 30 due to delayed response ,when reject
by Muhammed Buvaydani 18 Jun '21

18 Jun '21

hello , I have freeradius 3.x where I enabled Perl module for authentication, I noticed that my freeradius return this error in debug mode Discarding duplicate request from client nas_1 port 58159 - ID: 30 due to delayed response I thought that is because of my authentication script but then I disabled the authentication and configured my Perl to reject to all users without any query or authentication (just for checking ) but still, I have the same error Discarding duplicate request from client nas_1 port 58159 - ID: 30 due to delayed response this is my perl script use strict; use vars qw(%RAD_REQUEST %RAD_REPLY %RAD_CHECK); use IO::Socket; use locale; use POSIX; use PHP::Serialization qw(serialize unserialize); use LWP::Simple; use Sys::Syslog; setlocale(LC_ALL, 'C'); use constant RLM_MODULE_REJECT=> 0;# /* immediately reject the request */ use constant RLM_MODULE_FAIL=> 1;# /* module failed, don't reply */ use constant RLM_MODULE_OK=> 2;# /* the module is OK, continue */ use constant RLM_MODULE_HANDLED=> 3;# /* the module handled the request, so stop. */ use constant RLM_MODULE_INVALID=> 4;# /* the module considers the request invalid. */ use constant RLM_MODULE_USERLOCK=> 5;# /* reject the request (user is locked out) */ use constant RLM_MODULE_NOTFOUND=> 6;# /* user not found */ use constant RLM_MODULE_NOOP=> 7;# /* module succeeded without doing anything */ use constant RLM_MODULE_UPDATED=> 8;# /* OK (pairs modified) */ use constant RLM_MODULE_NUMCODES=> 9;# /* How many return codes there are */ my $splynx; my $answer; my $contents; my $request; my $ua = LWP::UserAgent->new(); my $res; sub authorize { return RLM_MODULE_REJECT; } sub authenticate { return RLM_MODULE_REJECT; } as you see I configured my Perl script to only reject users, but in debug mode, I have this warning, (12) Received Access-Request Id 148 from 104.46.67.10:58063 to 44.118.166.12:1812 length 123 (12) Service-Type = Framed-User (12) Framed-Protocol = PPP (12) NAS-Port = 15730188 (12) NAS-Port-Type = Ethernet (12) User-Name = "test2" (12) Calling-Station-Id = "00:0C:29:6E:F3:2F" (12) NAS-Port-Id = "vlan3800" (12) User-Password = "test2" (12) NAS-Identifier = "00:0C:29:D5:7F:74" (12) NAS-IP-Address = 104.46.67.10 (12) # Executing section authorize from file /etc/freeradius/3.0/sites-enabled/splynx (12) authorize { (12) update control { (12) Auth-Type := Accept (12) } # update control = noop (12) [preprocess] = ok (12) [mschap] = noop (12) eap: No EAP-Message, not doing EAP (12) [eap] = noop (12) perl: $RAD_REQUEST{'User-Name'} = &request:User-Name -> 'test2' (12) perl: $RAD_REQUEST{'User-Password'} = &request:User-Password -> 'test2' (12) perl: $RAD_REQUEST{'NAS-IP-Address'} = &request:NAS-IP-Address -> '104.46.67.10' (12) perl: $RAD_REQUEST{'NAS-Port'} = &request:NAS-Port -> '15730188' (12) perl: $RAD_REQUEST{'Service-Type'} = &request:Service-Type -> 'Framed-User' (12) perl: $RAD_REQUEST{'Framed-Protocol'} = &request:Framed-Protocol -> 'PPP' (12) perl: $RAD_REQUEST{'Calling-Station-Id'} = &request:Calling-Station-Id -> '00:0C:29:6E:F3:2F' (12) perl: $RAD_REQUEST{'NAS-Identifier'} = &request:NAS-Identifier -> '00:0C:29:D5:7F:74' (12) perl: $RAD_REQUEST{'NAS-Port-Type'} = &request:NAS-Port-Type -> 'Ethernet' (12) perl: $RAD_REQUEST{'Event-Timestamp'} = &request:Event-Timestamp -> 'Jun 18 2021 20:10:15 IST' (12) perl: $RAD_REQUEST{'NAS-Port-Id'} = &request:NAS-Port-Id -> 'vlan3800' (12) perl: $RAD_CHECK{'Auth-Type'} = &control:Auth-Type -> 'Accept' (12) perl: $RAD_CONFIG{'Auth-Type'} = &control:Auth-Type -> 'Accept' (12) perl: &request:Event-Timestamp = $RAD_REQUEST{'Event-Timestamp'} -> 'Jun 18 2021 20:10:15 IST' (12) perl: &request:User-Name = $RAD_REQUEST{'User-Name'} -> 'test2' (12) perl: &request:Calling-Station-Id = $RAD_REQUEST{'Calling-Station-Id'} -> '00:0C:29:6E:F3:2F' (12) perl: &request:Service-Type = $RAD_REQUEST{'Service-Type'} -> 'Framed-User' (12) perl: &request:NAS-Port-Id = $RAD_REQUEST{'NAS-Port-Id'} -> 'vlan3800' (12) perl: &request:NAS-IP-Address = $RAD_REQUEST{'NAS-IP-Address'} -> '104.46.67.10' (12) perl: &request:NAS-Identifier = $RAD_REQUEST{'NAS-Identifier'} -> '00:0C:29:D5:7F:74' (12) perl: &request:User-Password = $RAD_REQUEST{'User-Password'} -> 'test2' (12) perl: &request:Framed-Protocol = $RAD_REQUEST{'Framed-Protocol'} -> 'PPP' (12) perl: &request:NAS-Port-Type = $RAD_REQUEST{'NAS-Port-Type'} -> 'Ethernet' (12) perl: &request:NAS-Port = $RAD_REQUEST{'NAS-Port'} -> '15730188' (12) perl: &control:Auth-Type = $RAD_CHECK{'Auth-Type'} -> 'Accept' (12) [perl] = reject (12) } # authorize = reject (12) Using Post-Auth-Type Reject (12) # Executing group from file /etc/freeradius/3.0/sites-enabled/splynx (12) Post-Auth-Type REJECT { (12) attr_filter.access_reject: EXPAND %{User-Name} (12) attr_filter.access_reject: --> test2 (12) attr_filter.access_reject: Matched entry DEFAULT at line 11 (12) [attr_filter.access_reject] = updated (12) [eap] = noop (12) policy remove_reply_message_if_eap { (12) if (&reply:EAP-Message && &reply:Reply-Message) { (12) if (&reply:EAP-Message && &reply:Reply-Message) -> FALSE (12) else { (12) [noop] = noop (12) } # else = noop (12) } # policy remove_reply_message_if_eap = noop (12) } # Post-Auth-Type REJECT = updated (12) Delaying response for 1.000000 seconds Waking up in 0.3 seconds. Waking up in 0.6 seconds. (12) (12) Discarding duplicate request from client nas_1 port 58063 - ID: 148 due to delayed response Waking up in 0.6 seconds. (12) (12) Discarding duplicate request from client nas_1 port 58063 - ID: 148 due to delayed response Waking up in 0.3 seconds. (12) Sending delayed response in the other hand when I am accepting all users, I did not get that warning, this warning is just shown when rejecting user, as I said there is no query or anything else, thank you very much in advance

2 3

Logrotate config from Networkradius CentOS package breaks other logrotate configs
by Sven Scharf 18 Jun '21

18 Jun '21

Hi, I'm currently using the CentOS Radius packages provided by https://networkradius.com/packages/ for an OracleLinux 8 x86_64: Installed Packages Name : freeradius Version : 3.0.23 Release : 1 Architecture : x86_64 Size : 8.0 M Source : freeradius-3.0.23-1.src.rpm Repository : @System >From repo : networkradius-Project Summary : High-performance and highly configurable free RADIUS server URL : http://www.freeradius.org/ License : GPLv2+ and LGPLv2+ Description : The FreeRADIUS Server Project is a high performance and highly configurable [...] /etc/logrotate.d/radiusd contains settings outside of a logfile scope. e.g. su radiusd radiusd Sadly this affects all other logrotate configs after the radiusd config file, e.g. samba or sssd. Which now get a permission denied error as the radiusd user isn't allowed to rotate those logfiles. As this config file comes from the freeradius package I don't like to modify it. Is there any chance that the logrotate config of the package gets fixed? Thanks, Sven

4 5

ARTICLE: Your network will fail. You just don't know when, or how.
by Network RADIUS 18 Jun '21

18 Jun '21

** Why you should design for a worst case scenario --------------------------------------------- If you live in an earthquake zone, it’s important to engineer buildings to survive an earthquake. You don’t know when an earthquake will happen, or where exactly, or how big it’s going to be, but you know that it will happen at some point during the lifetime of the building. And the consequences of not earthquake proofing can be deadly. The same goes for your critical network infrastructure. At some point, some part of your network will go down. The consequences are not usually deadly, but it can feel that way when it’s happening to you. Read the full article... https://networkradius.com/articles/2021/06/09/why-you-should-design-for-a-w… ** Sign up to get this content directly --------------------------------------------- Want to get these articles in all their HTML glory? Sign up here: http://eepurl.com/hwuWrn ** Need RADIUS help? --------------------------------------------- Get commercial support from the team behind FreeRADIUS. https://networkradius.com/contact/ ** What is the relationship between Network RADIUS and FreeRADIUS? ---------------------------------------------- FreeRADIUS is an open source implementation of the RADIUS protocol and was written by Alan DeKok in 1999. Network RADIUS is a private, for-profit company founded by Alan DeKok which provides commercial support for FreeRADIUS. The Network RADIUS team has been the primary contributor to FreeRADIUS for the last 20 years. The FreeRADIUS mailing list, wiki, and documentation are all moderated and maintained by the Network RADIUS team. FreeRADIUS has always been, and will always continue to be, open source. The Network RADIUS team provides commercial support to paying clients, and free product development for the FreeRADIUS community at large. All of our software development for FreeRADIUS is integrated into the Open Source platform, and will always continue to be.

1 0

Can I use Freeradius DHCP server to allocate fixed IP to given 802.1X ?
by Olivier 18 Jun '21

18 Jun '21

Hello, In a BYOD context where each user may own severaldevices, is it possible to configure a fixed table such as bellow (either simple text file or database table) and have a single fixed private addresses being allocated to each 802.1X identity ? 802.1x ID Password IP user001 secret01 192.168.1.101 user002 superpwd02 192.168.1.102 If a device owner connects a second device providing the same 802.1 identity, I would like the first device to be kicked off the network. Could it be possible with latest Freeradius ? Comments ? Suggestions ? Best regards

2 1

Do not send Accounting-Response
by Strong, Mark 18 Jun '21

18 Jun '21

Weird question here, want to stop freeradius sending an Accounting-Response, I assume it's probably possible since it's like a Lego set, but how is best/easiest way of doing it on a per NAS basis. Why you would want to do such a thing, well I'll have more info on that tomorrow after I've spoken with the Telco. At the moment I just want to know if it's possible and best way of doing it. Mark. ________________________________ This e-mail message is for the sole use of the intended recipient(s) and may contain confidential and privileged information of Transaction Network Services. Any unauthorized reviews, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. --------------------------------------------------------------------------------------- This email has been scanned for email related threats and delivered safely by Mimecast. For more information please visit http://www.mimecast.com ---------------------------------------------------------------------------------------

2 5

FreeRADIUS Authentication with AD Without Joining AD
by Vertigo Altair 18 Jun '21

18 Jun '21

Hi! I'm trying to use FreeRADIUS with an Active Directory Server. I've read the documentations but the server that FreeRADIUS runs has to join the Active Directory as a client. Is there any way to authenticate users with AD without joining the AD server? P.S.: I'm using MSCHAP protocol.

4 5

Calling-Station-Id not received by server : how can i solve that?
by Wilfried Spillemaeckers 17 Jun '21

17 Jun '21

I have a freeradius server that I am trying to test for Mac Auth with NTRadping tool. When I use radclient on the server itself there is no issue. However when I use NTRadping from a PC the server appears not to receive the Calling-Station-Id. If I remove the authorized_macs part I can use NTRadping (meaning using simply a user/password combination it works, but I want to use Mac Auth). Below the debug info from freeradius -X Note that the info says "invalid user" although that user is perfectly valid and as i said the system works for this user when i simply remove the authorize_macs code in default. Help would be appreciated.... Ready to process requests (0) Received Access-Request Id 32 from 192.168.0.101:53887 to 192.168.0.10:1812 length 95 (0) User-Name = "wilfried" (0) CHAP-Password = 0x242c6f4547017ed4d3b33542f148ce0515 (0) NAS-IP-Address = 255.255.255.255 (0) NAS-Port = 0 (0) Service-Type = 0 (0) Framed-IP-Address = 255.255.255.255 (0) NAS-Port-Type = Async (0) # Executing section authorize from file /etc/freeradius/3.0/sites-enabled/default (0) authorize { (0) policy filter_username { (0) if (&User-Name) { (0) if (&User-Name) -> TRUE (0) if (&User-Name) { (0) if (&User-Name =~ / /) { (0) if (&User-Name =~ / /) -> FALSE (0) if (&User-Name =~ /@[^@]*@/ ) { (0) if (&User-Name =~ /@[^@]*@/ ) -> FALSE (0) if (&User-Name =~ /\.\./ ) { (0) if (&User-Name =~ /\.\./ ) -> FALSE (0) if ((&User-Name =~ /@/) && (&User-Name !~ /(a)(.+)\.(.+)$/)) { (0) if ((&User-Name =~ /@/) && (&User-Name !~ /(a)(.+)\.(.+)$/)) -> FALSE (0) if (&User-Name =~ /\.$/) { (0) if (&User-Name =~ /\.$/) -> FALSE (0) if (&User-Name =~ /(a)\./) { (0) if (&User-Name =~ /(a)\./) -> FALSE (0) } # if (&User-Name) = notfound (0) } # policy filter_username = notfound (0) policy filter_password { (0) if (&User-Password && (&User-Password != "%{string:User-Password}")) { (0) if (&User-Password && (&User-Password != "%{string:User-Password}")) -> FALSE (0) } # policy filter_password = notfound (0) [preprocess] = ok (0) policy rewrite_calling_station_id { (0) if (&Calling-Station-Id && (&Calling-Station-Id =~ /^([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9 a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})$/i)) { (0) if (&Calling-Station-Id && (&Calling-Station-Id =~ /^([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9 a-f]{2})[^0-9a-f]?([0-9a-f]{2})[^0-9a-f]?([0-9a-f]{2})$/i)) -> FALSE (0) else { (0) [noop] = noop (0) } # else = noop (0) } # policy rewrite_calling_station_id = noop (0) authorized_macs: EXPAND %{Calling-Station-ID} (0) authorized_macs: --> (0) [authorized_macs] = noop (0) if (!EAP-Message) { (0) if (!EAP-Message) -> TRUE (0) if (!EAP-Message) { (0) authorized_macs: EXPAND %{Calling-Station-ID} (0) authorized_macs: --> (0) [authorized_macs] = noop (0) if (!ok) { (0) if (!ok) -> TRUE (0) if (!ok) { (0) [reject] = reject (0) } # if (!ok) = reject (0) } # if (!EAP-Message) = reject (0) } # authorize = reject (0) Invalid user: [wilfried] (from client nneos port 0) (0) Using Post-Auth-Type Reject (0) # Executing group from file /etc/freeradius/3.0/sites-enabled/default (0) Post-Auth-Type REJECT { (0) attr_filter.access_reject: EXPAND %{User-Name} (0) attr_filter.access_reject: --> wilfried (0) attr_filter.access_reject: Matched entry DEFAULT at line 11 (0) [attr_filter.access_reject] = updated (0) } # Post-Auth-Type REJECT = updated (0) Delaying response for 1.000000 seconds Waking up in 0.3 seconds. Waking up in 0.6 seconds. (0) Sending delayed response (0) Sent Access-Reject Id 32 from 192.168.0.10:1812 to 192.168.0.101:53887 length 20 Waking up in 3.9 seconds. (0) Cleaning up request packet ID 32 with timestamp +7 Ready to process requests -- Wilfried Spillemaeckers Vichteplaats 20 8570 Vichte wilfried(a)spillemaeckers.net <mailto:wilfried@spillemaeckers.net> Tel. +32 5637 2766 Mob. +32 474 860 014

2 1