- Freeradius-Users - lists.freeradius.org

Building on RHEL 9
by g4-lisz＠tonarchiv.ch 29 Mar '25

29 Mar '25

Hi there Maybe someone here on the list has already done this and can help me: I have a hard time finding libtalloc-devel for Red Hat 9. libtalloc is already installed, but no headers... I'm really not a friend of this RHEL distro, but that's what our customer is using... Best, Till

5 12

accept all users, but conditionally
by Henrik SEKUJ 28 Mar '25

28 Mar '25

Hello, I am using freeradius for years with pppoe and I am very happy with it. I used default configurations with very little modifications, even using it for years I am having difficulties making some changes.This topic may be elaborated largely by the community, I read some similar, but I was not able to find exact details that I need.I use 'Simultaneous-Use' & 'Cleartext-Password' attributes and expiration module.Everything works fine Now I need, accept all requests, butIf user is authenticated send framed-pool=normal_poolif not send framed-pool=loginfailed_poolif expired send framed-pool=expired_pool (working now) My intention is to eliminate repeated login attempts in pppoe server.I am using a old version 3.0, not thinking to update please can anyone help me

2 1

Issue with disconnection between radsecproxy client and freeradius server
by James Wood 24 Mar '25

24 Mar '25

I'm not sure if this is a radsecproxy or freeradius issue so I've posted something similar in the radsecproxy list also, but I would appreciate it if you can advise. I am using radsecproxy 1.9.1 as a radsec TLS client on an openwrt (latest snapshot) embedded device, and freeradius 3.2.7. I have radsec in general working fine on this server but now trying to get radsec support on openwrt. radsecproxy initially connects just fine, but after 30 seconds it disconnects and then has a fit and spams the syslog forever until restart. It does this whether or not I connect a client to authenticate. I can authenticate a client just fine on radsec before that initial 30 second period so unsure what's going on here. It does seem like it's related to the idle_timeout setting, but according to the radsecproxy code it should just reconnect every 30s but can't. I don't want to set an idle_timeout of 0 ideally, would you agree this is not preferred behaviour? Debug log from freeradius: Listening on auth+acct proto tcp address * port 2083 (TLS) bound to server default Ready to process requests ... new connection request on TCP socket Listening on auth+acct from client (78.32.xx.xx, 44103) -> (*, 2083, virtual-server=default) Waking up in 0.2 seconds. (0) (TLS) RADIUS/TLS -Initiating new session (0) (TLS) RADIUS/TLS - Handshake state - before SSL initialization (0) (TLS) RADIUS/TLS - Handshake state - Server before SSL initialization (0) (TLS) RADIUS/TLS - Handshake state - Server before SSL initialization (0) (TLS) RADIUS/TLS - recv TLS 1.3 Handshake, ClientHello (0) (TLS) RADIUS/TLS - Handshake state - Server SSLv3/TLS read client hello (0) (TLS) RADIUS/TLS - send TLS 1.3 Handshake, ServerHello (0) (TLS) RADIUS/TLS - Handshake state - Server SSLv3/TLS write server hello (0) (TLS) RADIUS/TLS - send TLS 1.3 ChangeCipherSpec (0) (TLS) RADIUS/TLS - Handshake state - Server SSLv3/TLS write change cipher spec (0) (TLS) RADIUS/TLS - send TLS 1.3 Handshake, EncryptedExtensions (0) (TLS) RADIUS/TLS - Handshake state - Server TLSv1.3 write encrypted extensions (0) (TLS) RADIUS/TLS - send TLS 1.3 Handshake, Certificate (0) (TLS) RADIUS/TLS - Handshake state - Server SSLv3/TLS write certificate (0) (TLS) RADIUS/TLS - send TLS 1.3 Handshake, CertificateVerify (0) (TLS) RADIUS/TLS - Handshake state - Server TLSv1.3 write server certificate verify (0) (TLS) RADIUS/TLS - send TLS 1.3 Handshake, Finished (0) (TLS) RADIUS/TLS - Handshake state - Server SSLv3/TLS write finished (0) (TLS) RADIUS/TLS - Handshake state - Server TLSv1.3 early data (0) (TLS) RADIUS/TLS - Server : Need to read more data: TLSv1.3 early data (0) (TLS) RADIUS/TLS - In Handshake Phase Waking up in 0.2 seconds. (0) (TLS) RADIUS/TLS - Handshake state - Server TLSv1.3 early data (0) (TLS) RADIUS/TLS - recv TLS 1.3 Handshake, Finished (0) (TLS) RADIUS/TLS - Handshake state - Server SSLv3/TLS read finished (0) (TLS) RADIUS/TLS - Handshake state - SSL negotiation finished successfully (0) (TLS) RADIUS/TLS - Connection Established (0) TLS-Session-Cipher-Suite = "TLS_AES_256_GCM_SHA384" (0) TLS-Session-Version = "TLS 1.3" (0) (TLS) RADIUS/TLS - Application data. (0) (TLS) OpenSSL says that it needs to read more data. Waking up in 0.1 seconds. Waking up in 29.4 seconds. Reached idle timeout on socket auth+acct from client (78.32.xx.xx, 44103) -> (*, 2083, virtual-server=default) ... shutting down socket auth+acct from client (78.32.xx.xx, 44103) -> (*, 2083, virtual-server=default) ... cleaning up socket auth+acct from client (78.32.xx.xx, 44103) -> (*, 2083, virtual-server=default) Debug log from radseproxy for completeness: Sat Mar 22 12:43:01 2025 daemon.info radsecproxy[4861]: radsecproxy 1.9.1 starting Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: resolvehostport: (src info not available) -> 0.0.0.0 Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: tlsconnect: called from clientwr Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: udp server writer, waiting for signal Sat Mar 22 12:43:01 2025 daemon.info radsecproxy[4861]: tlsconnect: trying to open TLS connection to server myradsec (radsec.myradsec.xyz port 2083) Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: resolvehostport: 127.0.0.1 -> 127.0.0.1 Sat Mar 22 12:43:01 2025 daemon.info radsecproxy[4861]: disable_DF_bit: disabling DF bit (Linux variant) Sat Mar 22 12:43:01 2025 daemon.warn radsecproxy[4861]: createlistener: listening for udp on 127.0.0.1:1812 Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: resolvehostport: 127.0.0.1 -> 127.0.0.1 Sat Mar 22 12:43:01 2025 daemon.info radsecproxy[4861]: disable_DF_bit: disabling DF bit (Linux variant) Sat Mar 22 12:43:01 2025 daemon.warn radsecproxy[4861]: createlistener: listening for udp on 127.0.0.1:1813 Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: Connection up Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: verifyconfcert: verify certificate for host myradsec, subject CN=*.myradsec.xyz Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: matchtregex: matching *.myradsec.xyz Sat Mar 22 12:43:01 2025 daemon.debug radsecproxy[4861]: verifyconfcert: CN:/.myradsec\.xyz$/ matching for host myradsec (CN=*.myradsec.xyz) Sat Mar 22 12:43:01 2025 daemon.warn radsecproxy[4861]: tlsconnect: TLS connection to myradsec (radsec.myradsec.xyz port 2083), subject CN=*. myradsec.xyz up Sat Mar 22 12:43:31 2025 daemon.err radsecproxy[4861]: sslreadtimeout: SSL: error:0A000126:SSL routines::unexpected eof while reading Sat Mar 22 12:43:31 2025 daemon.info radsecproxy[4861]: sslreadtimeout: connection closed by remote host Sat Mar 22 12:43:31 2025 daemon.err radsecproxy[4861]: sslreadtimeout: SSL: error:0A000197:SSL routines::shutdown while in init Sat Mar 22 12:43:31 2025 daemon.err radsecproxy[4861]: sslreadtimeout: connection lost: No error information Sat Mar 22 12:43:31 2025 daemon.err radsecproxy[4861]: sslreadtimeout: SSL: error:0A000197:SSL routines::shutdown while in init Sat Mar 22 12:43:31 2025 daemon.err radsecproxy[4861]: sslreadtimeout: connection lost: No error information Sat Mar 22 12:43:31 2025 daemon.info radsecproxy[4861]: TLS Connection lost: Broken pipe Sat Mar 22 12:43:31 2025 daemon.info radsecproxy[4861]: TLS Connection lost: hang up Sat Mar 22 12:43:31 2025 daemon.info radsecproxy[4861]: TLS Connection lost: hang up Sat Mar 22 12:43:31 2025 daemon.info radsecproxy[4861]: TLS Connection lost: hang up Any idea how I can further debug or any suggestions? Thanks -- Visit purple.ai <https://purple.ai/> Purple on LinkedIn <https://uk.linkedin.com/company/purple-wifi> Email disclaimer <http://www.purple.ai/email-disclaimer/>

