> Since I didn't get an answer to my last question I have decided to go all
Sorry about the slow response. Several of our support and design engineers
have been at the pre IETF Radius Bake-off in Washington D.C. this week.
Things went very well btw! You should expect a reply soon. Thanks for your
patience.
Regards,
Sharon K. Caswell
=====================
IEA Software, Inc.
422 W. Riverside Suite 326
Spokane, WA 99201
509-444-2455 509-624-9903 fax
sales@iea-software.com
support@iea-software.com
> positive on the list and propose a solution to the RARAS problem, the way I
> read the RFC for accounting, you are in compliance when you send either
> attribute 4 (NAS IP Address) OR attribute 32 (Machine Name) or BOTH... USR
> sends Both, RARAS sends 32, everyone else it seems sends attribute 4.
>
> to make Radius-NT work with any compliant port server, if attribute 4 is
> sent, have it use attribute 4 as the NAS Id. if attribute 4 is not sent,
> look up the ip address of attribute 32 and use that as the nas Id.
>
> this may be a quick code change (I think it should be), anyway I
> currently have a test platform set up with an end to end isolated system to
> test on if I can be of any assistance testing a fix let me Know...
>
>
> "The woods are lovely, dark and deep. But I have promises to keep,
> And lines to code before I sleep, And lines to code before I sleep."
>
>
> David Harris
> Operations Manager
> StarNet OnLine Systems
>
>
> ----------------------------------------------------------
> RadiusNT Mailing List lists@iea-software.com
>
>