AFAIK, RadiuNT always logs pass-thru requests locally as well.
> i.e., we get the following acc recording in the logs:
> radrecv: Request from host aabbccdd (UUNET) code=4, id=41, length=125
> NAS-Identifier = a.b.c.d
> Acct-Status-Type = 7
> Acct-Delay-Time = 133
> Acct-Session-Id = "620002355"
> Received unknown attribute 115, vendor 0
> Proxy-State = "\360\032m\205S5\207\226\213\031\377\3760\312=\012"
> Jun 13 12:50:22 2000 [INFO]: SQL Statement: UPDATE sp SET
> sp.AcctStatusType=2, sp.CallDate=GetDate() FROM ServerPorts sp, Servers s
> WHERE sp.ServerID = s.ServerID AND s.IPAddress='a.b.c.d'
> Jun 13 12:50:22 2000 [NOTICE]: Server Ports successfully cleared by NAS
> Stop/Start request from a.b.c.d
> Sending Accounting Ack of id 41 to aabbccdd (UUNET)
> Resp Time: 30 Auth: 2/113 -> 115 Acct: 0/0/54 -> 168
> However, the accounting (stop record, in this case?) appears to be only
> being logged to the remote proxy, as per:
> "Sending Accounting Ack of id 41 to aabbccdd (UUNET)"
It looks like you are getting duplicate accounting requests (the
third number in the Acct: section is duplicates). You may need to
change the key on your Calls table if this continues to be the
problem (maybe adding username and/or NASPort).
Dale E. Reed Jr. Emerald and RadiusNT/X__________________________________________IEA Software, Inc. www.iea-software.com
For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart