(RADIATOR) Re: REPLYATTR SQL problem

Tue Sep 11 02:47:46 CDT 2001

Hugh:

The length of the CHECKATTR & REPLYATTR is 400 characters.  Find below some
information (Config, ReplyAttr & Trace 4 Debug)

Config File:
    Foreground
LogStdout
LogDir  e:/radiator/radiator-2.18.2
DbDir  e:/radiator/radiator-2.18.2

Trace  3

LogFile  %L/logfile

AuthPort 1645
AcctPort 1646

#DictionaryFile %D/dictionary

<Client  x.x.x.x>
     Secret xxxxxxx
    IgnoreAcctSignature
</Client>

# This will authenticate users from SubsInfo

<Realm DEFAULT>

 PasswordLogFileName pwdtunde
 AcctLogFileName  %L/detail

 <AuthBy SQL>
 # Adjust DBSource, DBUsername, DBAuth to suit your DB

     DefaultSimultaneousUse 5
     DBSource dbi:ODBC:optiusers
     DBUsername sa
     DBAuth  dl380linkserve

    AuthSelect select PASSWORD, CHECKATTR, REPLYATTR from SubsInfo where
USERNAME='%n'

    AuthColumnDef 0, User-Password, check
    AuthColumnDef 1, GENERIC, check
    AuthColumnDef 2, GENERIC, reply

 # store accounting records in RADUSAGEyyyymm table
     AccountingTable AcctInfo

     AcctColumnDef USERNAME,User-Name
     AcctColumnDef TIME_STAMP,Timestamp,integer
     AcctColumnDef ACCTSTATUSTYPE,Acct-Status-Type
     AcctColumnDef ACCTDELAYTIME,Acct-Delay-Time,integer
    AcctColumnDef ACCTINPUTOCTETS,Acct-Input-Octets,integer
    AcctColumnDef ACCTOUTPUTOCTETS,Acct-Output-Octets,integer
     AcctColumnDef ACCTSESSIONID,Acct-Session-Id
     AcctColumnDef ACCTSESSIONTIME,Acct-Session-Time,integer
     AcctColumnDef ACCTTERMINATECAUSE,Acct-Terminate-Cause
     AcctColumnDef NASIDENTIFIER,NAS-Identifier
     AcctColumnDef NASPORT,NAS-Port,integer
     AcctColumnDef FRAMEDIPADDRESS,Framed-IP-Address

 # You can arrange to log accounting to a file if the
 # SQL insert fails with AcctFailedLogFileName
 # That way you could recover from a broken SQL
 # server

     AcctFailedLogFileName %D/missedaccounting
    </AuthBy>
</Realm>

ReplyAttr Values
-------------------
Idle-Timeout = 120, Framed-Protocol = PPP, Framed-IP-Netmask =
255.255.255.0, Filter-Id = "email", USR-IP-Input-Filter = "1 ACCEPT dst-addr
= 195.166.232.000/24", USR-IP-Input-Filter = "2 ACCEPT dst-addr =
195.166.228.000/24", USR-IP-Input-Filter = "3 ACCEPT dst-addr =
195.166.226.000/24", USR-IP-Input-Filter = "4 ACCEPT dst-addr =
195.166.230.000/24", USR-IP-Input-Filter = "5 ACCEPT dst-addr =
195.166.232.000/24", USR-IP-Input-Filter = "6 REJECT tcp-dst-port = 80",
USR-IP-Input-Filter = "7 REJECT tcp-src-port = 80", USR-IP-Input-Filter = "8
DENY"

Trace 4 Debug
-----------------

Tue Sep 11 10:03:30 2001: ERR: Attribute number 38998 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:30 2001: ERR: Attribute number 39000 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:32 2001: ERR: Attribute number 39049 (vendor 429) is not
define
d in your dictionary
DBD::ODBC::st fetchrow failed: [Microsoft][ODBC Microsoft Access
Driver]String d
ata, right truncated on column number 3 (REPLYATTR) (SQL-01004)(DBD:
st_fetch/SQ
LFetch (long truncated) err=1) at Radius/SqlDb.pm line 283.
Tue Sep 11 10:03:32 2001: INFO: Access rejected for merinv: No such user
Tue Sep 11 10:03:33 2001: ERR: Attribute number 38998 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:33 2001: ERR: Attribute number 39000 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:33 2001: ERR: Attribute number 39001 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:33 2001: ERR: Attribute number 39051 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:33 2001: ERR: Attribute number 39049 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:33 2001: ERR: Attribute number 38998 (vendor 429) is not
define
d in your dictionary
Tue Sep 11 10:03:33 2001: ERR: Attribute number 39000 (vendor 429) is not
define
d in your dictionary

'Tunde Ogedengbe
Linkserve Limited
22 Akin Adesola Street
Victoria Island
Lagos - Nigeria
Tel: +234 1 2623900
Fax: +234 1 2623906
URL: http://www.linkserve.net
----- Original Message -----
From: "Hugh Irvine" <hugh at open.com.au>
To: "'Tunde Ogedengbe" <tunde at linkserve.net>
Cc: <radiator at open.com.au>
Sent: Tuesday, September 11, 2001 2:25 AM
Subject: (RADIATOR) Re: REPLYATTR SQL problem

>
> Hello 'Tunde -
>
> On Tuesday 11 September 2001 04:35, 'Tunde Ogedengbe wrote:
> > Hello:
> >
> > Does the RELPYATTR field have a field length limitation?  I am having
> > problems with Attributes loaded in my SQL database which is about 400
long.
> > The ODBC Driver is reporting an error "String truncated ".  I am
> > authenticating via MySQL.  Pls help resolve this problem.
> >
>
> The REPLYATTR field is defined in your database - what size have you
defined
> it to be? And when are you getting the error? As usual, I will need to see
a
> copy of the configuration file (no secrets) together with a trace 4 debug
> from Radiator and a copy of the table definitions for the database.
>
> regards
>
> 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 radiator-announce at open.com.au
> To unsubscribe, email 'majordomo at open.com.au' with
> 'unsubscribe radiator' in the body of the message.
>

===
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.