2 3

Unable to complete TLS handshake with iwd client
by Pat Pat 23 Mar '25

23 Mar '25

I am trying to use freeradius with WPA2-EAP. I have android clients working but using IWD it seems to fail with a TLS handshake error. Ready to process requests Threads: total/active/spare threads = 2/0/2 Waking up in 0.3 seconds. Thread 1 got semaphore Thread 1 handling request 0, (1 handled so far) (0) Received Access-Request Id 0 from 192.168.2.2:44444 to 192.168.2.1:1812 length 117 (0) User-Name = "as" (0) NAS-IP-Address = 192.168.2.2 (0) Called-Station-Id = "b4378330fc3b" (0) Calling-Station-Id = "5a5b3135062e" (0) NAS-Identifier = "b4378330fc3b" (0) NAS-Port = 29 (0) Framed-MTU = 1400 (0) NAS-Port-Type = Wireless-802.11 (0) EAP-Message = 0x02000007016173 (0) Message-Authenticator = 0x03105277799198b5f2c8e05d953827e8 (0) session-state: No State attribute (0) # Executing section authorize from file /etc/raddb/radiusd.conf (0) authorize { (0) modsingle[authorize]: calling eap (rlm_eap) (0) eap: Peer sent EAP Response (code 2) ID 0 length 7 (0) eap: EAP-Identity reply, returning 'ok' so we can short-circuit the rest of authorize (0) modsingle[authorize]: returned from eap (rlm_eap) (0) [eap] = ok (0) } # authorize = ok (0) Found Auth-Type = eap (0) # Executing group from file /etc/raddb/radiusd.conf (0) authenticate { (0) modsingle[authenticate]: calling eap (rlm_eap) (0) eap: Peer sent packet with method EAP Identity (1) (0) eap: Calling submodule eap_tls to process data (0) eap_tls: (TLS) TLS -Initiating new session (0) eap_tls: (TLS) TLS - Setting verify mode to require certificate from client (0) eap_tls: [eaptls start] = request (0) eap: Sending EAP Request (code 1) ID 1 length 10 (0) eap: EAP session adding &reply:State = 0xdfcd0373dfcc0e53 (0) modsingle[authenticate]: returned from eap (rlm_eap) (0) [eap] = handled (0) } # authenticate = handled (0) Using Post-Auth-Type Challenge (0) Post-Auth-Type sub-section not found. Ignoring. (0) session-state: Saving cached attributes (0) Framed-MTU = 1014 (0) Sent Access-Challenge Id 0 from 192.168.2.1:1812 to 192.168.2.2:44444 length 68 (0) EAP-Message = 0x0101000a0da000000000 (0) Message-Authenticator = 0x00000000000000000000000000000000 (0) State = 0xdfcd0373dfcc0e53057e01be00df4fb0 (0) Finished request Thread 1 waiting to be assigned a request (0) Cleaning up request packet ID 0 with timestamp +16 due to conflicting packet was received Waking up in 0.3 seconds. Thread 2 got semaphore Thread 2 handling request 1, (1 handled so far) (1) Received Access-Request Id 0 from 192.168.2.2:44444 to 192.168.2.1:1812 length 265 (1) User-Name = "as" (1) NAS-IP-Address = 192.168.2.2 (1) Called-Station-Id = "b4378330fc3b" (1) Calling-Station-Id = "5a5b3135062e" (1) NAS-Identifier = "b4378330fc3b" (1) NAS-Port = 29 (1) Framed-MTU = 1400 (1) State = 0xdfcd0373dfcc0e53057e01be00df4fb0 (1) NAS-Port-Type = Wireless-802.11 (1) EAP-Message = 0x020100890d00160301007e0100007a030367df7cae99f0e7e4fba4bb3181d9255fb4e4053b47f21d704f41904b9a089dc400002ac014c013003900330035002fc028c027006b0067003d003cc030c02f009f009e009d009cc0120016000a0100002700 (1) Message-Authenticator = 0x15eed9703faadf1d00a6dfe52a3e6807 (1) Restoring &session-state (1) &session-state:Framed-MTU = 1014 (1) # Executing section authorize from file /etc/raddb/radiusd.conf (1) authorize { (1) modsingle[authorize]: calling eap (rlm_eap) (1) eap: Peer sent EAP Response (code 2) ID 1 length 137 (1) eap: No EAP Start, assuming it's an on-going EAP conversation (1) modsingle[authorize]: returned from eap (rlm_eap) (1) [eap] = updated (1) } # authorize = updated (1) Found Auth-Type = eap (1) # Executing group from file /etc/raddb/radiusd.conf (1) authenticate { (1) modsingle[authenticate]: calling eap (rlm_eap) (1) eap: Removing EAP session with state 0xdfcd0373dfcc0e53 (1) eap: Previous EAP request found for state 0xdfcd0373dfcc0e53, released from the list (1) eap: Peer sent packet with method EAP TLS (13) (1) eap: Calling submodule eap_tls to process data (1) eap_tls: (TLS) EAP Continuing ... (1) eap_tls: (TLS) EAP Peer sent flags --- (1) eap_tls: (TLS) EAP Got final fragment (131 bytes) WARNING: (1) eap_tls: (TLS) EAP Total received record fragments (131 bytes), does not equal expected expected data length (0 bytes) (1) eap_tls: (TLS) EAP Verification says ok (1) eap_tls: (TLS) EAP Done initial handshake (1) eap_tls: (TLS) TLS - Handshake state [PINIT] - before SSL initialization (0) (1) eap_tls: (TLS) TLS - Handshake state [PINIT] - Server before SSL initialization (0) (TLS) Ignoring cbtls_msg call with pseudo content type 256, version 00000301 (1) eap_tls: (TLS) TLS - Handshake state [PINIT] - Server before SSL initialization (0) (TLS) Received 126 bytes of TLS data (TLS) 01 00 00 7a 03 03 67 df 7c ae 99 f0 e7 e4 fb a4 (TLS) bb 31 81 d9 25 5f b4 e4 05 3b 47 f2 1d 70 4f 41 (TLS) 90 4b 9a 08 9d c4 00 00 2a c0 14 c0 13 00 39 00 (TLS) 33 00 35 00 2f c0 28 c0 27 00 6b 00 67 00 3d 00 (TLS) 3c c0 30 c0 2f 00 9f 00 9e 00 9d 00 9c c0 12 00 (TLS) 16 00 0a 01 00 00 27 00 0a 00 10 00 0e 00 17 00 (TLS) 18 01 00 01 01 01 02 01 03 01 04 00 0d 00 0a 00 (TLS) 08 05 01 04 01 01 01 02 01 ff 01 00 01 00 (1) eap_tls: (TLS) TLS - recv TLS 1.3 Handshake, ClientHello (TLS) Ignoring cbtls_msg call with pseudo content type 256, version 00000303 (TLS) Received 2 bytes of TLS data (TLS) 02 28 (1) eap_tls: (TLS) TLS - send TLS 1.2 Alert, fatal handshake_failure ERROR: (1) eap_tls: (TLS) TLS - Alert write:fatal:handshake failure ERROR: (1) eap_tls: (TLS) TLS - Server : Error in error (1) eap_tls: Server preferred ciphers (by priority) (1) eap_tls: (TLS) [0] TLS_AES_256_GCM_SHA384 (1) eap_tls: (TLS) [1] TLS_AES_128_GCM_SHA256 (1) eap_tls: (TLS) [2] ECDHE-ECDSA-AES256-GCM-SHA384 (1) eap_tls: (TLS) [3] ECDHE-RSA-AES256-GCM-SHA384 (1) eap_tls: (TLS) [4] DHE-DSS-AES256-GCM-SHA384 (1) eap_tls: (TLS) [5] DHE-RSA-AES256-GCM-SHA384 (1) eap_tls: (TLS) [6] ECDHE-ECDSA-AES256-CCM (1) eap_tls: (TLS) [7] DHE-RSA-AES256-CCM (1) eap_tls: (TLS) [8] ECDHE-ECDSA-ARIA256-GCM-SHA384 (1) eap_tls: (TLS) [9] ECDHE-ARIA256-GCM-SHA384 (1) eap_tls: (TLS) [10] DHE-DSS-ARIA256-GCM-SHA384 (1) eap_tls: (TLS) [11] DHE-RSA-ARIA256-GCM-SHA384 (1) eap_tls: (TLS) [12] ADH-AES256-GCM-SHA384 (1) eap_tls: (TLS) [13] ECDHE-ECDSA-AES128-GCM-SHA256 (1) eap_tls: (TLS) [14] ECDHE-RSA-AES128-GCM-SHA256 (1) eap_tls: (TLS) [15] DHE-DSS-AES128-GCM-SHA256 (1) eap_tls: (TLS) [16] DHE-RSA-AES128-GCM-SHA256 (1) eap_tls: (TLS) [17] ECDHE-ECDSA-AES128-CCM (1) eap_tls: (TLS) [18] DHE-RSA-AES128-CCM (1) eap_tls: (TLS) [19] ECDHE-ECDSA-ARIA128-GCM-SHA256 (1) eap_tls: (TLS) [20] ECDHE-ARIA128-GCM-SHA256 (1) eap_tls: (TLS) [21] DHE-DSS-ARIA128-GCM-SHA256 (1) eap_tls: (TLS) [22] DHE-RSA-ARIA128-GCM-SHA256 (1) eap_tls: (TLS) [23] ADH-AES128-GCM-SHA256 (1) eap_tls: (TLS) [24] ECDHE-ECDSA-AES256-SHA384 (1) eap_tls: (TLS) [25] ECDHE-RSA-AES256-SHA384 (1) eap_tls: (TLS) [26] DHE-RSA-AES256-SHA256 (1) eap_tls: (TLS) [27] DHE-DSS-AES256-SHA256 (1) eap_tls: (TLS) [28] ECDHE-ECDSA-CAMELLIA256-SHA384 (1) eap_tls: (TLS) [29] ECDHE-RSA-CAMELLIA256-SHA384 (1) eap_tls: (TLS) [30] DHE-RSA-CAMELLIA256-SHA256 (1) eap_tls: (TLS) [31] DHE-DSS-CAMELLIA256-SHA256 (1) eap_tls: (TLS) [32] ADH-AES256-SHA256 (1) eap_tls: (TLS) [33] ADH-CAMELLIA256-SHA256 (1) eap_tls: (TLS) [34] ECDHE-ECDSA-AES128-SHA256 (1) eap_tls: (TLS) [35] ECDHE-RSA-AES128-SHA256 (1) eap_tls: (TLS) [36] DHE-RSA-AES128-SHA256 (1) eap_tls: (TLS) [37] DHE-DSS-AES128-SHA256 (1) eap_tls: (TLS) [38] ECDHE-ECDSA-CAMELLIA128-SHA256 (1) eap_tls: (TLS) [39] ECDHE-RSA-CAMELLIA128-SHA256 (1) eap_tls: (TLS) [40] DHE-RSA-CAMELLIA128-SHA256 (1) eap_tls: (TLS) [41] DHE-DSS-CAMELLIA128-SHA256 (1) eap_tls: (TLS) [42] ADH-AES128-SHA256 (1) eap_tls: (TLS) [43] ADH-CAMELLIA128-SHA256 (1) eap_tls: (TLS) [44] ECDHE-ECDSA-AES256-SHA (1) eap_tls: (TLS) [45] ECDHE-RSA-AES256-SHA (1) eap_tls: (TLS) [46] DHE-RSA-AES256-SHA (1) eap_tls: (TLS) [47] DHE-DSS-AES256-SHA (1) eap_tls: (TLS) [48] DHE-RSA-CAMELLIA256-SHA (1) eap_tls: (TLS) [49] DHE-DSS-CAMELLIA256-SHA (1) eap_tls: (TLS) [50] AECDH-AES256-SHA (1) eap_tls: (TLS) [51] ADH-AES256-SHA (1) eap_tls: (TLS) [52] ADH-CAMELLIA256-SHA (1) eap_tls: (TLS) [53] ECDHE-ECDSA-AES128-SHA (1) eap_tls: (TLS) [54] ECDHE-RSA-AES128-SHA (1) eap_tls: (TLS) [55] DHE-RSA-AES128-SHA (1) eap_tls: (TLS) [56] DHE-DSS-AES128-SHA (1) eap_tls: (TLS) [57] DHE-RSA-CAMELLIA128-SHA (1) eap_tls: (TLS) [58] DHE-DSS-CAMELLIA128-SHA (1) eap_tls: (TLS) [59] AECDH-AES128-SHA (1) eap_tls: (TLS) [60] ADH-AES128-SHA (1) eap_tls: (TLS) [61] ADH-CAMELLIA128-SHA (1) eap_tls: (TLS) [62] AES256-GCM-SHA384 (1) eap_tls: (TLS) [63] AES256-CCM (1) eap_tls: (TLS) [64] ARIA256-GCM-SHA384 (1) eap_tls: (TLS) [65] AES128-GCM-SHA256 (1) eap_tls: (TLS) [66] AES128-CCM (1) eap_tls: (TLS) [67] ARIA128-GCM-SHA256 (1) eap_tls: (TLS) [68] AES256-SHA256 (1) eap_tls: (TLS) [69] CAMELLIA256-SHA256 (1) eap_tls: (TLS) [70] AES128-SHA256 (1) eap_tls: (TLS) [71] CAMELLIA128-SHA256 (1) eap_tls: (TLS) [72] SRP-DSS-AES-256-CBC-SHA (1) eap_tls: (TLS) [73] SRP-RSA-AES-256-CBC-SHA (1) eap_tls: (TLS) [74] SRP-AES-256-CBC-SHA (1) eap_tls: (TLS) [75] AES256-SHA (1) eap_tls: (TLS) [76] CAMELLIA256-SHA (1) eap_tls: (TLS) [77] SRP-DSS-AES-128-CBC-SHA (1) eap_tls: (TLS) [78] SRP-RSA-AES-128-CBC-SHA (1) eap_tls: (TLS) [79] SRP-AES-128-CBC-SHA (1) eap_tls: (TLS) [80] AES128-SHA (1) eap_tls: (TLS) [81] CAMELLIA128-SHA (1) eap_tls: (TLS) TLS - Client preferred ciphers (by priority) (1) eap_tls: (TLS) [0] ECDHE-RSA-AES256-SHA (1) eap_tls: (TLS) [1] ECDHE-RSA-AES128-SHA (1) eap_tls: (TLS) [2] DHE-RSA-AES256-SHA (1) eap_tls: (TLS) [3] DHE-RSA-AES128-SHA (1) eap_tls: (TLS) [4] AES256-SHA (1) eap_tls: (TLS) [5] AES128-SHA (1) eap_tls: (TLS) [6] ECDHE-RSA-AES256-SHA384 (1) eap_tls: (TLS) [7] ECDHE-RSA-AES128-SHA256 (1) eap_tls: (TLS) [8] DHE-RSA-AES256-SHA256 (1) eap_tls: (TLS) [9] DHE-RSA-AES128-SHA256 (1) eap_tls: (TLS) [10] AES256-SHA256 (1) eap_tls: (TLS) [11] AES128-SHA256 (1) eap_tls: (TLS) [12] ECDHE-RSA-AES256-GCM-SHA384 (1) eap_tls: (TLS) [13] ECDHE-RSA-AES128-GCM-SHA256 (1) eap_tls: (TLS) [14] DHE-RSA-AES256-GCM-SHA384 (1) eap_tls: (TLS) [15] DHE-RSA-AES128-GCM-SHA256 (1) eap_tls: (TLS) [16] AES256-GCM-SHA384 (1) eap_tls: (TLS) [17] AES128-GCM-SHA256 ERROR: (1) eap_tls: (TLS) Failed reading from OpenSSL: ssl/statem/statem_srvr.c[2312]:error:0A0000C1:lib(20)::reason(193) ERROR: (1) eap_tls: (TLS) System call (I/O) error (-1) ERROR: (1) eap_tls: (TLS) EAP Receive handshake failed during operation ERROR: (1) eap_tls: [eaptls process] = fail ERROR: (1) eap: Failed continuing EAP TLS (13) session. EAP sub-module failed (1) eap: Sending EAP Failure (code 4) ID 1 length 4 (1) eap: Failed in EAP select (1) modsingle[authenticate]: returned from eap (rlm_eap) (1) [eap] = invalid (1) } # authenticate = invalid (1) Failed to authenticate the user (1) Using Post-Auth-Type Reject (1) Post-Auth-Type sub-section not found. Ignoring. (1) Login incorrect (eap_tls: (TLS) TLS - Alert write:fatal:handshake failure): [as] (from client ac port 29 cli 5a5b3135062e) (1) Delaying response for 5.000000 seconds Thread 2 waiting to be assigned a request Waking up in 4.6 seconds. (1) Sending delayed response (1) Sent Access-Reject Id 0 from 192.168.2.1:1812 to 192.168.2.2:44444 length 44 (1) EAP-Message = 0x04010004 (1) Message-Authenticator = 0x00000000000000000000000000000000 (1) Cleaning up request packet ID 0 with timestamp +16 due to done eady to process requests Waking up in 0.3 seconds. Thread 1 got semaphore Thread 1 handling request 2, (2 handled so far) (2) Received Access-Request Id 0 from 192.168.2.2:44444 to 192.168.2.1:1812 length 117 (2) User-Name = "as" (2) NAS-IP-Address = 192.168.2.2 (2) Called-Station-Id = "b4378330fc3b" (2) Calling-Station-Id = "5a5b3135062e" (2) NAS-Identifier = "b4378330fc3b" (2) NAS-Port = 29 (2) Framed-MTU = 1400 (2) NAS-Port-Type = Wireless-802.11 (2) EAP-Message = 0x02000007016173 (2) Message-Authenticator = 0x65ea19588c27954be750b34f05da01b7 (2) session-state: No State attribute (2) # Executing section authorize from file /etc/raddb/radiusd.conf (2) authorize { (2) modsingle[authorize]: calling eap (rlm_eap) (2) eap: Peer sent EAP Response (code 2) ID 0 length 7 (2) eap: EAP-Identity reply, returning 'ok' so we can short-circuit the rest of authorize (2) modsingle[authorize]: returned from eap (rlm_eap) (2) [eap] = ok (2) } # authorize = ok (2) Found Auth-Type = eap (2) # Executing group from file /etc/raddb/radiusd.conf (2) authenticate { (2) modsingle[authenticate]: calling eap (rlm_eap) (2) eap: Peer sent packet with method EAP Identity (1) (2) eap: Calling submodule eap_tls to process data (2) eap_tls: (TLS) TLS -Initiating new session (2) eap_tls: (TLS) TLS - Setting verify mode to require certificate from client (2) eap_tls: [eaptls start] = request (2) eap: Sending EAP Request (code 1) ID 1 length 10 (2) eap: EAP session adding &reply:State = 0x73da5fd773db5206 (2) modsingle[authenticate]: returned from eap (rlm_eap) (2) [eap] = handled (2) } # authenticate = handled (2) Using Post-Auth-Type Challenge (2) Post-Auth-Type sub-section not found. Ignoring. (2) session-state: Saving cached attributes (2) Framed-MTU = 1014 (2) Sent Access-Challenge Id 0 from 192.168.2.1:1812 to 192.168.2.2:44444 length 68 (2) EAP-Message = 0x0101000a0da000000000 (2) Message-Authenticator = 0x00000000000000000000000000000000 (2) State = 0x73da5fd773db520659675dbb5c31485d (2) Finished request Thread 1 waiting to be assigned a request (2) Cleaning up request packet ID 0 with timestamp +131 due to conflicting packet was received Waking up in 0.3 seconds. Thread 2 got semaphore Thread 2 handling request 3, (2 handled so far) (3) Received Access-Request Id 0 from 192.168.2.2:44444 to 192.168.2.1:1812 length 265 (3) User-Name = "as" (3) NAS-IP-Address = 192.168.2.2 (3) Called-Station-Id = "b4378330fc3b" (3) Calling-Station-Id = "5a5b3135062e" (3) NAS-Identifier = "b4378330fc3b" (3) NAS-Port = 29 (3) Framed-MTU = 1400 (3) State = 0x73da5fd773db520659675dbb5c31485d (3) NAS-Port-Type = Wireless-802.11 (3) EAP-Message = 0x020100890d00160301007e0100007a030367df7d21f4b742d6792d0128f9d335437102d658ee7fe1dc1c334257dacf927600002ac014c013003900330035002fc028c027006b0067003d003cc030c02f009f009e009d009cc0120016000a0100002700 (3) Message-Authenticator = 0x68e323e0b85f9b9e6c84bec8bc5bb779 (3) Restoring &session-state (3) &session-state:Framed-MTU = 1014 (3) # Executing section authorize from file /etc/raddb/radiusd.conf (3) authorize { (3) modsingle[authorize]: calling eap (rlm_eap) (3) eap: Peer sent EAP Response (code 2) ID 1 length 137 (3) eap: No EAP Start, assuming it's an on-going EAP conversation (3) modsingle[authorize]: returned from eap (rlm_eap) (3) [eap] = updated (3) } # authorize = updated (3) Found Auth-Type = eap (3) # Executing group from file /etc/raddb/radiusd.conf (3) authenticate { (3) modsingle[authenticate]: calling eap (rlm_eap) (3) eap: Removing EAP session with state 0x73da5fd773db5206 (3) eap: Previous EAP request found for state 0x73da5fd773db5206, released from the list (3) eap: Peer sent packet with method EAP TLS (13) (3) eap: Calling submodule eap_tls to process data (3) eap_tls: (TLS) EAP Continuing ... (3) eap_tls: (TLS) EAP Peer sent flags --- (3) eap_tls: (TLS) EAP Got final fragment (131 bytes) WARNING: (3) eap_tls: (TLS) EAP Total received record fragments (131 bytes), does not equal expected expected data length (0 bytes) (3) eap_tls: (TLS) EAP Verification says ok (3) eap_tls: (TLS) EAP Done initial handshake (3) eap_tls: (TLS) TLS - Handshake state [PINIT] - before SSL initialization (0) (3) eap_tls: (TLS) TLS - Handshake state [PINIT] - Server before SSL initialization (0) (TLS) Ignoring cbtls_msg call with pseudo content type 256, version 00000301 (3) eap_tls: (TLS) TLS - Handshake state [PINIT] - Server before SSL initialization (0) (TLS) Received 126 bytes of TLS data (TLS) 01 00 00 7a 03 03 67 df 7d 21 f4 b7 42 d6 79 2d (TLS) 01 28 f9 d3 35 43 71 02 d6 58 ee 7f e1 dc 1c 33 (TLS) 42 57 da cf 92 76 00 00 2a c0 14 c0 13 00 39 00 (TLS) 33 00 35 00 2f c0 28 c0 27 00 6b 00 67 00 3d 00 (TLS) 3c c0 30 c0 2f 00 9f 00 9e 00 9d 00 9c c0 12 00 (TLS) 16 00 0a 01 00 00 27 00 0a 00 10 00 0e 00 17 00 (TLS) 18 01 00 01 01 01 02 01 03 01 04 00 0d 00 0a 00 (TLS) 08 05 01 04 01 01 01 02 01 ff 01 00 01 00 (3) eap_tls: (TLS) TLS - recv TLS 1.3 Handshake, ClientHello (TLS) Ignoring cbtls_msg call with pseudo content type 256, version 00000303 (TLS) Received 2 bytes of TLS data (TLS) 02 28 (3) eap_tls: (TLS) TLS - send TLS 1.2 Alert, fatal handshake_failure ERROR: (3) eap_tls: (TLS) TLS - Alert write:fatal:handshake failure ERROR: (3) eap_tls: (TLS) TLS - Server : Error in error (3) eap_tls: Server preferred ciphers (by priority) (3) eap_tls: (TLS) [0] TLS_AES_256_GCM_SHA384 (3) eap_tls: (TLS) [1] TLS_AES_128_GCM_SHA256 (3) eap_tls: (TLS) [2] ECDHE-ECDSA-AES256-GCM-SHA384 (3) eap_tls: (TLS) [3] ECDHE-RSA-AES256-GCM-SHA384 (3) eap_tls: (TLS) [4] DHE-DSS-AES256-GCM-SHA384 (3) eap_tls: (TLS) [5] DHE-RSA-AES256-GCM-SHA384 (3) eap_tls: (TLS) [6] ECDHE-ECDSA-AES256-CCM (3) eap_tls: (TLS) [7] DHE-RSA-AES256-CCM (3) eap_tls: (TLS) [8] ECDHE-ECDSA-ARIA256-GCM-SHA384 (3) eap_tls: (TLS) [9] ECDHE-ARIA256-GCM-SHA384 (3) eap_tls: (TLS) [10] DHE-DSS-ARIA256-GCM-SHA384 (3) eap_tls: (TLS) [11] DHE-RSA-ARIA256-GCM-SHA384 (3) eap_tls: (TLS) [12] ADH-AES256-GCM-SHA384 (3) eap_tls: (TLS) [13] ECDHE-ECDSA-AES128-GCM-SHA256 (3) eap_tls: (TLS) [14] ECDHE-RSA-AES128-GCM-SHA256 (3) eap_tls: (TLS) [15] DHE-DSS-AES128-GCM-SHA256 (3) eap_tls: (TLS) [16] DHE-RSA-AES128-GCM-SHA256 (3) eap_tls: (TLS) [17] ECDHE-ECDSA-AES128-CCM (3) eap_tls: (TLS) [18] DHE-RSA-AES128-CCM (3) eap_tls: (TLS) [19] ECDHE-ECDSA-ARIA128-GCM-SHA256 (3) eap_tls: (TLS) [20] ECDHE-ARIA128-GCM-SHA256 (3) eap_tls: (TLS) [21] DHE-DSS-ARIA128-GCM-SHA256 (3) eap_tls: (TLS) [22] DHE-RSA-ARIA128-GCM-SHA256 (3) eap_tls: (TLS) [23] ADH-AES128-GCM-SHA256 (3) eap_tls: (TLS) [24] ECDHE-ECDSA-AES256-SHA384 (3) eap_tls: (TLS) [25] ECDHE-RSA-AES256-SHA384 (3) eap_tls: (TLS) [26] DHE-RSA-AES256-SHA256 (3) eap_tls: (TLS) [27] DHE-DSS-AES256-SHA256 (3) eap_tls: (TLS) [28] ECDHE-ECDSA-CAMELLIA256-SHA384 (3) eap_tls: (TLS) [29] ECDHE-RSA-CAMELLIA256-SHA384 (3) eap_tls: (TLS) [30] DHE-RSA-CAMELLIA256-SHA256 (3) eap_tls: (TLS) [31] DHE-DSS-CAMELLIA256-SHA256 (3) eap_tls: (TLS) [32] ADH-AES256-SHA256 (3) eap_tls: (TLS) [33] ADH-CAMELLIA256-SHA256 (3) eap_tls: (TLS) [34] ECDHE-ECDSA-AES128-SHA256 (3) eap_tls: (TLS) [35] ECDHE-RSA-AES128-SHA256 (3) eap_tls: (TLS) [36] DHE-RSA-AES128-SHA256 (3) eap_tls: (TLS) [37] DHE-DSS-AES128-SHA256 (3) eap_tls: (TLS) [38] ECDHE-ECDSA-CAMELLIA128-SHA256 (3) eap_tls: (TLS) [39] ECDHE-RSA-CAMELLIA128-SHA256 (3) eap_tls: (TLS) [40] DHE-RSA-CAMELLIA128-SHA256 (3) eap_tls: (TLS) [41] DHE-DSS-CAMELLIA128-SHA256 (3) eap_tls: (TLS) [42] ADH-AES128-SHA256 (3) eap_tls: (TLS) [43] ADH-CAMELLIA128-SHA256 (3) eap_tls: (TLS) [44] ECDHE-ECDSA-AES256-SHA (3) eap_tls: (TLS) [45] ECDHE-RSA-AES256-SHA (3) eap_tls: (TLS) [46] DHE-RSA-AES256-SHA (3) eap_tls: (TLS) [47] DHE-DSS-AES256-SHA (3) eap_tls: (TLS) [48] DHE-RSA-CAMELLIA256-SHA (3) eap_tls: (TLS) [49] DHE-DSS-CAMELLIA256-SHA (3) eap_tls: (TLS) [50] AECDH-AES256-SHA (3) eap_tls: (TLS) [51] ADH-AES256-SHA (3) eap_tls: (TLS) [52] ADH-CAMELLIA256-SHA (3) eap_tls: (TLS) [53] ECDHE-ECDSA-AES128-SHA (3) eap_tls: (TLS) [54] ECDHE-RSA-AES128-SHA (3) eap_tls: (TLS) [55] DHE-RSA-AES128-SHA (3) eap_tls: (TLS) [56] DHE-DSS-AES128-SHA (3) eap_tls: (TLS) [57] DHE-RSA-CAMELLIA128-SHA (3) eap_tls: (TLS) [58] DHE-DSS-CAMELLIA128-SHA (3) eap_tls: (TLS) [59] AECDH-AES128-SHA (3) eap_tls: (TLS) [60] ADH-AES128-SHA (3) eap_tls: (TLS) [61] ADH-CAMELLIA128-SHA (3) eap_tls: (TLS) [62] AES256-GCM-SHA384 (3) eap_tls: (TLS) [63] AES256-CCM (3) eap_tls: (TLS) [64] ARIA256-GCM-SHA384 (3) eap_tls: (TLS) [65] AES128-GCM-SHA256 (3) eap_tls: (TLS) [66] AES128-CCM (3) eap_tls: (TLS) [67] ARIA128-GCM-SHA256 (3) eap_tls: (TLS) [68] AES256-SHA256 (3) eap_tls: (TLS) [69] CAMELLIA256-SHA256 (3) eap_tls: (TLS) [70] AES128-SHA256 (3) eap_tls: (TLS) [71] CAMELLIA128-SHA256 (3) eap_tls: (TLS) [72] SRP-DSS-AES-256-CBC-SHA (3) eap_tls: (TLS) [73] SRP-RSA-AES-256-CBC-SHA (3) eap_tls: (TLS) [74] SRP-AES-256-CBC-SHA (3) eap_tls: (TLS) [75] AES256-SHA (3) eap_tls: (TLS) [76] CAMELLIA256-SHA (3) eap_tls: (TLS) [77] SRP-DSS-AES-128-CBC-SHA (3) eap_tls: (TLS) [78] SRP-RSA-AES-128-CBC-SHA (3) eap_tls: (TLS) [79] SRP-AES-128-CBC-SHA (3) eap_tls: (TLS) [80] AES128-SHA (3) eap_tls: (TLS) [81] CAMELLIA128-SHA (3) eap_tls: (TLS) TLS - Client preferred ciphers (by priority) (3) eap_tls: (TLS) [0] ECDHE-RSA-AES256-SHA (3) eap_tls: (TLS) [1] ECDHE-RSA-AES128-SHA (3) eap_tls: (TLS) [2] DHE-RSA-AES256-SHA (3) eap_tls: (TLS) [3] DHE-RSA-AES128-SHA (3) eap_tls: (TLS) [4] AES256-SHA (3) eap_tls: (TLS) [5] AES128-SHA (3) eap_tls: (TLS) [6] ECDHE-RSA-AES256-SHA384 (3) eap_tls: (TLS) [7] ECDHE-RSA-AES128-SHA256 (3) eap_tls: (TLS) [8] DHE-RSA-AES256-SHA256 (3) eap_tls: (TLS) [9] DHE-RSA-AES128-SHA256 (3) eap_tls: (TLS) [10] AES256-SHA256 (3) eap_tls: (TLS) [11] AES128-SHA256 (3) eap_tls: (TLS) [12] ECDHE-RSA-AES256-GCM-SHA384 (3) eap_tls: (TLS) [13] ECDHE-RSA-AES128-GCM-SHA256 (3) eap_tls: (TLS) [14] DHE-RSA-AES256-GCM-SHA384 (3) eap_tls: (TLS) [15] DHE-RSA-AES128-GCM-SHA256 (3) eap_tls: (TLS) [16] AES256-GCM-SHA384 (3) eap_tls: (TLS) [17] AES128-GCM-SHA256 ERROR: (3) eap_tls: (TLS) Failed reading from OpenSSL: ssl/statem/statem_srvr.c[2312]:error:0A0000C1:lib(20)::reason(193) ERROR: (3) eap_tls: (TLS) System call (I/O) error (-1) ERROR: (3) eap_tls: (TLS) EAP Receive handshake failed during operation ERROR: (3) eap_tls: [eaptls process] = fail ERROR: (3) eap: Failed continuing EAP TLS (13) session. EAP sub-module failed (3) eap: Sending EAP Failure (code 4) ID 1 length 4 (3) eap: Failed in EAP select (3) modsingle[authenticate]: returned from eap (rlm_eap) (3) [eap] = invalid (3) } # authenticate = invalid (3) Failed to authenticate the user (3) Using Post-Auth-Type Reject (3) Post-Auth-Type sub-section not found. Ignoring. (3) Login incorrect (eap_tls: (TLS) TLS - Alert write:fatal:handshake failure): [as] (from client ac port 29 cli 5a5b3135062e) (3) Delaying response for 5.000000 seconds Thread 2 waiting to be assigned a request Waking up in 4.6 seconds. (3) Sending delayed response (3) Sent Access-Reject Id 0 from 192.168.2.1:1812 to 192.168.2.2:44444 length 44 (3) EAP-Message = 0x04010004 (3) Message-Authenticator = 0x00000000000000000000000000000000 (3) Cleaning up request packet ID 0 with timestamp +131 due to done Ready to process requests

