Hi Friends,
I have a doubt about handlers. Below is my current configuration , but i have plans to distinguish this configuration as two parts for further development. One part is to be handled by handler clause <Handler Acct-Status-Type = Alive> and the other part is to be handled by <Handler Acct-Status-Type = Stop>.

Previously i had made a configuration similar to this, but the 2nd defined handler clause in radiator config was never called. Why is this? How is a right way/syntax to implement the above mentioned requirement of mine? I previously got a reply something like " first matching clause would be used and others would be ignored" . Can you please elaborate this , i did not understand this?

My requirement is to process and handle ,Alive and Stop packet separately and the configuration must be called/processed separately ,each time the radiator receives it based on the Acct Status type as described above. Please help me out , i could not find an explanation for this anywhere and i am confused. Please let me know, if you need any more specifics to help me out.


_Configuration _

#Foreground
#LogStdout

AcctPort 1813
AuthPort 1812

BindAddress 0.0.0.0

LogDir          /var/log/radius
DbDir           /etc/radiator
# Use a low trace level in production systems. Increase
# it to 4 or 5 for debugging, or use the -trace flag to radiusd
Trace           4

# You will probably want to add other Clients to suit your work site,

<Client DEFAULT>
        Secret  xxxxx
        DupInterval 0
</Client>


<Client 10.50.1.4>
        Secret xxxxx
        DupInterval 0
        NasType Cisco
        IgnoreAcctSignature
</Client>

<SessionDatabase SQL>


        Identifier      tamesql
        DBSource        dbi:ODBC:IRONMAN
        DBUsername      xxxxxx
        DBAuth          xxxxx

</SessionDatabase>





<Handler Request-Type = Accounting-Request>
PreProcessingHook file:"/etc/radiator/createavpairs.pl"
        <AuthBy SQL>
                Identifier thomas
                DBSource dbi:ODBC:IRONMAN
                DBUsername xxxx
                DBAuth xxxxx


                #AccountingStopsOnly
                AccountingTable ACCOUNTING
                AcctColumnDef   USERNAME, User-Name
                AcctColumnDef   ACCTSTATUSTYPE,Acct-Status-Type
                AcctColumnDef   FRAMEDIPADDRESS,Framed-IP-Address
                AcctColumnDef ACCTINPUTOCTETS,Acct-Input-Octets,integer
                AcctColumnDef ACCTOUTPUTOCTETS,Acct-Output-Octets,integer
                AcctColumnDef TIME_STAMP,Event-Timestamp,integer-date
                AcctColumnDef ACCTSESSIONTIME,Acct-Session-Time,integer
                AcctColumnDef ACCTDELAYTIME,Acct-Delay-Time,integer
                AcctColumnDef   ACCTSESSIONID,Acct-Session-Id
                AcctColumnDef ACCTTERMINATECAUSE,Acct-Terminate-Cause
                AcctColumnDef   NASIDENTIFIER,NAS-Identifier
                AcctColumnDef   NASPORT,NAS-Port,integer
                AcctColumnDef   PARENTSESSIONID,parent-session-id

AcctSQLStatement update quotasubscribers set monthlycounter = monthlycounter + 0%{Acct-Output-Octets}, totalcounter = totalcounter + 0%{Acct-Output-Octets}, timestamp = %{Event-Timestamp} \
                                where username='%n' \
                                And Type = 'Q'



        </AuthBy>
PostAuthHook file:"/etc/radiator/rocky.pl"
                #Log accounting to a detail file
                AcctLogFileName %L/detail


</Handler>




<Handler Request-Type=Disconnect-Request>
        <AuthBy RADIUS>

                <Host 10.50.1.4>
                    Secret xxxxxx
                </Host>
        </AuthBy>
</Handler>

--
Thanks & Best Regards,

Thomas Kurian
IT Security Engineer (B.Tech. -- Electrical)
Kuwaiti Canadian Consulting Group (www.kccg.com)
T: +965 22435566
F: +965 22415149
E: [email protected]

_______________________________________________
radiator mailing list
[email protected]
http://www.open.com.au/mailman/listinfo/radiator

Reply via email to