Hi, I want to store accounting packet(s) for future processing. [radiusd@tdrad1 freeradius-server-2.2.0]$ cat /app_log/radius/ggsn-acct/radacct/127.0.0.1/pre-proxy-detail-20121127 Tue Nov 27 15:03:35 2012 Packet-Type = Accounting-Request NAS-Port-Type = Virtual X-Ascend-Dial-Number = "<U+0557>\331\025" Acct-Session-Id = "d597d91572f51ab3" Is there any way to change / simulate functionality of the detail module like this ? Timestamp=" Tue Nov 27 15:03:35 2012"[delimiter]Packet-Type = Accounting-Request[delimiter]NAS-Port-Type = Virtual[delimiter] NAS-Port-Type = Virtual[delimiter] .... [end of line] Thx Peter Balšianok
BALSIANOK, Peter wrote:
Is there any way to change / simulate functionality of the detail module like this ?
Timestamp=“ Tue Nov 27 15:03:35 2012“[delimiter]Packet-Type = Accounting-Request[delimiter]NAS-Port-Type = Virtual[delimiter] NAS-Port-Type = Virtual[delimiter] .... [end of line]
See the "linelog" module. Alan DeKok.
I read it before i sent email. But my accounting radius servers receives packets from many devices ( each packet contains different group of AVPs ). Therefore Is it possible to configure linelog module to store all AVPs ( everytime, not only defined part of accounting packet ). -----Original Message----- From: freeradius-users-bounces+peter.balsianok=orange.sk@lists.freeradius.org [mailto:freeradius-users-bounces+peter.balsianok=orange.sk@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, November 27, 2012 10:41 PM To: FreeRadius users mailing list Subject: Re: Detail file BALSIANOK, Peter wrote:
Is there any way to change / simulate functionality of the detail module like this ?
Timestamp=“ Tue Nov 27 15:03:35 2012“[delimiter]Packet-Type = Accounting-Request[delimiter]NAS-Port-Type = Virtual[delimiter] NAS-Port-Type = Virtual[delimiter] .... [end of line]
See the "linelog" module. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
BALSIANOK, Peter wrote:
I read it before i sent email. But my accounting radius servers receives packets from many devices ( each packet contains different group of AVPs ). Therefore Is it possible to configure linelog module to store all AVPs ( everytime, not only defined part of accounting packet ).
See doc/variables.txt This is documented. But... there really isn't any point. Why is so vital to have them all on one line? Why not just use the detail file? Do the extra linefeeds really cause that much panic? Alan DeKok.
Sorry, i didnt read doc/variables.txt carefully ( missed %Z ). To have one packet in one line ( AVPs separated with delimiter ) from my point of view is better (simple). Of course i can parse current detail file format :). Last question. Is writing to detail file serialized ( paralel threads can write data at the same time to one file ) ? -----Original Message----- From: freeradius-users-bounces+peter.balsianok=orange.sk@lists.freeradius.org [mailto:freeradius-users-bounces+peter.balsianok=orange.sk@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Wednesday, November 28, 2012 3:41 PM To: FreeRadius users mailing list Subject: Re: Detail file BALSIANOK, Peter wrote:
I read it before i sent email. But my accounting radius servers receives packets from many devices ( each packet contains different group of AVPs ). Therefore Is it possible to configure linelog module to store all AVPs ( everytime, not only defined part of accounting packet ).
See doc/variables.txt This is documented. But... there really isn't any point. Why is so vital to have them all on one line? Why not just use the detail file? Do the extra linefeeds really cause that much panic? Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
BALSIANOK, Peter wrote:
Sorry, i didnt read doc/variables.txt carefully ( missed %Z ). To have one packet in one line ( AVPs separated with delimiter ) from my point of view is better (simple). Of course i can parse current detail file format :).
I wouldn't agree with "simpler". But it's your system.
Last question. Is writing to detail file serialized ( paralel threads can write data at the same time to one file ) ?
The server works, and doesn't do stupid things. Alan DeKok.
On 28 Nov 2012, at 15:05, Alan DeKok <aland@DEPLOYINGRADIUS.COM> wrote:
BALSIANOK, Peter wrote:
Sorry, i didnt read doc/variables.txt carefully ( missed %Z ). To have one packet in one line ( AVPs separated with delimiter ) from my point of view is better (simple). Of course i can parse current detail file format :).
I wouldn't agree with "simpler". But it's your system.
It's also going to go away in version 3.0 along with all the other one letter expansions. -Arran
participants (4)
-
Alan DeKok -
Arran Cudbard-Bell -
BALSIANOK, Peter -
Phil Mayers