At 09:05 PM 6/16/97 -0700, you wrote:
>Michael R. Conder wrote:
>>
>> 1. We received a Unknown Attribute message for attributes 32 and 50. Our
>> example Access database in the RadAttributes Table had no entries for
>> attributes 32 and 50. I assume attribute 32 is the NAS-Identifier per the
>> RadiusNT Dictionary, ver 25.12. 10/25/95, and that NAS-Identifier is NOT
>> attribute 4 as indicated in our example calls table provided with the
>> RadiusNT version 1.60.
>
>Attribute 4 is officially NAS-IP-Address and 32 is NAS-Identifier. The
>first
>is an IP Address type and the second is a string. USR is the only one I
>know
>of using 32 (they actually send both 32 and 4, which IMHO is against the
>RADIUS RFC). Typically with a USR I name 4 NAS-Identifier and 32
>NAS-Identifier2.
>RadiusNT handles this without having to fuss with all the names (if you
>name
>them with the RFC specifics for RadiusNT 2.2, it can handle it fine).
>
>> 2. Which attribute should we use to assign an inactivity timeout to
>> callers?, i.e. to bump them off line when they are idle for xxxxx time.
>> How do we define xxxxx in the access database?
>
>Idle-Timeout = xxxxx seconds.
>
>> 3. When will RadiusNT version 2 be available?
>
>I don't have a definite date.
>
>
>
>--
>Dale E. Reed Jr. (daler@iea.com)
>_________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.emerald.iea.com
>
> ----------------------------------------------------------
> RadiusNT Mailing List listserver@emerald.iea.com
>
>