On Jul 8, 2026, at 7:52 AM, Alan Smith via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
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?
Yes.
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?
The server has debug output. Read it. Alan DeKok.