Re: [RADIATOR] AcctLogFileName alongside AccountingTable in AuthBy SQL

2012-05-11 Thread Heikki Vatiainen
On 05/10/2012 09:48 AM, Jens Neu wrote: unfortunately the error is in my email only, i typed this from my config file and did not copy/paste. I'll be a little bit more verbose, here's my current handler config, just stripped for some AcctColumnDefs. I Tried the AcctLogFileName

Re: [RADIATOR] AcctLogFileName alongside AccountingTable in AuthBy SQL

2012-05-11 Thread Jens Neu
Hmm, I took your configuration I tried it on a machine that even does not have Oracle stuff installed. The SQL insert of course failed, but detail.loca-testing was created with the accounting record. So for me it worked as expected. Are you sure you are not handling accounting with some

Re: [RADIATOR] AcctLogFileName alongside AccountingTable in AuthBy SQL

2012-05-11 Thread Jens Neu
#Realm FILE # AuthBy FILE # Filename %D/users # /AuthBy # AcctLogFileName %L/detail #/Realm still in the config for users that are not in the SQL Database, but just removed it. Disregard my last email, removing AcctLogFileName from the Realm did the

Re: [RADIATOR] AcctLogFileName alongside AccountingTable in AuthBy SQL

2012-05-10 Thread Jens Neu
I was quite puzzled why it does not work for you. I bet you have something like this in your log: ERR: Unknown keyword 'AcctLogFilename' in file.cfg line 38 So use AcctLogFileName in your Handlers and it should work. Notice the spelling (f vs F). That's where the problem is. Thanks!

Re: [RADIATOR] AcctLogFileName alongside AccountingTable in AuthBy SQL

2012-05-09 Thread Heikki Vatiainen
On 05/08/2012 09:12 AM, Jens Neu wrote: this works quite well so far. Please note the %L/authlog.pool1, %L/authlog.pool2, etc. Now I want to create the analog for %L/detail.pool1, %L/detail.pool2 and so on. Any hints on how to achieve this? No matter where I place my AcctLogFilename

[RADIATOR] AcctLogFileName alongside AccountingTable in AuthBy SQL

2012-05-08 Thread Jens Neu
Dear all, I'm trying to build a setup where I can route requests from several clients to a dedicated ip-pool each. Currently I'm doing something like this (simplified): Client 10.x.x.x Identifier a /Client ... AddressAllocator SQL Indentifier id1 AddressPool pool1