2 2

FreeRadius ldap queries are not executed
by Matvey Teplov 21 Mar '25

21 Mar '25

Hi, I am having a problem making FreeRADIUS querying for the group presence. Generally, authentication consists of two stages. The first stage is verifying the user with the RADIUS server via proxy; in the second stage, freeradius has to confirm if the user belongs to one of the groups defined LDAP and populate VSA's. So, the first stage ran successfully, LDAP connections were established at the startup, but pulling groups at the second stage is not happening. The log is: (6) Received Access-Request Id 239 from 127.0.0.1:55766 to 127.0.0.1:1825 length 101 (6) Message-Authenticator = 0xc70aa4ebf93116a15e305fbe97e49bb8 (6) User-Name = "generic-ms-user" (6) User-Password = "*********" (6) NAS-IP-Address = 172.17.0.6 (6) NAS-Port = 1 (6) # Executing section authorize from file /etc/freeradius/3.0/sites-enabled/default (6) authorize { (6) [preprocess] = ok (6) auth_log: EXPAND /var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/auth-detail-%Y%m%d (6) auth_log: --> /var/log/freeradius/radacct/127.0.0.1/auth-detail-20250311 (6) auth_log: /var/log/freeradius/radacct/%{%{Packet-Src-IP-Address}:-%{Packet-Src-IPv6-Address}}/auth-detail-%Y%m%d expands to /var/log/freeradius/radacct/127.0.0.1/auth-detail-20250311 (6) auth_log: EXPAND %t (6) auth_log: --> Tue Mar 11 12:38:06 2025 (6) [auth_log] = ok (6) pap: WARNING: No "known good" password found for the user. Not setting Auth-Type (6) pap: WARNING: Authentication will fail unless a "known good" password is available (6) [pap] = noop (6) update control { (6) Proxy-to-Realm := "radius_server" (6) } # update control = noop (6) } # authorize = ok (6) Starting proxy to home server 100.127.1.24 port 1823 (6) server default { (6) } (6) Proxying request to home server 100.127.1.24 port 1823 timeout 10.000000 (6) Sent Access-Request Id 171 from 0.0.0.0:57934 to 100.127.1.24:1823 length 112 (6) Message-Authenticator = 0xc70aa4ebf93116a15e305fbe97e49bb8 (6) User-Name = "generic-ms-user" (6) User-Password = "*********" (6) NAS-IP-Address = 172.17.0.6 (6) NAS-Port = 1 (6) Event-Timestamp = "Mar 11 2025 12:38:06 UTC" (6) Proxy-State = 0x323339 Waking up in 0.3 seconds. (6) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (6) BlastRADIUS check: Received packet without Message-Authenticator from home_server radius_server1 (6) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (6) The packet does not contain Message-Authenticator, which is a security issue (6) UPGRADE THE HOME SERVER AS YOUR NETWORK IS VULNERABLE TO THE BLASTRADIUS ATTACK. (6) Once the home server is upgraded, set "require_message_authenticator = true" for home_server radius_server1 (6) !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! (6) Clearing existing &reply: attributes (6) Received Access-Accept Id 171 from 100.127.1.24:1823 to 172.17.0.6:57934 length 25 (6) Proxy-State = 0x323339 (6) server default { (6) } (6) Found Auth-Type = Accept (6) Auth-Type = Accept, accepting the user (6) # Executing section post-auth from file /etc/freeradius/3.0/sites-enabled/default (6) post-auth { (6) [ldap_server] = noop (6) if (&control:LDAP-Group == "Radius_Admin_Group") { (6) ERROR: Failed retrieving values required to evaluate condition (6) elsif (&control:LDAP-Group == "Radius_ReadOnly_Group") { (6) ERROR: Failed retrieving values required to evaluate condition (6) elsif (&control:LDAP-Group == "Radius_ReadWrite_Group") { (6) ERROR: Failed retrieving values required to evaluate condition (6) else { (6) update control { (6) Auth-Type := Reject (6) } # update control = noop (6) update reply { (6) Reply-Message := "Access denied: Unauthorized group." (6) } # update reply = noop (6) } # else = noop (6) } # post-auth = noop (6) Login OK: [generic-ms-user] (from client localhost port 1) (6) Sent Access-Accept Id 239 from 127.0.0.1:1825 to 127.0.0.1:55766 length 0 (6) Reply-Message := "Access denied: Unauthorized group." (6) Finished request Waking up in 4.9 seconds. Any ideas will be appreciated! Best regards Matvey Teplov

