(RADIATOR) No such user ?

Mon Jun 25 01:27:49 CDT 2001

Hi ,
Today I wonder why I cann't logon any user on Radmin Database .  In log
file always show   "No such user"
.   I'm very sure that Radiator and Radmin host can connect to Database
host .
Can someone tell me what 's wrong ?

Thanks,
Chairath

--------------------------------------------- Log File
-----------------------------------------------

Mon Jun 25 10:55:48 2001: DEBUG: Packet dump:
*** Received from 10.2.0.1 port 49152 ....
Code:       Access-Request
Identifier: 20
Authentic:  <0><0>e<161><0><0>7/<0><0>`<20><0><0>u<178>
Attributes:
 User-Name = "david"
 User-Password =
"<186>e<128><206>L<30>n<223><183><174>G<209>r<13><166><216>"
 Acct-Session-Id = "56000e27"
 NAS-IP-Address = 10.10.0.2
 Shasta-SGROUP = "Shasta 5000: iSOS (tm), 2.1(17)"
 Service-Type = Framed-User
 Framed-Protocol = PPP
 Calling-Station-Id = "ldc_12200000069"
 NAS-Port = 1644167237

Mon Jun 25 10:55:48 2001: DEBUG: Handling request with Handler
'Realm=DEFAULT'
Mon Jun 25 10:55:48 2001: DEBUG:  Deleting session for david, 10.10.0.2,
1644167237
Mon Jun 25 10:55:48 2001: DEBUG: do query is: delete from RADONLINE
where
NASIDENTIFIER='10.10.0.2' and NASPORT=01644167237

Mon Jun 25 10:55:48 2001: DEBUG: do query is: insert into RADMESSAGES
(TIME_STAMP, TYPE,
MESSAGE) values (993441348, 4, 'Handling with Radius::AuthRADMIN')

Mon Jun 25 10:55:48 2001: DEBUG: do query is: insert into RADMESSAGES
(TIME_STAMP, TYPE,
MESSAGE) values (993441348, 4, 'Handling with Radius::AuthRADMIN')

Mon Jun 25 10:55:48 2001: DEBUG: Query is: select PASS_WORD,
STATICADDRESS, TIMELEFT,
MAXLOGINS from RADUSERS where USERNAME='david' and BADLOGINS < 5 and
VALIDFROM <
993441348 and VALIDTO > 993441348

Mon Jun 25 10:55:48 2001: DEBUG: do query is: insert into RADMESSAGES
(TIME_STAMP, TYPE,
MESSAGE) values (993441348, 4, 'Radius::AuthRADMIN looks for match with
david')

Mon Jun 25 10:55:48 2001: DEBUG: Query is: select PASS_WORD,
STATICADDRESS, TIMELEFT,
MAXLOGINS from RADUSERS where USERNAME='DEFAULT' and BADLOGINS < 5 and
VALIDFROM <
993441348 and VALIDTO > 993441348

Mon Jun 25 10:55:48 2001: INFO: Access rejected for david: No such user
Mon Jun 25 10:55:48 2001: DEBUG: Packet dump:
*** Sending to 10.2.0.1 port 49152 ....
Code:       Access-Reject
Identifier: 20
Authentic:  <0><0>e<161><0><0>7/<0><0>`<20><0><0>u<178>
Attributes:
 Reply-Message = "Request Denied"

------------------------------------------- Configuration File
-------------------------------------------
Foreground
LogStdout
LogDir  d:/Radiator-Demo-2.18/log
DbDir  d:/Radiator-Demo-2.18
LogFile %L/logfile-%d-%m-%Y

# Dont turn this up too high, since all log messages are logged
# to the RADMESSAGES table in the database. 3 will give you everything
# except debugging messages
Trace 4

# You will probably want to change this to suit your site.
# You should list all the clients you have, and their secrets
# If you are using the Radmin Clients table, you wil probably
# want to disable this.
#<Client DEFAULT>
# Secret mysecret
# DupInterval 0
#</Client>

# You can put additonal (or all) client details in your Radmin
# database table
# and get their details from there with something like this:
# You can then use the Radmin 'Add Radius Client' to add new clients.
<ClientListSQL>
 DBSource dbi:ODBC:xxx
 DBUsername xxx
 DBAuth  xxx
</ClientListSQL>

#<AuthBy RADIUS>
# Identifier ProxyTofunk
# Host xxx
# Secret test
#</AuthBy>

#<Realm funk>
# strip Realm
# RewriteUsername s/^([^@]+).*/$1/
# AuthBy ProxyTofunk
#</Realm>

# Handle everyone with RADMIN
<Realm DEFAULT>
 <AuthBy RADMIN>
  # Change DBSource, DBUsername, DBAuth for your database
  # See the reference manual. You will also have to
  # change the one in <SessionDatabse SQL> below
  # so its the same
  DBSource dbi:ODBC:xxx
  DBUsername xxx
  DBAuth  xxx
  DateFormat %e %m  %Y %T
  # You can add to or change these if you want, but you
  # will probably want to change the database schema first
  AccountingTable RADUSAGE
  AcctColumnDef USERNAME,User-Name
  AcctColumnDef TIME_STAMP,Timestamp,integer
  AcctColumnDef ACCTSTATUSTYPE,Acct-Status-Type,integer
  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,integer
  AcctColumnDef FRAMEDIPADDRESS,Framed-IP-Address
  AcctColumnDef NASIDENTIFIER,NAS-Identifier
  AcctColumnDef NASIDENTIFIER,NAS-IP-Address
  AcctColumnDef NASPORT,NAS-Port,integer
  AcctColumnDef DNIS,Called-Station-Id
  AcctColumnDef DATE,Timestamp,integer-date
  # This updates the time and octets left
  # for this user
  AcctSQLStatement update RADUSERS set
TIMELEFT=TIMELEFT-0%{Acct-Session-Time},
OCTETSINLEFT=OCTETSINLEFT-0%{Acct-Input-Octets},
OCTETSOUTLEFT=OCTETSOUTLEFT-0%{Acct-Output-Octets} where USERNAME='%n'

  # These are the classic things to add to each users
  # reply to allow a PPP dialup session. It may be
  # different for your NAS. This will add some
  # reply items to everyone's reply
  AddToReply Framed-Protocol = PPP,\
   Service-Type = Framed-User,\
          Framed-IP-Netmask = 255.255.255.255,\
          Framed-Routing = None,\
          Framed-MTU = 1500,\
   Framed-Compression = Van-Jacobson-TCP-IP,\
   Idle-Timeout = 600
 </AuthBy>
</Realm>

<SessionDatabase SQL>
 # This database spec usually should be exactly the same
 # as in <AuthBy RADMIN> above
 DBSource dbi:ODBC:xxx
 DBUsername xxx
 DBAuth  xxx
 ClearNasQuery
</SessionDatabase>

# You can also set up an address pool for Radiator to manage.
# The standard Radmin tables include a RADPOOL address pool table.
# see the example in addressallocator.cfg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20010625/a93c8670/attachment.html>