Re: Subscriber session limit

Alan DeKok via Freeradius-Users <[email protected]> Thu, 15 Jan 2026 18:15:45 -0500
Newsgroups	gmane.comp.freeradius.user
Message-ID	<[email protected]>
On Jan 15, 2026, at 5:39 PM, Filip Nikolić <[email protected]> wrote:
> Sorry If I wasn't clear in first message.
> I am trying to establish the 60k sessions running on Ixia machine over the BNG.

  Again... what do you mean by "session"?

  Are you trying to authenticate different users?

> Every time as I am running a sessions my process is failing after I reach 28232 user. ( it looks like that their is a limit).
> I am wondering where can be a bottle neck,

  Not FreeRADIUS.

> When I run the freeradius in debug mode I see this:
> 
> (59150) Cleaning up request packet ID 1 with timestamp +857 due to done Waking up in 7.8 seconds. (57551) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57557) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57561) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57564) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57567) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57569) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57575) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57577) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57583) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached

  Formatting things properly helps.

> (57590) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57591) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57597) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57601) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57603) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57604) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57605) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57608) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57609) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached (57615) Cleaning up request packet ID 1 with timestamp +835 due to cleanup_delay was reached
> leanup_delay was reached
> (59146) Cleaning up request packet ID 1 with timestamp +857 due to cleanup_delay was reached
> (59149) Cleaning up request packet ID 1 with timestamp +857 due to cleanup_delay was reached
> Ready to process requests

  i.e. FreeRADIUS stops receiving packets.

> After this messages my process stop. And I can't establish any other session.


  Get the client to send more packets.

  If FreeRADIUS isn't receiving packets, it can't authenticate anyone.

  Alan DeKok.

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
signature.asc (application/pgp-signature, 833 B)