Re: Ascend Filters and RADIUS

Dale E. Reed Jr. ( (no email) )
Thu, 26 Mar 1998 08:03:15 -0800

Scott Lagos wrote:
>
> You mentioned that we send the filters up to the ts in binary. I assume
> that if I put the string as it appears below in the RADConfig table that
> RADIUS will automatically convert it to binary because of the 4 in the
> dictionary table. Correct?

Correct. RadiusNT knows how to handle Ascend-Binary-Filter type
attributes.

> # Filter to stop all WWW packets#
>
> Ascend-Data-Filter = "ip in drop proto 6 dstport = 80",
> Ascend-Data-Filter = "generic in forward 0 0 0",
> Ascend-Data_filter = "generic out forward 0 0 0"#
>
> So in RADConfig I would have something like....
>
> RadIdConfig AccountID RaddAtrribID Data Value
> x x 242 "ip in drop proto 6 ds.....'
> .
> .

Make sure your data field in RadConfigs is large enough. People have ran
into a length issue with the filter.

> Also, what is the deal with Ascend-Data_filter ? That underscore appears
> in the last line of all the Ascend samples but I do not see it in the
> Dictionary. Is that just a mistake.

Its a typo. They should all be Ascend-Data-Filter.

-- Dale E. Reed Jr.  (daler@iea-software.com)_________________________________________________________________       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |   http://www.iea-software.com