- Freeradius-Users - lists.freeradius.org

TACACS+ is now in the v4.0.x branch
by Alan DeKok 06 Feb '17

06 Feb '17

I've just committed a patch to add TACACS+ to the v4.0.x branch: https://github.com/FreeRADIUS/freeradius-server/commit/6a59647304955d984f2e… It's experimental, and works in basic tests. Minor things in the configuration are likely to change as we update v4, but the basic TACACS+ functionality should remain the same. Thanks to Alexander Clouter for doing the work. He had to read the TACACS+ proposed standard document, and figure out what it said: not much... The implementation is inter-operable with the switches we have access to, but you never now. People interested in trying the bleeding edge can now use TACACS+ in the v4 branch. Alan DeKok.

4 6

limiting fail timeout for an LDAP module
by Zenon Mousmoulas 06 Feb '17

06 Feb '17

Hi, I am working with a peculiar LDAP backend which, from time to time, will take upwards of 10 seconds to respond to a search request. I know that is what needs fixing, but let's say I have to live with it for now. There is a second LDAP backend which I can use a backup when the first one goes nuts. So I'm thinking let's setup two LDAP module instances and use them in a redundant group. For this to be usable for EAP authentication however, I need to make sure freeradius fails the first LDAP module within some (short) time limit. I have thus been trying to tweak the first LDAP module instance settings in order to achieve that. After experimenting with these settings: options.res_timeout options.srv_timelimit pool.start I found that if I set pool.start=0 and, say, options.res_timeout=2 freeradius reconnects (retrying the search once) and fails the module after a total of 4 seconds: Fri Feb 3 18:29:43 2017 : Debug: (1) ldap_first_bad: Waiting for search result... Fri Feb 3 18:29:44 2017 : Debug: Waking up in 0.4 seconds. Fri Feb 3 18:29:44 2017 : Debug: Waking up in 0.7 seconds. Fri Feb 3 18:29:45 2017 : Debug: Waking up in 1.1 seconds. Fri Feb 3 18:29:45 2017 : Debug: rlm_ldap: Closing libldap handle 0x7fa240000cb0 Fri Feb 3 18:29:45 2017 : Debug: rlm_ldap (ldap_first_bad): Reconnecting (0) Fri Feb 3 18:29:45 2017 : Debug: rlm_ldap (ldap_first_bad): Connecting to ldaps://xxxxxxxx Fri Feb 3 18:29:45 2017 : Debug: rlm_ldap (ldap_first_bad): New libldap handle 0x7fa238000da0 Fri Feb 3 18:29:45 2017 : Debug: rlm_ldap (ldap_first_bad): Waiting for bind result... Fri Feb 3 18:29:45 2017 : Debug: rlm_ldap (ldap_first_bad): Bind successful Fri Feb 3 18:29:45 2017 : WARNING: (1) ldap_first_bad: Search failed: Timed out while waiting for server to respond. Got new socket, retrying... Fri Feb 3 18:29:45 2017 : Debug: (1) ldap_first_bad: Waiting for search result... Fri Feb 3 18:29:46 2017 : Debug: Waking up in 1.6 seconds. Fri Feb 3 18:29:47 2017 : Debug: rlm_ldap: Closing libldap handle 0x7fa238000da0 Fri Feb 3 18:29:47 2017 : Debug: rlm_ldap (ldap_first_bad): Reconnecting (0) Fri Feb 3 18:29:47 2017 : Debug: rlm_ldap (ldap_first_bad): Connecting to ldaps://xxxxxxxx Fri Feb 3 18:29:47 2017 : Debug: rlm_ldap (ldap_first_bad): New libldap handle 0x7fa238000da0 Fri Feb 3 18:29:47 2017 : Debug: rlm_ldap (ldap_first_bad): Waiting for bind result... Fri Feb 3 18:29:47 2017 : Debug: rlm_ldap (ldap_first_bad): Bind successful Fri Feb 3 18:29:47 2017 : WARNING: (1) ldap_first_bad: Search failed: Timed out while waiting for server to respond. Got new socket, retrying... Fri Feb 3 18:29:47 2017 : Debug: (1) ldap_first_bad: Waiting for search result... Fri Feb 3 18:29:48 2017 : Debug: Waking up in 2.5 seconds. Fri Feb 3 18:29:48 2017 : Error: (1) Ignoring duplicate packet from client localhost port 34423 - ID: 11 due to unfinished request in component authorize module ldap_first_bad Fri Feb 3 18:29:48 2017 : Debug: Waking up in 1.9 seconds. Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap: Closing libldap handle 0x7fa238000da0 Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): Reconnecting (0) Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): Connecting to ldaps://xxxxxxxx Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): New libldap handle 0x7fa238000da0 Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): Waiting for bind result... Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): Bind successful Fri Feb 3 18:29:49 2017 : WARNING: (1) ldap_first_bad: Search failed: Timed out while waiting for server to respond. Got new socket, retrying... Fri Feb 3 18:29:49 2017 : ERROR: (1) ldap_first_bad: Hit reconnection limit Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): Released connection (0) Fri Feb 3 18:29:49 2017 : Info: rlm_ldap (ldap_first_bad): Need 1 more connections to reach 10 spares Fri Feb 3 18:29:49 2017 : Info: rlm_ldap (ldap_first_bad): Opening additional connection (2), 1 of 30 pending slots used Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): Connecting to ldaps://xxxxxxxx Fri Feb 3 18:29:49 2017 : Debug: rlm_ldap (ldap_first_bad): New libldap handle 0x7fa2380215b0 Fri Feb 3 18:29:50 2017 : Debug: rlm_ldap (ldap_first_bad): Waiting for bind result... Fri Feb 3 18:29:50 2017 : Debug: rlm_ldap (ldap_first_bad): Bind successful Fri Feb 3 18:29:50 2017 : Debug: (1) modsingle[authorize]: returned from ldap_first_bad (rlm_ldap) Fri Feb 3 18:29:50 2017 : Debug: (1) [ldap_first_bad] = fail Fri Feb 3 18:29:50 2017 : Debug: (1) modsingle[authorize]: calling ldap_backup (rlm_ldap) I am wondering if this is as good as it gets or if there are other things to tweak or to try, to get a shorter timeout in this particular case, perhaps avoiding the side effect of start=0 documented therein (Set to 0 to allow the server to start without the directory being available). This is on freeradius 3.0.12. Thanks for any insight, Z.

