Hello Mariano -
On Monday 27 August 2001 23:04, Mariano Absatz wrote:
> Hi,
>
> for what I understand of the standard (RFC2865 section 5.32) the NAS-
> Identifier attribute is an arbitrary string used to identify the NAS.
>
Yes, although it is usually a fully qualified domain name, and that is what
Radiator expects it to be.
> However, when I put a simple string in a <ClientListSQL> it complains that
> it can�t resolve an address for it.
>
> I had something like this:
>
> ==========================================================================
> <ClientListSQL>
> # Client (NAS) info is in the database
>
> include %{GlobalVar:ConfigDir}/DBUseData.cfg
>
> GetClientQuery SELECT \
> NAS_IDENTIFIER, NAS_SECRET, \
> NAS_IGNOREACCTSIGNATURE, NAS_DUPINTERVAL, \
> NAS_DEFAULTREALM, NAS_TYPE, NAS_SNMPCOMMUNITY, \
> NAS_LIVINGSTONOFFS, NAS_LIVINGSTONHOLE, \
> NAS_FRAMEDGROUPBASEADDRESS, NAS_FRAMEDGROUPMAXPORTSPERCLAS, \
> NAS_REWRITEUSERNAME, NAS_NOIGNOREDUPLICATES, \
> NAS_PREHANDLERHOOK \
> FROM NAS
>
> </ClientListSQL>
> ==========================================================================
>
> The message in the log is:
>
> ==========================================================================
> Sat Aug 25 12:07:40 2001: ERR: Could not resolve an address for Client CPM1
> Sat Aug 25 12:07:41 2001: INFO: Server started: Radiator 2.18.2 on radius1
> ==========================================================================
>
> However, in the database, NAS_IDENTIFIER is a common name (in fact, it's
> the table's id field) and I have a NAS_IP_ADDRESS field.
>
> Re-reading the manual, I see there is no place to hold the
> NAS-IP-Address... should I use NAS_IP_ADDRESS as the first field in the
> query?
>
> All the fields ar taken "in order"? that is, it works as if it had an
> implied "ClientColumnDef" or something like that?
>
Yes, the fields are taken in order.
>From section 6.6.2 in the Radiator 2.18.2 reference manual:
Your database table must include at least the first and second fields (i.e.
the NAS name or IP address and the shared secret). All the other fields are
optional, but if they occur, they must occur in the same order. When they
occur, they are used to initialize the Client parameter of the same name as
shown above. The FRAMEDGROUPBASEADDRESS column may contain multiple
comma-separated base addresses.
# Our custom client table only has NAS identifier,
# shared secret and default realm in it:
GetClientQuery select NAME,SECRET,NULL,NULL,DREALM
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.open.com.au/archives/radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
