Anton Maksimenkov wrote:
If I add to "users" file this: When I used exec-program all the attributes I wanted were in the environment.
And how can I exploit it? I get only this: -- $ cat "/home/engineer/acrad.sh" #!/bin/sh printenv > /tmp/exec-program-wait -- "bob" Auth-Type := Local, User-Password == "bob" Reply-Message = "Hello, %u", Exec-Program = "/home/engineer/acrad.sh" -- after "radtest" in /tmp/exec-program-wait I found only $ cat /tmp/exec-program-wait CLIENT_IP_ADDRESS=127.0.0.1 NAS_IP_ADDRESS=255.255.255.255 PATH=/usr/bin:/bin:/usr/sbin:/sbin:/usr/X11R6/bin:/usr/local/bin NAS_PORT=0 USER_PASSWORD="bob" USER_NAME="bob"
See? Its working perfectly. Your radtest caused the above.
But this is far less than what I wait for... I need to do the same that SQL accounting do.
Your radtest DOES NOT cause accounting requests to occur as well.
If I look at raddb/pgsql-voip.conf, I can see <snip>
I read this. But I just newbie, sorry. I tried this exec echo { wait = yes program = "/home/engineer/acrad.sh %{User-Name}" input_pairs = request output_pairs = reply } instantiate { exec ... but it seems that program not started at all.
packet_type = Accounting-Request And make sure you instantiate the "echo" instance of the exec module under the radiusd accounting section