3 4

Accounting Packets and Anonymous Identity
by Selahattin Cilek 05 Feb '17

05 Feb '17

I have been checking the traffic between NASes and FreeRADIUS (2.2.9) and I have come across accounting packets with the User-Name field set to "anonymous." Sun Nov 13 02:41:50 2016 Acct-Session-Id = "57B6F41F-000014D2" Acct-Status-Type = Start Acct-Authentic = RADIUS User-Name = "anonymous" NAS-Identifier = "KAT_8_MERDIVEN" Called-Station-Id = "DC-9F-DB-34-CF-B4:TDV.NET" NAS-Port-Type = Wireless-802.11 NAS-Port = 0 Calling-Station-Id = "F8-16-54-1E-AB-2C" Connect-Info = "CONNECT 0Mbps 802.11b" Acct-Session-Id = "57B6F41F-000014D2" NAS-IP-Address = 192.168.0.38 FreeRADIUS-Acct-Session-Start-Time = "Nov 13 2016 02:41:50 EET" Acct-Unique-Session-Id = "6c4322c41296866a" Timestamp = 1478997710 1. This server does not use MySQL and keeps the accounting data in plain text files. If I were using MySQL as the back-end, would I still see the user's name as "anonymous" in the "radacct.username" field? 2. Is it possible to find the true identity of the user by means of reading some files or an SQL query and using the other data provided in the packet such as Acct-Session-Id, Calling-Station-Id or Acct-Unique-Session-Id etc? --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

7 13

v3.0.12 crashed (load testing)
by Chris Howley 05 Feb '17

05 Feb '17

