Re: [RadiusNT] idle-timeout

Josh Hillman ( (no email) )
Wed, 27 Jan 1999 11:37:22 -0500

>>Josh Hillman wrote:
>>> They're being disconnected based on the idle limit set in the Max. By
>>> default (unless it's changed recently), the Maxes have 120 seconds set
>>> so low, I don't know). On the assumption that you changed it to
>>> like 1200 (20 mins) or something, then all users will be using that
>>> You won't be able to override it for individual users with radius
>>> because the Max will ignore them (because Shared Prof = no).
>>Shared Profiles tell the Max not to let two non-multi-link connections
>>use the same username.

From: Ed Miller <>
>Should it be yes or no to the stop non-multi-link connections?

If you have RadiusNT set to use Concurrency Control and Variable Login
Limits, and also have your users' accounts have a Login Limit of 1, then
those users will not be able to log in more than once per username
simultaneously. This in-turn prevents MP.

Now that I think of it, I think we have Shared Prof = yes to allow a couple
of us to use MP--we authenticate directly in the Max instead of using the
database/radius, so that in the event that there's some problem with the
db/radius, we can still dial-up.
Information on Shared Prof is in the Max Reference Guide, "MAX Alphabetical
Parameter Reference". I seem to remember MP not working until we set this
to "yes", but I don't remember if it was strictly with the few accts on the
Maxes or if it also affected

>I have Ethernet/answer/Session options/Idle="0" This does mean that i can
>set the disconnect from Emerald services, Right?

This setting is overridden by whatever value you have set in the radius
attribute, Ascend-Idle-Limit. Setting either of these settings to zero
makes it not time out.


For more information about this list, including removal, please
see this URL: