Re: [RadiusNT] Radius Attribute #4

Dale E. Reed Jr. ( (no email) )
Thu, 23 Mar 2000 19:23:44 -0800

Messages sorted by: [ date ][ thread ][ subject ][ author ]
Previous message: Josh Hillman: "Re: [RadiusNT] Radius Attribute #4"
Next message: S.Tumurbaatar: "[RadiusNT] What table?"
Maybe in reply to: Josh Hillman: "[RadiusNT] Radius Attribute #4"

Josh Hillman wrote:
>
> > Just add attribute #32 as NAS-Identifier as well.
>
> I did this (string).
>
> > Don't change
> > the name of #4, or your calls accounting will not function right.
>
> Renaming attribute 4 to "NAS-IP-Address" AND changing Calls.NASIdentifier to
> Calls.NASIPAddress won't prevent this problem from occuring? For what it's
> worth, we don't use any of the Calls data for billing, etc.

Emerald specifically looks for certain columns in those tables,
including NASIdentifier. Changing the column name will prevent
many things from working.

> I'm bringing this up because some NASes that will soon be authenticating and
> issuing accounting records to our system use both attribute 4 AND 32.

Thats fine. RadiusNT knows how to deal with that and will handle it
just fine. If you want both of them, I would recommending changing
#32 to NAS-ID2 or something like that. Leave #4 as NAS-Identifier.

Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc. www.iea-software.com

For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart

Previous message: Josh Hillman: "Re: [RadiusNT] Radius Attribute #4"
Next message: S.Tumurbaatar: "[RadiusNT] What table?"
Maybe in reply to: Josh Hillman: "[RadiusNT] Radius Attribute #4"