Hi, I'm load testing freeradius 3.0.12 using GNU parallel and eapol_test. I'm trying to integrate freeradius with Active Directory. After ten hours of testing the freeradius server crashed (see below). The system is using the following: CentOS Linux release 7.2.1511 parallel-20160222-1.el7.noarch wpa_supplicant-2.0-17.el7_1.x86_64 samba-common-4.2.10-7 freeradius-3.0.12-2.el7 (built RPMS using gcc version 4.8.5) I can share the output from the debugger off-list. Help in fixing this issue would appreciated. Thanks, Chris Howley Sat Feb 4 20:01:47 2017 : Error: ASSERT FAILED src/main/connection.c[827]: pool->active == pool->num CAUGHT SIGNAL: Aborted Backtrace of last 39 frames: /usr/lib64/freeradius/libfreeradius-radius.so(fr_fault+0xa7)[0x7f48dabb0397] /usr/lib64/freeradius/libfreeradius-server.so(rad_assert_fail+0x29)[0x7f48dae09b59] /usr/sbin/radiusd[0x42c80c] /usr/lib64/freeradius/rlm_mschap.so(do_auth_wbclient+0x11a)[0x7f48d3f160aa] /usr/lib64/freeradius/rlm_mschap.so(+0x2301)[0x7f48d3f12301] /usr/lib64/freeradius/rlm_mschap.so(+0x4bc1)[0x7f48d3f14bc1] /usr/sbin/radiusd[0x426faf] /usr/sbin/radiusd[0x427ad9] /usr/sbin/radiusd[0x42688e] /usr/sbin/radiusd[0x427ad9] /usr/sbin/radiusd[0x42688e] /usr/sbin/radiusd(modcall+0x56)[0x427b96] /usr/sbin/radiusd(indexed_modcall+0xad)[0x42238d] /usr/lib64/freeradius/rlm_eap_mschapv2.so(+0x1dfb)[0x7f48cfa6edfb] /usr/lib64/freeradius/rlm_eap.so(+0x3795)[0x7f48d5dc4795] /usr/lib64/freeradius/rlm_eap.so(eap_method_select+0xb9)[0x7f48d5dc4b09] /usr/lib64/freeradius/rlm_eap.so(+0x2b36)[0x7f48d5dc3b36] /usr/sbin/radiusd[0x426faf] /usr/sbin/radiusd[0x427ad9] /usr/sbin/radiusd[0x42688e] /usr/sbin/radiusd(modcall+0x56)[0x427b96] /usr/sbin/radiusd(indexed_modcall+0xad)[0x42238d] /usr/sbin/radiusd(rad_authenticate+0x7be)[0x4112de] /usr/sbin/radiusd(rad_virtual_server+0x272)[0x411802] /usr/lib64/freeradius/rlm_eap_peap.so(eappeap_process+0x6d3)[0x7f48cfc75833] /usr/lib64/freeradius/rlm_eap_peap.so(+0x1c0a)[0x7f48cfc73c0a] /usr/lib64/freeradius/rlm_eap.so(+0x3795)[0x7f48d5dc4795] /usr/lib64/freeradius/rlm_eap.so(eap_method_select+0xb9)[0x7f48d5dc4b09] /usr/lib64/freeradius/rlm_eap.so(+0x2b36)[0x7f48d5dc3b36] /usr/sbin/radiusd[0x426faf] /usr/sbin/radiusd[0x427ad9] /usr/sbin/radiusd[0x42688e] /usr/sbin/radiusd(modcall+0x56)[0x427b96] /usr/sbin/radiusd(indexed_modcall+0xad)[0x42238d] /usr/sbin/radiusd(rad_authenticate+0x7be)[0x4112de] /usr/sbin/radiusd[0x4374c3] /usr/sbin/radiusd[0x42f443] /lib64/libpthread.so.0(+0x7dc5)[0x7f48d947edc5] /lib64/libc.so.6(clone+0x6d)[0x7f48d8d2eced] Calling: gdb -silent -x /etc/raddb/panic.gdb /usr/sbin/radiusd 47031 2>&1 | tee /var/log/radius/gdb-radiusd-47031.log Temporarily setting PR_DUMPABLE to 1 Resetting PR_DUMPABLE to 0 Panic action exited with 0 _EXIT(0) CALLED src/lib/debug.c[743]

2 1

getting error such max_requests set too low in configurations
by manjunath uthappa ponnachana 04 Feb '17

04 Feb '17

Hi,Getting following error when using  free radius under heavy load,Thu Feb  2 20:18:00 2017 : Error: Dropping request (13057 is too many): from client  port 41215 - ID: 244Thu Feb  2 20:18:00 2017 : Info: WARNING: Please check the configuration file.     The value for 'max_requests' is probably set too low. Thu Feb  2 20:18:00 2017 : Error: Dropping request (13057 is too many): from client  port 40991 - ID: 192Thu Feb  2 20:18:00 2017 : Info: WARNING: Please check the configuration file.     The value for 'max_requests' is probably set too low.Please let me know, what might be the problem and resolution for the problem. Thanks & regardsManjunath 

2 1

