Single RADIUS Class attribute supported by HP's Comware - Bug or Enhancement?
aland at deployingradius.com
Fri May 30 14:59:08 CEST 2014
Nick Lowe wrote:
> This seems obviously incorrect as, to my mind, there is simply no such
> thing as 'limited RFC' support. Either a product complies with a
> standard or it does not.
Unfortunately, that's not how RADIUS works. The documents have a
number of SHOULD and SHOULD NOT statements. These make the specs very
The documents are also *silent* on a number of subjects. This makes
certain insane behavior "allowed", because it's not forbidden. :(
As for the Class attribute, pretty much every NAS vendor supports one,
and only one Class attribute. If you're lucky, they support more than 8
bytes for Class. Asking anyone to support multiple Class attributes is
probably a waste of time.
> Please can I get some weight of consensus here that this is just as
> absurd as I think it is from others experienced in the RADIUS space?
Most of the RADIUS space is absurd.
To be honest, there's probably another way to solve the problem you're
seeing. Describe it in detail, and we may be able to help you.
More information about the Freeradius-Users