- Freeradius-Users - lists.freeradius.org

Re: Re: Freeradius 3.0.19 and 3.0.21 can not find proto_acc.so and proto_auth.so.
by CpServiceSPb . 25 Apr '20

25 Apr '20

> Already asked and answered. > If you ask questions on the list, please read the replies you get. There was an issue for delivering my messages to the mailing list. I informed even to mailing list administrator about the situation.

1 0

Problem with EAP PEAP Authentication on freeradius 3.22
by Gleb Lisikh 24 Apr '20

24 Apr '20

Hello world! Trying to enable EPA2 Enterprise authentication for a Cisco Meraki AP. EAP Authenticaton section fails with the following: ===================================== (2) eap: Peer sent EAP Response (code 2) ID 2 length 161 (2) eap: Continuing tunnel setup (2) [eap] = ok (2) } # authorize = ok (2) Found Auth-Type = eap (2) # Executing group from file /usr/local/etc/raddb/sites-enabled/default (2) authenticate { (2) eap: Expiring EAP session with state 0x1da40b4e1ca6122b (2) eap: Finished EAP session with state 0x1da40b4e1ca6122b (2) eap: Previous EAP request found for state 0x1da40b4e1ca6122b, released from the list (2) eap: Peer sent packet with method EAP PEAP (25) (2) eap: Calling submodule eap_peap to process data (2) eap_peap: Continuing EAP-TLS (2) eap_peap: [eaptls verify] = ok (2) eap_peap: Done initial handshake (2) eap_peap: (other): before/accept initialization (2) eap_peap: TLS_accept: before/accept initialization tls: TLS_accept: Error in SSLv2/v3 read client hello A (2) eap_peap: ERROR: Failed in __FUNCTION__ (SSL_read): error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol (2) eap_peap: ERROR: System call (I/O) error (-1) (2) eap_peap: ERROR: TLS receive handshake failed during operation (2) eap_peap: ERROR: [eaptls process] = fail (2) eap: ERROR: Failed continuing EAP PEAP (25) session. EAP sub-module failed (2) eap: Sending EAP Failure (code 4) ID 2 length 4 (2) eap: Failed in EAP select (2) [eap] = invalid (2) } # authenticate = invalid (2) Failed to authenticate the user ===================================== Any idea where I may need to start troubleshooting? I haven't touched Authentication at all from its original. Authorization is done through python3 and seems to be working just fine. By the way, exactly the same error occurs on a different freeradius server running 3.021 Thank you! Gleb

2 6

originate-coa automatic home_server generation for clients
by Ali Arslan 24 Apr '20

24 Apr '20

Hello, I am using freeradius 3.0.16 with sql module and clients are generated automatically from nas table by adding uncommenting read_clients = yes in sql configuration f,le. But each nas client is added manually to originate-coa site as a home_server. Can this be made automatic just like nas clients? Thanks.

2 2

originate-coa automatic generation of cclients
by Ali Arslan 23 Apr '20

23 Apr '20

Hello, I am using freeradius 3.0.16 with sql module and clients are generated automatically from nas table by adding adding line read_clients = yes in sql configuration f,le. Each nas client is added manually to originate-coa site as a home_server. Can this be made automatic just like nas clients? Thanks.

2 1

Problems on replying attributes
by Marco Miglietta 22 Apr '20

22 Apr '20

Dears. In the authentication process on my freeradius v3 server, I reply to user its IP address to access VPN (Framed-IP-Address vsa). Now, I have to assign different IP address depending on which NAS the user wants access to. Is there a simple solution that I'm not finding ? Can anyone tell me in what direction should I direct my studies ? Thank you. Marco. --

3 6

Problems on replying attributes
by Marco Miglietta 21 Apr '20

21 Apr '20

Dears. In the authentication process on my freeradius v3 server, I reply to user its IP address to access VPN (Framed-IP-Address vsa). Now, I have to assign different IP address depending on which NAS the user wants access to. Is there a simple solution that I'm not finding ? Can anyone tell me in what direction should I direct my studies ? Thank you. Marco. --

1 0

rlm_sql
by Aurélio de Souza Ribeiro Neto 21 Apr '20

21 Apr '20

Hello, What I need to do to remove this warning? WARNING: Module rlm_sql became unblocked Thanks Aurélio

2 3

allocate_clear
by Aurélio de Souza Ribeiro Neto 20 Apr '20

20 Apr '20

Dear All, When allocate_clear query is executed? I'm using FreeRadius 3.19 and MySQL 5.7 In my sqlippool conf file It's set each 1s by default, but in which condition? Thanks a lot. Aurelio

2 2

accounting proxy via tcp
by belyj＠belyj.eu 20 Apr '20

20 Apr '20