Garbage password from pam_radius_auth with skip_passwd set
by Ilkka Virta 03 Feb '17

03 Feb '17

I'm using pam_radius_auth with 'skip_passwd' to talk to FreeRADIUS, and seem to be receiving garbage passwords in the initial request, instead of the empty password I expected. (USAGE says pam_radius_auth sends a "NULL" password, but I don't know if it means the User-Password field is to be zero-length, zero-filled, or nonexisting.) PAM config: auth required pam_radius_auth-1.4.0.so debug skip_passwd The User-Password contained in the initial request appears as 16 random-looking bytes: > ------------- freeradius -X > rad_recv: Access-Request packet from host 127.0.0.1 port 41394, id=210, length=72 > User-Name = "user" > User-Password = "\222\350)\2304Z@ \374\217G>߇<\t" > ... > > rlm_perl: test.pl: RAD_REQUEST: User-Password = '\222\350)\2304Z@ \374\217G>�?<\t' > rlm_perl: Added pair User-Password = \222\350)\2304Z@ \374\217G>�?<\t The "rlm_perl: test.pl" line comes from a perl script that just prints the received values, like example.pl. If I give an empty response to a password prompt, I get the empty password as expected: > ------------- freeradius -X > rad_recv: Access-Request packet from host 127.0.0.1 port 41394, id=211, length=71 > User-Name = "user" > User-Password = "" > > rlm_perl: test.pl: RAD_REQUEST: User-Password = '' > rlm_perl: Added pair User-Password = This works with both the initial password prompt if skip_passwd is not set, and in replies to any Access-Challenges sent later on. I don't think this is the expected behaviour given the documentation, any thoughts?

2 2

Logging proxy server
by Chris Taylor (chtaylo2) 03 Feb '17

03 Feb '17

1.) Is it possible to log the home_server which proxied a connection? Log today: radiusd[22590]: (436) Login OK: [Radius-ACE-Prob@REMOTE] (from client Radius-ACE-Prob port 0) [Source: 111.111.111.111] I’d like to be able to log --> [Proxy: home_server_A]. If not possible there, how about in post-proxy { post_proxy_log } Thanks

2 5

Re: Session-Timeout Problem
by Selahattin Cilek 03 Feb '17

03 Feb '17

-------- Forwarded Message -------- Subject: Re: Session-Timeout Problem Date: Thu, 2 Feb 2017 15:17:00 +0300 From: Selahattin ÇİLEK <selahattin_cilek(a)hotmail.com><mailto:selahattin_cilek@hotmail.com> To: Brian Candler <b.candler(a)pobox.com><mailto:b.candler@pobox.com> On 02.02.2017 13:45, Brian Candler wrote: On 02/02/2017 09:24, Selahattin Cilek wrote: When I set the "Session-Timeout := 600" for a user, the NAS is supposed to renew the session every 10 minutes. My Unifi AP recognises the attribute and actually DOES terminate the first session when it times out after 10 minutes. The problem is that it terminates only the first session, the second session lasts until the NAS reboots, the user logs out or shuts down the host. This means a user could exceed his quota if he keeps his wireless connection alive. There are some users that exceed their 7GB weekly quota by 6 GBs! Should I blame the AP firmware for this or is it a bug in FreeRADIUS 2.2.8? That's very easy to determine. Use tcpdump / wireshark / radsniff to capture all the response from FreeRADIUS. - If FreeRADIUS *is* sending the Session-Timeout every time, then the bug is in the access point. - If FreeRADIUS *isn't* sending the Session-Timeout attribute sometimes, then the bug is in FreeRADIUS (or the way you have configured it) I don't believe FreeRADIUS is supposed to send Session-Timeout messages the to NAS, but the other way around. However, I would point out that there are much better ways of achieving your goal than kicking off users every 10 minutes, which is highly disruptive. No, it is not disruptive. The NAS is not supposed to first disconnect and then reconnect the user every 10 minutes, it is supposed to send usage statistics and request a re-authentication of the user. I have a script that checks network usage and decides whether or not to allow the user to be re-authenticated: Exec-Program-Wait = /usr/local/bin/bash /usr/local/etc/raddb/scripts/sql_datacounter_auth.sh scilek I need to keep track of network usage using FreeRADIUS and MySQL. 1. Use Radius Accounting to measure how much traffic users are using (with Interim-Accounting you will get periodic updates). Then kick the user off when the user reaches the download limit. The "Acct-Interim-Interval" informs the NAS of how frequently it should send update packets to the FreeRADIUS server and send the usage statistics incrementally. A user cannot be re-authenticated using this attribute. The updates do not occur during the second session anyway. The key is the "Session-Timeout" attribute. A user can be granted or denied access only before a new session starts. Unifi provides an HTTP/JSON API to do this. This shell script shows how to use it: https://www.ubnt.com/downloads/unifi/5.3.11/unifi_sh_api I do not want to use vendor scripts. I want to use FreeRADIUS, MySQL and my own scripts. "unifi_reconnect_sta" will kick off the user, to force them to reauthenticate. A NAS based solution will not work because I will have to configure each and every NAS on each and every site. What if I'd like to use some other NAS some other day? 2. The Unifi controller's mongodb database tracks how much bandwidth every user has consumed. So you could just periodically query that and kick off the abusers. I cannot have a separate machine for Unifi controller on the site. Besides, I might someday wanna keep track of network usage in a centralised database. 3. Use the Unifi's built-in bandwidth control features (User Groups / bandwidth limits). That's at the level of kbps not total GB per week. Still, people who have exceeded their quota could have a very low bandwidth limit applied. That will not work because it is not centralised. I have 30 APs on one site and the user can log in to any one of them. Regards, Brian. Thank you very much for the advice. ________________________________ [Avast logo] <https://www.avast.com/antivirus> This email has been checked for viruses by Avast antivirus software. www.avast.com<https://www.avast.com/antivirus> ________________________________ [Avast logo] <https://www.avast.com/antivirus> This email has been checked for viruses by Avast antivirus software. www.avast.com<https://www.avast.com/antivirus>

