Dear Alan and Herwin, Thank you for your replies. Plz find in line my responses.
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 ??]
Your configuration here will not do anything. I have no idea why you're doing it, or why you think it will work.
the script I'm using was working fine with sql backends and an old version of freeradius server. Now i'm just trying to addapt it to cassandra DB and I'm using the version 3.1.x of freeradius server. As Herwin pointed, the RAD_CHECK is mapped to the control list and the script uses it to send COA or disconnect AVPs.
Depending on what version you're using, you might have to use RAD_CONFIG instead of RAD_CHECK. They're both mapped to the control list, but in version 3.0.x RAD_CONFIG overwrites the RAD_CHECK (which makes RAD_CHECK effectively a read-only version of the control list)
I'm using the 3.1.x version of Freeradius. I will try with the RAD_CONFIG and see if it works. Sara
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.
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.
participants (2)
-
Alan DeKok -
ICHIBA Sara