hello all,
i am currently trying to proxy accounting to another freeradius server. the
accounting request receives the proxied server but i get the following
message in with debug:
+- entering group accounting {...}
[sql_default] expand: packet has no accounting status type. [user
Hi,
+- entering group accounting {...}
[sql_default] expand: packet has no accounting status type. [user
'%{User-Name}', nas '%{NAS-IP-Address}'] - packet has no accounting status
type. [user 'b...@realm', nas '10.80.10.140']
[sql_default] packet has no accounting status type. [user
Is it possible to have the accounting packets that you would normally proxy
to another server wrote to a file and then sent from the file. The same
concept as we get with the buffered-sql config.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Mark Jones wrote:
Is it possible to have the accounting packets that you would normally
proxy to another server wrote to a file and then sent from the file.
The same concept as we get with the buffered-sql config.
raddb/sites-available/decoupled-accounting
Alan DeKok.
-
List
I'm currently running Freeradius 2.1.7 across 3 servers and have been having a
recurring issue where proxied accounting packets
stop being relayed to my customers approximately after 1 month of uptime. Auth
still works just fine, but for some strange reason, acct just stops being
relayed
Hi everyone,
I have an interesting dilemma that I would like to share with the list,
perhaps someone can shed some light on how they handle this kind of thing.
I have 2 freeradius 2.1.7 servers that receive accounting updates from
multiple clients, and proxy these accounting updates to
Patric wrote:
When the proxied updates are eventually processed, they are written into
my account logs mysql table. The acct_start_time is written as the
current date and time, and the acct_delay_time holds the difference
between the actual time of the accounting update and now.
Hmm... the
Any advise or experiences would be much appreciated!
Fix the SQL queries so that the right information goes into the DB.
Note that the calculated times may be off by a second or two, due to
limited time resolution.
It may be worth updating the server to create a Acct-Start-Time
Ignore me...
signature.asc
Description: OpenPGP digital signature
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
(processed by the proxy server that send accounting to Server2).
I'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
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?
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 cmiy...@lycos.com
To : freeradius-users@lists.freeradius.org
p {margin-top:0px;margin
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 message for
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
Hi all,
I am trying to use a FreeRadius server as a proxy server using the realm.
Apparently my configuration is working for the Access-Request messages, but
not for the Accounting-request messages.
The proxy.conf is very simple:
realm test.com {
type= radius
authhost
We proxy some authentication and accounting to another company.
After installing freeradius version 2.0.1 they have said they are getting
errors in their log file:
02/13/2008 00:01:06 Missing Acct-Status-Type attribute in request
02/13/2008 00:01:06 Request has invalid syntax (e.g. invalid,
.. snip ...
Wed Feb 13 15:17:00 2008 : Debug: rlm_sql (sql): Released sql socket
id: 4
Wed Feb 13 15:17:00 2008 : Debug: modsingle[accounting]: returned
from sql (rlm_sql) for request 0
Wed Feb 13 15:17:00 2008 : Debug: ++[sql] returns ok
Wed Feb 13 15:17:00 2008 : Debug:
Tony Spencer wrote:
We proxy some authentication and accounting to another company.
After installing freeradius version 2.0.1 they have said they are
getting errors in their log file:
...
Wed Feb 13 15:17:00 2008 : Debug: modsingle[accounting]: returned from
Arran Cudbard-Bell wrote:
Can always apply the accounting_response filter in post-proxy if you
were worried about it... something like
post-proxy {
...
if(%{Packet-Type} == 'Accounting-Response'){
attr_filter.accounting_response
That won't do what you think. It filters the
Alan DeKok wrote:
Arran Cudbard-Bell wrote:
Can always apply the accounting_response filter in post-proxy if you
were worried about it... something like
post-proxy {
...
if(%{Packet-Type} == 'Accounting-Response'){
attr_filter.accounting_response
That won't do what you
Arran Cudbard-Bell wrote:
Alan DeKok wrote:
Arran Cudbard-Bell wrote:
Can always apply the accounting_response filter in post-proxy if you
were worried about it... something like
post-proxy {
...
if(%{Packet-Type} == 'Accounting-Response'){
attr_filter.accounting_response
Hello,
I'm trying to configure freeradius to only sql log Accounting packets
that are not proxied. I see the note in the config file that reads
accounting requests which are proxied are also logged in the detail
file. That is fine, but I can't have it log to sql. In general I
would only like
, the accounting packets are handled by the attr_filter_accounting
function.
I have a problem with this, because I'm rewriting attributes with the
preproxy_users file.
That module's function will change attributes in both proxied authentication
requests and proxied accounting requests.
Now
24 matches
Mail list logo