3 4

Error when starting FreeRadius
by Leandro Tavares 21 Mar '25

21 Mar '25

Good morning, I am migrating the FreeRadius server from version 2.2.8 to a new machine running RHEL9 with FreeRadius 3.0.21-43, but when I try to start the services I get the following error: /etc/raddb/radiusd.conf[167]: Configuration item "user" is deprecated /etc/raddb/radiusd.conf[0]: Cannot use deprecated configuration item "user" radiusd: ERROR - Failed to parse user/group information. Has anyone else experienced this problem or have a solution? Thank you.

2 1

fr3 as squid?
by Dariusz Bloch 19 Mar '25

19 Mar '25

Hello. Does somebody try to use FR3 to act like squid proxy? Is this even possible? I want to block all websites and make exceptions(allow) for some specific sites. In generally, I try to replace AD and use LDAP/Samba4, maybe freeradius acting as hub to authenticate against external LDAP and authorize to resources(files, sites etc)... It's just ideas... -- Z poważaniem, *Dariusz Bloch* Specjalista ds. IT tel. +48 22 420 57 56 kom. +48 665 678 605 dariusz.bloch(a)telbridge.pl www.telbridge.pl <http://www.telbridge.pl> <http://www.telbridge.pl> <http://www.telbridge.pl> <http://www.telbridge.pl> Telbridge sp. z o.o. sp. k. ul. Zagnańska 49, 25-528 Kielce, NIP: 959-153-09-86. Sąd Rejonowy w Kielcach, X Wydział Gospodarczy KRS, KRS 0000788347, Oddział w Toruniu, ul. Gdańska 4a, II p. 87-100 Toruń, tel. +48 22 420 56 60, tel./fax +48 22 420 56 55

