Hello Dave -
You will have to check your NAS documentation to see what options you have.
Other than Session-Timeout and Idle-Timeout as you have already mentioned,
there isn't anything else you can do with Radius reply attributes.
hth
Hugh
On Tuesday 17 April 2001 05:30, Kitabjian, Dave wrote:
> We seem to have a constant chunk of ports hogged up by users who aren't
> using the Internet "interactively". This kills our dialup resources (and
> violates our Terms and Conditions).
>
> We already have an Idle-Timeout set, but that doesn't catch people who have
> AIM running, or who set Eudora to automatically check their mail every 10
> minutes, since they pass data. And we don't want to use Session-Timeout
> since that will kick them off even if they're "active" at the time of the
> Timeout.
>
> So...
>
> What we'd really like is a "parametrized Idle-Timeout": an Idle-Timeout
> that will kick you off if your recent usage falls BELOW AN ADJUSTABLE
> THRESHOLD of bytes/minute. Is there such a thing?
>
> Another option might be a "conditional Session-Timeout": after
> Session-Timeout is exceeded, prompt the user if he needs to remain
> connected, and if there is no reply after X minutes, disconnect them. Is
> this possible?
>
> Or, what other solutions are out there for attacking this problem?
>
> Thanks in advance!
>
> Dave
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