6 23

FreeRadius + OpenLDAP + MSCHAP2
by SolidSystems | Alex Grigorescu 03 Feb '17

03 Feb '17

Hello I am a system integrator that has just delivereded an Aruba WiFi solution to a customer. They have an infrastructure that is based on a OpenLDAP server with more than 10k active users. All the users have their passwords encripted using SSHA. We are currently trying to help them implement an 802.1x WiFi access network and we are having problems with Microsoft clients connecting. If we create a new user in the LDAP directory and store the password in Clear Text everything works fine. But the goal is to be able to do user logins using the existing paswords without installing any 3rd party software on the clients (which is an impossible task). Is there a way to make FreeRadius authenticate the users against OpenLDAP without having ClearText or NT Hash stored passwords? Best regards, Alex Ing. Alex GRIGORESCU Director Tehnic Solid Systems Brasov, 500059 Str. Lunga Nr. 200 Phone: +40 (368) 80.80.00 Fax: +40 (368) 80.20.80 Mobile: +40 (772) 20.20.02 E-mail: alex.grigorescu(a)solidsystems.ro<mailto:alex.grigorescu@solidsystems.ro> SolidSystems este marca inregistrata a SC Wi-Novation SRL Brasov [Description: Description: Description: Description: MCP(rgb)] [Description: Description: Description: HP AIS] Acest mesaj este adresat exclusiv destinatarului mentionat si poate contine informatii confidentiale si privilegiate. In cazul in care ati primit acest mesaj printr-o eroare, va rugam sa ne informati si sa il stergeti apoi din sistemul Dvs. SolidSystems nu este responsabila pentru eventualele pagube provocate de cunoasterea si/sau folosirea acestui mesaj de terti sau pentru destinatia eronata a mesajului This message is exclusively directed to the above mentioned recipient and may contain confidential and privileged information. Should you receive this message by error we kindly ask you to delete this message immediately. SolidSystems is not liable for any damages resulting from the knowledge and/or manipulation of this message by third parties or from the misdirection of the message.

2 1

FreeRADIUS v3.0.12 Error to Start
by Jose Quezada 02 Feb '17

02 Feb '17

Hello Dears, I have been installing freeradius v3.0.12 in a centos to prove it since I read that the founders recommended that version because it has many better ones. I admit that it has given me a lot of effort to get it works. I immediately wrote radiusd -XC to see that everything was fine, and so it was, but when I try "systemctl start / status radiusd" the service does not start. Some help? below i put the output. [root@centosLAB ~]# sudo systemctl status radiusd Unit radiusd.service could not be found. [root@centosLAB ~]# sudo systemctl start radiusd Failed to start radiusd.service: Unit not found. [root@centosLAB ~]# Thanks for advance, Jose

2 1