Hello Andy -
Actually, what you get from any Radius client is a binary packet - the
translation to/from binary is done entirely by the Radius server which itself
is completely controlled by the local dictionary. In other words, you will
always get the same binary code from the NAS for an IP address (8) as you
correctly show below.
The only problem that you may have is on the server side, when different
dictionaries have been used for different user definitions. The simple fix to
this problem is to convert items such as you show below to all have the same
format and then just use that dictionary definition (or use the latest
version of the dictionary that defines both).
Note that there are two things happening with the dictionary. The first is
the translation from binary to string (for an inbound request) which will
always use the last such definition in the dictionary. However, to translate
from string to binary (for an outbound reply), either string will be
translated into the correct binary representation.
On Monday 07 May 2001 15:59, Andy De Petter wrote:
> Hello,
>
> As I have a verity of access servers, I was wondering how it would be
> possible to link 2 attributes to eachother.
>
> For example, from some access servers, I get the attribute "Framed-IP", and
> from other ones, I get "Framed-IP-Address", to get the client's IP address.
>
> Now, I know that it's possible to link the same integer attribute id to
> more than 1 name, like this:
>
> ATTRIBUTE Framed-IP 8 ipaddr
> ATTRIBUTE Framed-IP-Address 8 ipaddr
>
> BUT the problem with this is, that it only takes the last one, to translate
> an accounting packet.
>
> So, when I do a AcctColumnDef myframedip,Framed-IP-Address I don't get the
> ones, that have been sent with Framed-IP .
>
This will never happen - see above.
> Is there any way, to make sure, that I'm always saving either Framed-IP or
> Framed-IP-Address into myframedip, depending on what has been sent by the
> access server?
>
> If not, I might lose a considerable amount of information, for those who
> have been sent with Framed-IP.
>
All of the above said, there are a few cases where different NAS vendors send
the same information in different attributes entirely, but this is easy to
address with multiple AcctColumnDef's all using the same database column. As
there will only ever be one of the multiple attributes in the single packet,
you will never have a problem.
This topic has been discussed on the list a few times, so check the archive.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.
-
Nets: internetwork inventory and management - graphical, extensible,
flexible with hardware, software, platform and database independence.
===
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.
