Thanks for the advice Alan. I tried configuring radsecproxy in another server (radsec_server) which radsecproxy config pointing to my radius server who is listening at both udp 1812 and tcp 2083.After configuring radsecproxy successfully, this new server listens at udp 1812. I ran radtest in this server to localhost 1812 and it will go to radius server at 2083.Let me confirm this is the correct setup? The authentication needs the radsec_server IP address to be present in clients.conf. Although it is already present in SQL radius client table, it cannot be recognized.I think authentication request that reaches tcp 2083 are not associated with SQL client table. Did I miss to update something? On Wednesday, 1 July 2026 at 09:56:19 pm SGT, Alan DeKok <alan.dekok@inkbridge.io> wrote: On Jul 1, 2026, at 5:00 AM, Alan Smith via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
I am currently running Freeradius on RHEL 8.10 in a lab. It has custom site configured and make use of sql for radius client table.Customised perl module is used for the authentication. It listens on UDP 1812 and 1813. I would say it is working fine.
That's good.
I would like to check the use of Radius over TLS on TCP 2083 for some of the clients. I update tls in sites-available and created symlink in sites-enabled. Configured the custom CA certs.It is now listening at TCP 2083. I want to test if the clients from sql be recognized. Is there like a tool NTRadping? I can test from either Windows or Linux.I do not have any device that can authenticate. Kindly advise. Thank you.
There's a pyradius library with TLS, or you can run another RADIUS server such as radsecproxy. For now, that's the simplest way. Alan DeKok.