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