Hi List! I seem to have a problem with Acct Stop Packets going "missing". Quite often it seems, when our NAS's (Livingston PM3) send the stop packet to indicate the user has logged off, the MySQL "Radacct" table doesnt seem to get updated. This results in what appears to be a user remaining online for longer than what they actually were.
Now I found this in the logs on the 2nd server : <snip> Error: Accounting: logout: login entry for NAS GHT-PM3 port 10 not found </snip> I suspect that its when the Primary Radius Server (for what ever reason) doesnt answer in time, the Acct Stop Packet gets sent to the 2nd radius server wich doesnt "remember" this user ever having logged in. Right so, How can I persuade the 2nd Radius Server to not trash these packets, but rather first try update the RadAcct SQL table, or perhaps I have to tell the 2 radius servers about each others existence? My effective setup is as follows: 3 x Lucent PM3 NAS's 2 x FreeRadius servers (Configured to share a single MySQL DB on a 3rd Machine) all NAS's use Radius Server A as the Primary, and only connect to Radius Server B for fail-over. The FreeRadius servers are setup pretty generically to use the MySQL DB. The MySQL DB is based on the "Dialup Admin" php set that can with FreeRadius. Any ideas/feedback would be appreciated. -Rob ---------------------------------- Rob Hartzenberg Network Admin : Imaginet Contact: 086 11 111 01 Email: [EMAIL PROTECTED] Web: http://www.imaginet.co.za/ ---------------------------------- - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
