Hello Jason -
I would be interested to see a trace 5 debug from Radiator showing
the packet dump of this attribute (it looks bogus from what you show
below).
Either your equipment has a bug (not unusual), or you will indeed
need to get the specifications for the vendor-specifics from
Entera
I'm getting errors regarding Attribute number # (vendor 5624) not in
dictionary. Radiator is receiving packets from an Enterasys SSR8600. Do I
need to get a hold of attributes for the SSR8600? Will this aid in receiving
info on Accounting-Requests? I am rather new to radiator and have got
Authenti
ect: (RADIATOR) vendor specific attributes per subscriber
>
> (Mike: Thanks, the ${$_[0}}->add_attr(..., ...) works perfect.)
>
> We're experimenting with the Cisco service selection gateway (SSG) for ADSL.
The SSG is a router and a radius client. Depending on some vendor specific
attr
(Mike: Thanks, the
${$_[0}}->add_attr(..., ...) works perfect.)
We're experimenting with the
Cisco service selection gateway (SSG) for ADSL. The SSG is a router and a radius
client. Depending on some vendor specific attributes, it sets up some routes per
subscriber (client ip-address). So
