I've upgraded my RadiusNT 2.5 from build .209 to build .213 and I restarted
my RadiusNT service. I then observed my logfile and here are my observations
1. If there is a Session-Timeout service default, it is followed, regardless
of TimeLeft value.
2. If there is no Session-Timeout service default and TimeLeft is NULL, no
Session-Timeout is sent to NAS (unlike the very large Session-Timeout that
..209 sends the NAS).
3. If there is no Session-Timeout service default and TimeLeft > 0, then a
Session-Timeout = TimeLeft is sent to NAS.
Do you think item #1 is the way RadiusNT should really work ? If not, when
will this be corrected ?
----- Original Message -----
From: Dale E. Reed Jr. <email@example.com>
Sent: Wednesday, May 17, 2000 12:38 AM
Subject: Re: [Emerald] RadiusNT - problem with TimeBanking - very big value
for Session Timeout
> Danny Sinang wrote:
> > I am running RadiusNT 2.5.267 along with Emerald 2.5 using a SQL Server
> > database.
> I assume you mean 2.5.167, as 2.5.214 is the lastest build. :)
> There are been several issues addressed and fixed concerning
> time banking and session-timeout in the latest .2xx build.
> One specific one was were RadiusNT was not adding the Session-Timeout
> attribute if it didn't already exist.
> > Is this the way RadiusNT is supposed to work ?
> > I tried deleting the SessionTimeout from the service defaults and tried
> > dialling in as TimeBanked user. This time, the SessionTimeout attribute
> > sent the NAS is the remaining value of TimeLeft. However, the user still
> > won't get disconnected from the NAS.
> This is an issue with your NAS, then.
> > My NAS is a Cisco 2600 and its debug output does not show anything
> > However, I noticed that when the NON-TimeBanked users, RadiusNT sends
> > SessionTimeout whose value is 679952640.
> I'd like to see behavior of a more recent build. I'm pretty sure all of
> has been addresses.
> Dale E. Reed Jr. Emerald and RadiusNT/X
> IEA Software, Inc. www.iea-software.com
> For more information about this list (including removal) go to:
For more information about this list (including removal) go to: