Re: RadiusNT and Calls Table

Dale E. Reed Jr. ( (no email) )
Fri, 12 Dec 1997 09:07:54 -0800

Jeff Woods wrote:
>
> This is still a BAD THING. The ASID should be unique in and of itself, and
> really ought to be one of only TWO priomary keys in the Calls table --
> combined with the "start" or "stop" identifier, it should be completely
> unique. If it isn't, you need to get with your NAS manufacturer and ask
> WHY it isn't.

No, you are wrong there. The ASID is unique ONLY to that client.
Therefore NASIdentifier is REQUIRED in the key. If you have several
PortMasters and they are all on the same reboot cycle, you will
definately see duplicate ASID attributes, which is COMPLETELY
legal. Thats why all four of the fields are in RadiusNT: we've
been there, we've done that, and we know what it should be! :)

-- Dale E. Reed Jr.  (daler@iea.com)_________________________________________________________________       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |   http://www.iea-software.com