TLS Radsec
Alan DeKok
aland at deployingradius.com
Tue Jun 10 13:15:19 UTC 2025
On Jun 10, 2025, at 9:01 AM, Rodrigo Prieto <rodrigoprieto2019 at gmail.com> wrote:
> Thanks Alan for replying. I'm configuring it in this place, and if I set it to more than 30 seconds, it doesn't take effect.
It does take effect. Read the debug output. Look for "idle_timeout":
> client cliente2 {
> ipaddr = 192.168.122.188
> require_message_authenticator = "no"
> secret = <<< secret >>>
> limit {
> max_connections = 16
> lifetime = 0
> idle_timeout = 30
> }
> }
> ...
> Reached idle timeout on socket auth+acct from client (192.168.122.188, 39871) -> (*, 2083, virtual-server=default)
> ... shutting down socket auth+acct from client (192.168.122.188, 39871) -> (*, 2083, virtual-server=default)
> ... cleaning up socket auth+acct from client (192.168.122.188, 39871) -> (*, 2083, virtual-server=default)
> Ready to process requests
The problem, and solution, should be obvious.
You can also read the comments for idle_timeout in the clients.conf file. It explains this behavior.
Alan DeKok.
More information about the Freeradius-Users
mailing list