3 3

match replay log with the request and log rejected request
by Peter Hudec 19 Mar '25

19 Mar '25

Hello, I would like to ask how to configure the reply log that way I;m able to apir it with the request. As there is no username or some knd of session id in the reoply, the default reply_log configuration just logs the reply attributes. In this scenario I'm not able to pair it with the original request ;( At this time the logging is just into files. By default, the Rejected request are not logged, what should be changed to add logging for them? regards Peter

2 3

require_message_authenticator = auto
by David Herselman 18 Mar '25

18 Mar '25

Hi, I'd like to thank everyone that contributes to the RADIUS standards and particularly FreeRADIUS developers for their tireless efforts. I realise that the Blast RADIUS protocol vulnerability (CVE-2024-3596) could have been avoided should the standards have adopted recommendations put forward in the past, it must be very frustrating to work on things to have users asking questions more than a year later. We're diligently upgrading vendor equipment to support message authenticator, where CheckPoint, FortiNet and MikroTik have recently backported support to LTS versions. Whilst security devices (eg firewalls) have unique client definitions to match fixed IPs, we have approximately 1500+ routers that live in non-publicly accessible management subnets, although these are arguably still public as they are reachable from client environments. The main issue with these is that they connect via LTE mobile APNs. We configured client prefix definitions that cover hundreds of routes (eg 198.19.200.0/23), where we can't simply blindly upgrade these in large batches, requiring client scheduled maintenance windows. Due to how mobile operators assign IPs out of pools for the APNs, it's not possible for us to configure individual client statements. Any possibility of there being an additional option to augment the auto setting? So that each individual IP in a defined range is flipped to enforcing message-authenticator? Let me try to explain in way of example, let's say we have a client configured as follows: client managed.routers { ipaddr = 198.19.200.0 netmask = 23 secret = **************** nastype = cisco require_message_authenticator = auto-per-IP } We're hoping that other networks would benefit from an option whereby FreeRADIUS would possibly use a bloom filter to mark individual IPs in those subnets to requiring message authenticator should they receive a request which includes the M-A attribute. We would actually prefer FreeRADIUS to additionally flip on enforcement should a request contains the M-A attribute, irrespective of whether or not it's the first packet to arrive after FreeRADIUS was restarted. This way technicians could schedule and upgrade equipment and thereafter enforce M-A validation without having to reach out to people that have access to restart FreeRADIUS thereafter. It would also inconvenience technicians, forcing them to use special jump hosts that log in using _break glass_ local admin accounts without revealing those credentials in the process (we're hoping that this would motivate technicians to add routers to a _to be upgraded_ list to catch those that fall through cracks). Any suggestions from anyone that's walked this road before? Have we completely missed the boat or simply unaware of clever ways to handle this scenario? Regards David Herselman

2 1

RADIUS Conference 2025
by Linux Threads 18 Mar '25

18 Mar '25

Hi Guys. I tried joining the event, and got this error "event is now full", are you guys going to upload the Conference to youtube or other video hosting service? RADIUS Conference 2025 - Securing the Intranet and Extranet - Session 3 Live Join event or By registering, you agree to the Livestorm Terms and Conditions and Privacy Policy. * We're sorry but this event is now full. To ask for more seats, contact the host. Regards,

3 4