My appologies to you. I didn't mean I won't be using the originate-coa file. I actually do. I was talking about the AVP COA-To-Send which I needed to hand over to the control list. The script I'm using used the rad_check list as it is mapped to the control list but it seems that lately this list bacame a read-only. Herwin suggested that I use the rad_config instead. Which I did and It's getting better. Now I can see this Sorry again for the misunderstanding. Mon Jul 20 15:30:22 2015 : Debug: (25) if ("%{control:COA-To-Send}"=="yes") -> TRUE Mon Jul 20 15:30:22 2015 : Debug: (25) if ("%{control:COA-To-Send}"=="yes") { Mon Jul 20 15:30:22 2015 : Debug: (25) update coa { Mon Jul 20 15:30:22 2015 : Debug: (25) EXPAND %{request:User-Name} Mon Jul 20 15:30:22 2015 : Debug: (25) --> test Mon Jul 20 15:30:22 2015 : Debug: (25) User-Name = test Mon Jul 20 15:30:22 2015 : Debug: (25) EXPAND %{request:Acct-Session-Id} Mon Jul 20 15:30:22 2015 : Debug: (25) --> 55ACF3B7-143CF000 Mon Jul 20 15:30:22 2015 : Debug: (25) Acct-Session-Id = 55ACF3B7-143CF000 Mon Jul 20 15:30:22 2015 : Debug: (25) EXPAND %{request:NAS-IP-Address} Mon Jul 20 15:30:22 2015 : Debug: (25) --> 192.168.2.7 Mon Jul 20 15:30:22 2015 : Debug: (25) NAS-IP-Address = 192.168.2.7 Mon Jul 20 15:30:22 2015 : Debug: (25) } # update coa = noop 2015-07-20 13:34 GMT+02:00 Alan DeKok <aland@deployingradius.com>:
On Jul 20, 2015, at 12:27 PM, ICHIBA Sara <ichi.sara@gmail.com> wrote:
If you want to send CoA packets, read raddb/sites-available/ originate-coa
I read it but I'm afraid it's not enough. As the perl module doesn't handle (directly) COA. [right ??]
I have no idea what that means.
If you want to originate CoA packets, that file documents how to do it. If you want some OTHER way to originate CoA packets, it won't work. You MUST use the way which is documented in that file.
Alan DeKok.