> We have just upgraded to FreeRADIUS 2.1.6, but unfortunately the problem
> persists:
>
>
>
> Server1/:
> total 1008236
> -rw--- 1 root root 714751062 Jul 29 11:53 detail-20090729
> -rw--- 1 root root 316653344 Jul 29 07:29 detail.work <= stuck!
>
>
> We got sometimes the following messa
ing requests received by FreeRADIUS, and
> Server2 receives accounting requests that matches a filter. I've noticed that
> Server1 and Server2 accounting responses for the same accounting requests
> have the same Packet Identifier, and that the NAS frequently reuses this
> Packet
Cristina Miyata wrote:
> We have just upgraded to FreeRADIUS 2.1.6, but unfortunately the problem
> persists:
>
> Server1/:
> total 1008236
> -rw--- 1 root root 714751062 Jul 29 11:53 detail-20090729
> -rw--- 1 root root 316653344 Jul 29 07:29 detail.work <= stuck!
A 700M detail file?
#x27;d suggest upgrading to 2.1.6. It fixes some issues when reading
from detail files.
Alan DeKok.
-[ Received Mail Content ]--
Subject : Problem with proxied accounting
Date : Tue, 21 Jul 2009 21:28:58 -0400 (EDT)
>From : "Cristina Miyata"
To :
p {margin-top
Cristina Miyata wrote:
> We are using Freeradius 2.1.1 and we send accounting RADIUS to 2 different
> servers called Server1 and Server2. In order to do so, we created two proxy
> servers and 3 detailed accouting logs: detail (stored in the server), detail1
> (processed by the proxy server that
Dear FreeRADIUS Users,
We are using Freeradius 2.1.1 and we send accounting RADIUS to 2 different
servers called Server1 and Server2. In order to do so, we created two proxy
servers and 3 detailed accouting logs: detail (stored in the server), detail1
(processed by the proxy server that sen
6 matches
Mail list logo
