April 2020 - Freeradius-Users - lists.freeradius.org

Unable to create control socket
by email.me＠kevp.com 26 Apr '20

26 Apr '20

Hi all, Can anyone please help me get the control socket for radmin working on Ubuntu. I've built FreeRADIUS v3.0.21 debs from source and install the debs on Ubuntu 18.04. I then created some ssl certs and the default config starts up ok. I then add a symlink to turn on the control-socket and sudo freeradius -X gives the error: Failed creating control socket "/var/run/freeradius/freeradius.sock": Failed creating control socket directory: Permission denied I know the service startup has comments about the directory creation not working on Ubuntu Bionic (18.04). So I've tried creating /usr/lib/tmpfiles.d/freeradius.conf containing: 'd /var/run/freeradius 0755 freerad freerad -' Ran sudo systemd-tmpfiles --create but no /var/run/freeradius Rebooted and no /var/run/freeradius sudo freeradius -X gives same error (as above). Anyone know how to get the control-socket to start correctly on Bionic? I've also tried on Ubuntu 16.04 and get the same issue, but I rather fix on 18.04 if poss. Many thanks all, Kev/.

3 3

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