Probably a lot like choice net. The reason they are called
binary filters really has to do with how they are passed
from the Radius server to the NAS itself. Thus really
the only "Ascend Extension" to a radius server.
Rather than specifying a Framed-Filter in the radius entry,
you build the filter just like you would using the "set filter"
command on the PM. Thus, the entire filter is sent, in
binary form to make it smaller, to the NAS with the Radius
information. They use the 242 and 243 RAs for this
(Ascend-Data-Filter and Ascend-Call-Filter). Not quite
sure the difference between them, though.
> With ChoiceNet you put the filters on a central server and the NAS dynamically
> loads them. No need to put them on each NAS - except for the ethernet port.
> We felt that allowing a NAS to dynamically load a filter for the ethernet is
> just asking for trouble.
Speaking of ChoiceNet, is it like an enhancement to the
proprietary pmcmd stuff? It would be almost impossible for
me to start over porting Radius 2.0 to NT, nor would I
really like to. Are there going to be specs on how to do
the menuing and other features that Radius2.0 is going to offer?
Dale