Hello Mark -
On Wed, 08 Mar 2000, you wrote:
Whenever I get an auth request, I want to look back at the SQL database the
accounting-start packet was written to, to look at a few fields that are not
available in the auth request packet (namely called_station-id). We use
AS5300 and SQL auth and accounting and whenever people call in on 1 of the
4e1's they need to be treated and authed differently. The SQL procedure
called by auth works great so does the accounting but is there any way to
associate the following stream :
acct-start
auth
acct_stop
How do I tie the acct-start to the auth ???
I must confess to being confused by your question. The normal sequence of
events is this:
1. user dials NAS
2. NAS answers call
3. NAS initiates PPP authentication
4. NAS sends Radius authentication request (including Called-Station-Id,
Calling-Station-Id, etc.)
5. Radiator processes the authentication request (Access-Request)
6. if Access-Accept, NAS starts PPP
7. NAS sends Accounting-Request - Start
8. Radiator processes Accounting-Start
9. when session ends, NAS sends Accounting-Request - Stop
10. Radiator processes Accounting-Stop
If you want to tie accounting requests to a particular Access-Request, the
usual practice is to send a "Class" attribute in the Access-Accept.
hth
Hugh
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald,
Platypus, Freeside, Interbiller, TACACS+, PAM, external, etc, etc.
Available on Unix, Linux, FreeBSD, Windows 95/98/2000, NT, MacOS X.
===
Archive at http://www.starport.net/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
