Hmm.. okay, so it comes down to the fact it's not possible to map more than
1 attribute name, to an attribute id # .. The reason I asked, in the first
place, was for compatibility reasons.. I have a few attributes, that have
other names, on different access servers, and I wanted to satisfy all of
them..
Thanks anyway for the information Hugh,
-a
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Hugh Irvine
> Sent: vrijdag 1 januari 1904 10:02
> To: Andy De Petter; Radiator Mailing
> Subject: IMPORTANT - Re: (RADIATOR) dictionary question
>
>
>
> Hi Andy -
>
> At 10:31 +0200 01/3/27, Andy De Petter wrote:
> >Hi guys,
> >
> >I was just wondering, whether someone knows, whether you can
> have some kinds
> >of "aliases", in your dictionary? For example, if you'ld want
> to support:
> >
> >ATTRIBUTE attname1 999 ipaddr
> >
> >BUT you'ld also want another attribute, to point to the same one:
> >
> >ATTRIBUTE attname2 999 ipaddr
> >
> >In the end, you'ld turn up like:
> >
> >ATTRIBUTE attname1 999 ipaddr
> >ATTRIBUTE attname2 999 ipaddr
> >
> >in your dictionary. Would the dictionary still be valid, and
> will Radiator
> >support this?
> >
>
> Yes you can do this, however you need to keep in mind how the
> dictionary is used. Basically there are two tables built in memory
> inside Radiator, one is for translating attribute names to the
> numeric equivalent and the other is to translate from the numeric
> representation to the attribute name. The dictionary file is parsed
> sequentially from start to finish, with any later definition
> replacing the previous definition for any identical attribute name or
> value.
>
> This being the case, you can use one or the other or both attribute
> names in your configuration file and user definitions, however only
> the last definition will be used for the decoding of the numeric
> attribute representations in the inbound packets.
>
>
> hth
>
> Hugh
>
> --
>
> NB: I am travelling this week, so there may be delays in our
> correspondence.
>
> Radiator: the most portable, flexible and configurable RADIUS server
> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
> Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
> Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
>
> ===
> Archive at http://www.starport.net/~radiator/
> Announcements on [EMAIL PROTECTED]
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
