June 2023 - Freeradius-Users - lists.freeradius.org

rlm_perl module crash on high load, need to restart service
by Imdad Hasan 05 Jun '23

05 Jun '23

Thanks Alen, Great if the perl or any module will provide async support. Right now I am using FreeRADIUS version 3.0.20 with Jan-2023 built. Actually I tried loading with Jmeter, it's handling around 300 requests per second, but sometimes the resend ratio is big compared to my last exec module php script.. Even the new perl module and php swoole back-end is very light weight with Async MySQL support. But I don't know why the resend ratio is more than the old exec module. I am using 2Core CPU/1GB RAM EC2 for new code for FreeRADIUS with perl module and php swoole backend. The MySQL server is in the same VPC with different EC2. Please guide me for a quick solution for now, after FreeRADIUS 4.x, i will upgrade it. Thanks Imdad

2 1

rlm_perl module crash on high load, need to restart service
by Imdad Hasan 04 Jun '23

04 Jun '23

Hi All, I am using the rlm_perl module with an async TCP server. in this rlm_perl module is the TCP socket client and swoole is Async TCP socket server. When i am testing high load, at that time it's showing an error duplicate packet conflict module queue and crashes the server, even after stopping the load the freerdius is not working, i need to restart the freeradius server and it's working fine. Please guide me. Thanks Imdad

2 1

radiusd binary static (linux) build
by Ľudovít Mikula 03 Jun '23

03 Jun '23

Hi, have anybody tried to do a static build of radiusd binary? Would it be possible with current build setup? If so, can you share the steps to get a static build (or with as little dynamic dependencies as possible). Thank you. -- Ludo

2 2

Modifying outgoing device name attribute
by Kenny Simpson 02 Jun '23

02 Jun '23

Hi all, New to freeradius and need a little help which has stumped me and a colleague. We are using freeradius to proxy authentication from Fortinet to freeradius to cisco acs. We are now stumped on how to get it to authenticate properly. We can see in the Cisco ACS logs that the device is being authenticated and that it is matching the appropriate access service but it is failing on shared secret even though we know that the shared secret is correct and that the password for the user is correct. Looking at the logs its says that the client is the incoming proxy server with its name and ip address as this is what is in the client. It has the NAS IP correctly defined but I am thinking that because the device name and ip are different to the NAS IP then its failing as the actual proxied connection has a different secret. Is there anyway of modifying the out going "device name attribute and ip" to match that of the client configuration. I hope this makes sense hahah Thanks Kenny

2 1