|
I have a existing session database. I am now to the
point where I need to control MaxSessions.
When i add the MaxSessions 1 to my conf. file I get
ALOT of people that can't login because it believes the user is still online or
maxsession is exceeded. I know for a fact that these users are not online. Why
is it not letting them online?
Is there any other way or Proper way to set
radiator up to control maxsessions when I'm getting my auth's from wholesale
provider which does not support snmp to the nas's...? How do other people on the
list control simultaneous usage with Networks like Uunet,Qwest,Megapop
etc....
I have included the log file (Trace 4) with
the errors I get when I add MaxSessions 1 these errors are occurring even when
the user is not trying to do simultaneous connections. I have also
attached my conf file.
Mon Mar 3 08:06:00 2003: DEBUG: Packet
dump:
*** Received from 216.127.139.10 port 3800 .... Code: Access-Request Identifier: 171 Authentic: U<143><8><233><171><129><22><252><26>7<148><157>b<21><216>M Attributes: User-Name = "[EMAIL PROTECTED]" CHAP-Password = <1>#<134><194><141>c(<29>;<243><168><143>D<168>V<213><172> NAS-IP-Address = 67.193.160.36 NAS-Port = 2052 NAS-Port-Type = Async Service-Type = Framed-User Framed-Protocol = PPP State = "" Called-Station-Id = "************" Acct-Session-Id = "388570715" Ascend-Data-Rate = 26400 Ascend-Xmit-Rate = 50667 network = "u2" Mon Mar 3 08:06:00 2003: DEBUG: Handling
request with Handler 'Realm=DEFAULT'
Mon Mar 3 08:06:00 2003: DEBUG: Deleting session for [EMAIL PROTECTED], 67.193.160.36, 2052 Mon Mar 3 08:06:00 2003: DEBUG: do query is: delete from RADONLINE where NASIDENTIFIER='67.193.160.36' and NASPORT=02052 Mon Mar 3 08:06:00 2003: DEBUG: Query is:
select NASIDENTIFIER, NASPORT, ACCTSESSIONID, FRAMEDIPADDRESS from RADONLINE
where [EMAIL PROTECTED]
Mon Mar 3 08:06:01 2003: DEBUG: Checking if
user is still online: unknown, [EMAIL PROTECTED],
67.193.160.36
, 13,
388532462
67.193.119.193
Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.36 , 3203, 388529606 67.193.119.73 Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.36 , 2121, 388518728 67.193.119.57 Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.36 , 2244, 388501182 67.193.119.57 Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.36 , 111, 388543128 67.193.119.187 Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.47 , 17, 376236234 67.193.170.23 Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.36 , 2065, 388528348 67.193.119.93 Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.47 , 2059, 376233805 67.193.170.77 Mon Mar 3 08:06:01 2003: DEBUG: Checking if user is still online: unknown, [EMAIL PROTECTED], 67.193.160.47 , 209, 376233644 67.193.170.44 Mon Mar 3 08:06:01 2003: INFO: Access rejected for [EMAIL PROTECTED]: MaxSessions exceeded Mon Mar 3 08:06:01 2003: DEBUG: Packet dump: *** Sending to 216.127.139.10 port 3800 .... Code: Access-Reject Identifier: 171 Authentic: U<143><8><233><171><129><22><252><26>7<148><157>b<21><216>M Attributes: Reply-Message = "Request Denied" |
# common-sql.cfg # # Example Radiator configuration file that allows you to # authenticate from an SQL database. # With Radiator you can interface with almost any databse schema, # and there are many more configurable parameters that allow you # to control database fallback, select statements, column names # and arrangements etc etc etc. # See the reference manual for more details. # This is a very simple exmaple to get you started. It will # work with the tables created by the goodies/*.sql scripts. # # You should consider this file to be a starting point only # $Id: sql.cfg,v 1.5 2000/11/07 21:18:05 mikem Exp $
Foreground
LogStdout
LogDir .
DbDir .
Trace 4
DictionaryFile %D/dictionary.ascend2
include %D/clients.cfg
# This will authenticate users from SUBSCRIBERS
<Realm DEFAULT>
MaxSessions 1
<AuthBy SQL>
# Adjust DBSource, DBUsername, DBAuth to suit your DB
DBSource dbi:ODBC:LocalRadiusDB
DBUsername ****
DBAuth ******
AuthSelect select radiusname, password, profiles.checkattr, profiles.replyattr
from RADIUSCUSTOMER,profiles where radiuscustomer.radiusprofile =
profiles.radiusprofile and radiusname= %0
# You may want to tailor these for your ACCOUNTING table
# You can add your own columns to store whatever you like
AccountingTable RAD_ACCOUNTING
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
AuthColumnDef 1, Password, check
AuthColumnDef 2, GENERIC, check
AuthColumnDef 3, GENERIC, reply
# 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
<SessionDatabase SQL>
DBSource dbi:ODBC:LocalRadiusDB
DBUsername ****
DBAuth ******
# We want to save the DNIS as well as the usual things.
# Requires a different schema to the example RADONLINE
# provided
AddQuery insert into RADONLINE (USERNAME,\
NASIDENTIFIER, NASPORT, ACCTSESSIONID, TIME_STAMP,\
FRAMEDIPADDRESS, NASPORTTYPE, SERVICETYPE, DNIS) \
values ('%n', '%N',\
%{NAS-Port}, '%{Acct-Session-Id}', %{Timestamp},\
'%{Framed-IP-Address}', '%{NAS-Port-Type}', \
'%{Service-Type}', '%{Called-Station-Id}')
</SessionDatabase>
#<StatsLog SQL>
# You need to specify which database to connect to:
# DBSource dbi:ODBC:LocalRadiusDB
# DBUsername ****
# DBAuth ******
# # The logging interval in seconds
# #Interval 2
#</StatsLog>
#<Log SQL>
# # Defines how to connect to the database. See examples above
# DBSource dbi:ODBC:LocalRadiusDB
# DBUsername ****
# DBAuth ******
#
# # Trace level to use (allows same values as the global Trace level)
# #Trace 4
#</Log>
</AuthBy>
</Realm>
