Hi, Don`t you plan to extend linelog this way: If filename is '', linelog will write message to standard radius log file (radiusd.conf section log.file). Also if i run radiusd with -X, linelog will write message to standard output. For me it will be helpful in this case: I want to send access accept for all cases (correct login, incorrect login, wrong password). In case of correct login, i will send access accept with Context-Name = internet. In rest cases, i will send access accept with Context-Name = wrong. In this case user is able to go just at html page with information: Pleases verify your name or password. But i loose possibility to say: login was correct or incorrect or bad password (based on radius.log, because all rows will be Login OK) OR Maybe there is another solution in this case. Thank you.
On 19 Apr 2015, at 06:44, Peter Balsianok <balsianok.peter@gmail.com> wrote:
Hi,
Don`t you plan to extend linelog this way:
If filename is '', linelog will write message to standard radius log file (radiusd.conf section log.file). Also if i run radiusd with -X, linelog will write message to standard output.
For me it will be helpful in this case: I want to send access accept for all cases (correct login, incorrect login, wrong password).
In case of correct login, i will send access accept with Context-Name = internet. In rest cases, i will send access accept with Context-Name = wrong. In this case user is able to go just at html page with information: Pleases verify your name or password.
But i loose possibility to say: login was correct or incorrect or bad password (based on radius.log, because all rows will be Login OK)
OR Maybe there is another solution in this case.
Yes, I was planning on adding that functionality, but only in v3.1.x. There's only so many ways you can overload 'filename' so the new config structure for linelog is not backwards compatible. -Arran Arran Cudbard-Bell <a.cudbardb@freeradius.org> FreeRADIUS development team FD31 3077 42EC 7FCD 32FE 5EE2 56CF 27F9 30A8 CAA2
On 19.04.2015 07:44, Peter Balsianok wrote:
But i loose possibility to say: login was correct or incorrect or bad password (based on radius.log, because all rows will be Login OK)
You could use msg_goodpass in your radiusd.conf log section to get some extra attribute logged at the end of you "Login OK" line. We use that to log a whole bunch of attributes, but we are planning use something else (probably linelog) to get rid of auth messages in radius.log. I see that as kind of bad practice because it floods the daemon's log with lot's of messages and you won't see important error messages etc.
Hi, Thank you for your help and answer. Maybe i found another solution (Module-Success-Message attribute). update request { &Module-Success-Message := 'User suspended DUMMY context' } Result in radius.log ... (0) Login OK (User suspended DUMMY context): [ ferencdalibor@orangenet.sk/FNNYWT] (from client localhost port 12901 cli #/111265060/LIHR_USNP-14 atm 1/1/07/22:1.32) ... On Mon, Apr 20, 2015 at 12:44 AM, Jakob Hirsch <jh@plonk.de> wrote:
On 19.04.2015 07:44, Peter Balsianok wrote:
But i loose possibility to say: login was correct or incorrect or bad password (based on radius.log, because all rows will be Login OK)
You could use msg_goodpass in your radiusd.conf log section to get some extra attribute logged at the end of you "Login OK" line.
We use that to log a whole bunch of attributes, but we are planning use something else (probably linelog) to get rid of auth messages in radius.log. I see that as kind of bad practice because it floods the daemon's log with lot's of messages and you won't see important error messages etc.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Sun, Apr 19, 2015 at 07:44:45AM +0200, Peter Balsianok wrote:
But i loose possibility to say: login was correct or incorrect or bad password (based on radius.log, because all rows will be Login OK)
OR Maybe there is another solution in this case.
Personally, I'd leave the standard radius log file as-is, and just use linelog to write out your own separate log file. That way you get to create it in whatever format you desire. Matthew -- Matthew Newton, Ph.D. <mcn4@le.ac.uk> Systems Specialist, Infrastructure Services, I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom For IT help contact helpdesk extn. 2253, <ithelp@le.ac.uk>
participants (4)
-
Arran Cudbard-Bell -
Jakob Hirsch -
Matthew Newton -
Peter Balsianok