On Fri, May 2, 2008 at 6:17 PM, Alan DeKok <[EMAIL PROTECTED]> wrote: > rsg wrote: > > They are not on the same LAN. This delay is induced by SQL based IP > assignment. > > > > Specially when around 30 concurrent Auth queries are made, the > > accounting response (Start) takes about 30 seconds (Delayed by New > > Auth requests) to reach NAS leading to the ultimate Auth failures. > > Huh? You're saying that the NAS rejects the user because it can't > send an Accounting-Request packet? That's broken.
No, NAS doesn't receive the Accounting-Response from AAA in time. > > > > Could Accouting-Responses be prioritized over New Auth-queries? > > No. > > (1) Your SQL server seems to have problems. 32 queries/s isn't a lot. > (2) Your NAS seems to have problems. Users should NOT be rejected > because it doesn't get an accounting response packet > (3) Even if it *did* prioritize accounting responses, all you would be > doing is trading off rejecting one user for rejecting another user. > > Something is broken in your system. It's not FreeRADIUS. > Thanks. Will have a closer look into the SQL first.. > > > Alan DeKok. > - > List info/subscribe/unsubscribe? See > http://www.freeradius.org/list/users.html > - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html