Hi, Im trying to proxy NAS requests to freeradius via tcp. Authentication works, but accounting packets are still arriving via udp to radius. NAS < udp > FR proxy < tcp > FR, is it possible? or am i missing something radiusd: FreeRADIUS Version 3.0.21 (git #af428abda), for host x86_64-pc-linux-gnu FreeRADIUS Version 3.0.21 proxy.conf home_server testsrv1 { type = auth+acct ipaddr = 192.168.1.10 port = 2083 proto = tcp secret = 01b6c42 } home_server testsrv2 { type = acct ipaddr = 192.168.1.100 port = 2084 secret = 887b2a8a proto = tcp } ... sites-enabled/default ... accounting { update control { Replicate-To-Realm += testsrv1 Replicate-To-Realm += testsrv2 } replicate ... 12:53:35.758094 IP (tos 0x0, ttl 57, id 53740, offset 0, flags [none], proto UDP (17), length 204) 192.168.1.1.62825 > 192.168.1.100.2084: [udp sum ok] UDP, length 176 12:53:36.760526 IP (tos 0x0, ttl 57, id 53771, offset 0, flags [none], proto UDP (17), length 178) 192.168.1.1.17830 > 192.168.1.100.2084: [udp sum ok] UDP, length 150

2 3

Route through post-proxy not working when no live home servers are available - (3.0.20)
by João Vitor Arruda 20 Apr '20

20 Apr '20

Hello there I would like to request your help to see why we are facing this issue that was supposedly fixed in https://github.com/FreeRADIUS/freeradius-server/pull/2072 We have a server configured to proxy to an upstream server and the "post-proxy" configured with "Post-Proxy-Type Fail-Authentication" (tested with "Post-Proxy-Type Fail" too) to not respond. When the upstream server does not reply (either before or after starting the zombie period) the post-proxy section is invoked and works as expected as you can see in the log bellow (some lines were suppressed): (1) Received Access-Request Id 4 from [IPv6_HERE]:1812 to [IPv6_HERE]:1812 length 371 (1) Starting proxy to home server 192.168.100.10 port 1812 (1) Proxying request to home server 192.168.100.10 port 1812 timeout 5.000000 (1) Sent Access-Request Id 188 from 0.0.0.0:41510 to 192.168.100.10:1812 length 398 (1) Expecting proxy response no later than 4.667684 seconds from now (1) No proxy response, giving up on request and marking it done Marking home server 192.168.100.10 port 1812 as zombie (it has not responded in 5.000000 seconds). (1) ERROR: Failing proxied request for user "deadbeefcafe", due to lack of any response from home server 192.168.100.10 port 1812 (1) Clearing existing &reply: attributes (1) Found Post-Proxy-Type Fail-Authentication (1) server default { (1) # Executing group from file /etc/raddb/sites-enabled/default (1) Post-Proxy-Type Fail-Authentication { (1) if ((NAS-Port-Type == Ethernet) || (Service-Type == Call-Check) || (Service-Type == Framed-User)) { (1) if ((NAS-Port-Type == Ethernet) || (Service-Type == Call-Check) || (Service-Type == Framed-User)) -> TRUE (1) if ((NAS-Port-Type == Ethernet) || (Service-Type == Call-Check) || (Service-Type == Framed-User)) { (1) update control { (1) &Response-Packet-Type := Do-Not-Respond (1) } # update control = noop (1) } # if ((NAS-Port-Type == Ethernet) || (Service-Type == Call-Check) || (Service-Type == Framed-User)) = noop (1) } # Post-Proxy-Type Fail-Authentication = noop (1) } (1) Login incorrect (Home Server failed to respond): [deadbeefcafe] (from client any_ipv6 port 111 cli de-ad-be-ef-ca-fe) (1) Not responding to request (1) # Executing section post-auth from file /etc/raddb/sites-enabled/default But when the upstream server is marked as DEAD the post-proxy section is never invoked as you can see in the log bellow (some lines were suppressed): (60) Received Access-Request Id 216 from [IPv6_HERE]:1812 to [IPv6_HERE]:1812 length 371 (60) ERROR: Failed to find live home server: Cancelling proxy (60) WARNING: No home server selected (60) There was no response configured: rejecting request (60) Using Post-Auth-Type Reject (60) # Executing group from file /etc/raddb/sites-enabled/default (60) Post-Auth-Type REJECT { (60) Login incorrect (Failed to find live home server: Cancelling proxy): [deadbeefcafe ] (from client any_ipv6 port 111 cli de-ad-be-ef-ca-fe) (60) Sent Access-Reject Id 216 from [ IPv6_HERE]:1812 to [ IPv6_HERE ]:1812 length 20 Thanks for your help. Regards, Joao Arruda

2 4