ascend-data-filter in freeradius v3.0.x - interaction with RFC6929?
Hello, I am using the freeradius-server version V3.0.x and have the problem that the data specified in the users file for the Ascend-Data-Filter attribute (from the Ascend vendor space) is not correct sent in the radius access-accept msg. Is this related to the rfc6929 extended-attribute 242 that I need to do something specific, the Ascend-Data-filter is sent as part of the vendor space Ascend(=529), so there is no conflict with the 242 extended-attribute of rfc6929? My users file contains the following: Ascend-Data-Filter = 0x01010100010203040a0b0c0d05200600000504d2020200000000000000000000, The radius output is : (12) Sent Access-Accept Id 222 from 138.203.10.191:1812 to 138.203.10.123:64397 length 0 .... (12) Alc-Default-Router = 10.50.2.1 (12) Ascend-Data-Filter = 0x (12) Class = 0x41444d494e31 (12) Finished request Waking up in 4.9 seconds. (12) <done>: Cleaning up request packet ID 222 with timestamp +184 Ready to process requests My wireshark shows for the ascend-data-filter the following " 1a 28 00 00 02 11 f2 22 20 27 7a 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00" In a previous version of freeradius V2.1.12. this is working fine, but I stepped up to version V3.0.8 to have support for the radius extensions RFC6929. Thanks, Regards, Katrien.
On Sep 8, 2015, at 9:38 AM, Vereecke, Katrien (Katrien) <katrien.vereecke@alcatel-lucent.com> wrote:
I am using the freeradius-server version V3.0.x and have the problem that the data specified in the users file for the Ascend-Data-Filter attribute (from the Ascend vendor space) is not correct sent in the radius access-accept msg.
I've pushed a fix to the v3.0.x branch. The hex version of the Ascend-Data-Filter wasn't being parsed properly. It also wasn't being printed properly. I've added tests for encoding / decoding on the wire, and printing / parsing of Ascend-Data-Filter, so that the problem doesn't occur again. Alan DeKok.
Thanks Alan, it's working fine now. Kind Regards, Katrien. -----Original Message----- From: Freeradius-Users [mailto:freeradius-users-bounces+katrien.vereecke=alcatel-lucent.com@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Tuesday, September 08, 2015 16:18 To: FreeRadius users mailing list Subject: Re: ascend-data-filter in freeradius v3.0.x - interaction with RFC6929? On Sep 8, 2015, at 9:38 AM, Vereecke, Katrien (Katrien) <katrien.vereecke@alcatel-lucent.com> wrote:
I am using the freeradius-server version V3.0.x and have the problem that the data specified in the users file for the Ascend-Data-Filter attribute (from the Ascend vendor space) is not correct sent in the radius access-accept msg.
I've pushed a fix to the v3.0.x branch. The hex version of the Ascend-Data-Filter wasn't being parsed properly. It also wasn't being printed properly. I've added tests for encoding / decoding on the wire, and printing / parsing of Ascend-Data-Filter, so that the problem doesn't occur again. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (2)
-
Alan DeKok -
Vereecke, Katrien (Katrien)