[RADIATOR] Issues with VSA

[Heikki Vatiainen]

On 4.8.2020 19.40, Brandon Shiers wrote:

> I’m trying to get some Cambium VSA’s passed back to some subscriber 
> modules.  I have the latest Cambium dictionary loaded up in my 
> dictionary file.  I get authenticated and a trace 4 shows the attributes 
> in the reply packet but when I packet sniff them, I am seeing for all 
> the Cambium specific VSA’s under the VSA I get an unknown attribute and 
> then the attribute ID out of the dictionary file.  The AVP does identify 
> the packet as Vendor-Specific (26) and finds the vendor (Motorola 161), 
> which is , which is actually Cambium now for the product we are using.
> 
> Any ideas on what I’m doing wrong?  I have confirmed I have the most 
> recent dictionary file loaded from the vendor and radiator doesn’t 
> complain about the dictionary file on startup.

Looks like there are Cambium-Canopy and Motorol-Canopy attributes in 
circulation. This might be the reason why you see unexpected attributes.

If you can pass me the definitions of the Cambium/Motorola/Canopy 
attributes you have with VENDOR id, attribute names, codes and types 
I'll see how well they match Radiator dictionary.

In addition to this, documentation of what the devices expect would be 
needed to know which attributes to return.

I'm sure this gets solved but sometimes the definitions from different 
sources are not as clear or consistently named as they could.

Thanks,
Heikki


-- 
Heikki Vatiainen <hvn at open.com.au>

Radiator: the most portable, flexible and configurable RADIUS server
anywhere. SQL, proxy, DBM, files, LDAP, TACACS+, PAM, Active Directory,
EAP, TLS, TTLS, PEAP, WiMAX, RSA, Vasco, Yubikey, HOTP, TOTP,
DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, etc.