3 What happens when a big vendor ignores an RFC
6 FreeRADIUS uses Vendor-Specific attributes to send the Ascend attributes.
7 By default, Ascend NASes send the Ascend specific attributes as NON VSA's,
8 which conflict with new RADIUS attributes assigned by the IETF. This was
9 a very bad screw-up by Ascend that still causes many headaches, but sometimes
10 we have to live with it, so we try to cope the best we can.
12 If you see a large number of messages about invalid Message-Authenticator
13 attribute, you most likely are affected by this problem, and should implement
18 o Enable VSA's on the Ascend/Lucent MAX:
20 This is by far the preferred method ( as it solves many other problems ).
22 Max6000/4000 Series TAOS with Menued Interface:
24 Go to Ethernet->Mod Config->Auth.
25 At the bottom of the menu, change Auth-Compat from "OLD" to "VSA".
26 Save your changes, no reboot is needed.
28 Go to Ethernet->Mod Config->Acct.
29 At the bottom of the menu, change Acct-Compat from "OLD" to "VSA".
30 Save your changes, no reboot is needed.
32 Max TNT/Apex 8000 Series TAOS with CLI:
34 nas> read external-auth
35 nas> set rad-auth-client auth-radius-compat = vendor-specific
36 nas> set rad-acct-client acct-radius-compat = vendor-specific
39 o Enable OLD attributes in FreeRADIUS
41 One note on this, cicsos have an Ascend compatability mode that
42 accepts only the OLD style Ascend attributes, just to make life more
45 You can make FreeRADIUS send the OLD style attributes by prefixing the
46 Ascend attributes with 'X-' in the 'users' file, sql table, ldap directory,
47 attr_filter module, etc...
49 Thus the VSA Ascend attribute:
53 becomes the OLD Ascend attribute: