[RADIATOR] Issues with VSA

[Heikki Vatiainen]

On 4.8.2020 20.20, Brandon Shiers wrote:

> I've attached a copy of their dictionary file.  For you to peruse.

Getting back to this before the month rolls over, there's now a new 
dictionary file dictionary.cambium-motorola-161 in Radiator's goodies 
directory. It will be part of next release.

Those who are interested in using it can update their Radiator 
configuration file with something like this:

DictionaryFile /opt/radiator/radiator/dictionary, 
/opt/radiator/radiator/goodies/dictionary.cambium-motorola-161

Vendor 161 was already defined with partly same attribute numbers for 
Motorola's WiMAX gear. The above configuration effectively overrides the 
WiMAX definitions with Cambium definitions.

Cambium documentation and discussion forums indicate that the currently 
preferred attribute naming uses Cambium prefix. For this reason 
dictionary.cambium-motorola-161 first lists Motorola- prefixed attribute 
names and then the respective Cambium- names. For example:

Motorola-Canopy-LPULCIR      1    integer
is followed by
Cambium-Canopy-LPULCIR       1    integer

What this means is that when Radiator receives vendor 161 attribute 1, 
it will name it Cambium-Canopy-LPULCIR. If the name needs to be sent 
over the network, both names map to vendor 161 attribute 1 with type 
integer. In other words, Motorola-Canopy-LPULCIR is an alias for the 
preferred name Cambium-Canopy-LPULCIR.

Thanks again Brandon for your help with this.
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.