(RADIATOR) Ascend SNMP Problems

[Leon Oosterwijk]

Colin, 

The issue at hand is about the fact that the username on the NAS is not the
same that the RADIUS server compares it against. 

Leon 


-----Original Message-----
From: Colin D. Easton [mailto:ceaston at attcanada.ca] 
Sent: Wednesday, August 29, 2001 10:58 AM
To: 'Leon Oosterwijk'
Subject: RE: (RADIATOR) Ascend SNMP Problems


In my experience it's always good to set it at twice what it should be.
For regular users set to 2 and for isdn etc set to 4.  This way most
race conditions may be avoided.  It's not absolute nor is it perfect but
it works.

C.

-----Original Message-----
From: owner-radiator at open.com.au [mailto:owner-radiator at open.com.au] On
Behalf Of Leon Oosterwijk
Sent: Wednesday, August 29, 2001 9:47 AM
To: 'radiator at open.com.au'
Subject: RE: (RADIATOR) Ascend SNMP Problems

Hugh, 

Please help me in trying to setup the SNMP Pull with the non-rewritten
username. I've altered the config for my session db to store both
versions
of the username. Following is the session Database as it is defined in
our
configuration. Where do I change the behaviour of RADIATOR to use the
non-rewritten username for NAS-SNMP checks? 

Leon 
 


#*******************************************************************
#*******************************************************************
# SESSIONS Database holds the sessions for all the users
# /usr/local/bin/Radius-Session-DBCheck.pl removes stale entries
#*******************************************************************
#*******************************************************************
<SessionDatabase SQL>
        Identifier sessiondb
        DBSource        dbi:mysql:radadmin:host=host.isdn.net
        DBUsername      username
        DBAuth          password

        AddQuery  insert into RADONLINE (RRUSERNAME, USERNAME,
NASIDENTIFIER, NASPORT, \
                        ACCTSESSIONID, FRAMEDIPADDRESS, NASPORTTYPE, \
                        SERVICETYPE, DNIS, CALLINGSTATIONID, TIME_STAMP)
values ('%U', '%u', '%N', %{NAS-Port}, \
				'%{Acct-Session-Id}',
'%{Framed-IP-Address}', '%{Port-Type}', '%{Framed-Protocol}', \
                        '%{Called-Station-Id}', '%{Calling-Station-Id}',
'%{Timestamp}' )
        
        DeleteQuery  delete from RADONLINE where USERNAME='%u' and \
                        NASIDENTIFIER='%N' and NASPORT='%{NAS-Port}'

        ClearNasQuery delete from RADONLINE where NASIDENTIFIER='%N'

        CountQuery select NASIDENTIFIER, NASPORT, ACCTSESSIONID from \
                         RADONLINE where USERNAME='%u'
        
                # The OLD query:
                #select nasid, slotitem, sessionid from ses4web where
username='%u'
</SessionDatabase SQL>



-----Original Message-----
From: Hugh Irvine [mailto:hugh at open.com.au] 
Sent: Tuesday, August 28, 2001 6:50 PM
To: Leon Oosterwijk; 'radiator at open.com.au'
Subject: Re: (RADIATOR) Ascend SNMP Problems



Hello Leon -

You don't show the session database that you are using, but the problem
is 
because you are doing a RewriteUsername and the rewritten username is
being 
used to check against the NAS (which of course won't work).

The usual way to deal with this problem is to use an SQL session
database
and 
store both the original username and the rewritten username therein with
your 
own queries. That way you can use the rewritten username for
simultaneous
use 
limit checking, and the original username for checking with the NAS.

regards

Hugh

===
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.