User's Manual Part 1

126 APCD-LM043-8.0 (DRAFT C)
7: Configuring the CCU
The following example
•Adds EUM ID
60:0a:32 to the Authorization Table, and assigns it the gold grade of
service,
• Saves the new settings, and
• Displays the Authorization Table.
60:00:43> auth add 60:00:83 gold
Added 60:00:83 as gold
60:00:43> save
Basic Config saved
Port Filter Config saved
sntp cfg file saved
Route Config saved
Authorization Database saved
DHCP Server Config saved
60:00:43> auth
EUM ID GOS CLASS TYPE
-----------------------------------
60:00:83 gold static
Default be
Total of 1 entries
60:00:43>
7.10 Configuring RADIUS
This section explains how to configure the RADIUS server and client.
Refer to
WaveRider Attribute Definition on page 325 for the vendor-specific attribute definition.
NOTE: The WaveRider RADIUS client implementation conforms to
RFC’s 2865 and 2866.
7.10.1 Configuring the RADIUS Server
NOTE: There is some confusion about which ports to use for the
RADIUS protocol. From RFC2865, “The early deployment of
RADIUS used UDP port number 1645, which conflicts with the
“datametrics” service. The officially assigned port number for
RADIUS is 1812
.” As well, from RFC2866, “The early deployment
of RADIUS Accounting was done using UDP port number 1646,
which conflicts with the “sa-msg-port” service. The officially
assigned port number for RADIUS Accounting is 1813
.”
As stated earlier, when RADIUS authorization is enabled, the CCU will periodically generate
RADIUS access-request messages for each registered EUM. The responses from the
RADIUS server are then used to maintain the CCU Authorization Table, described in
Authorization Table (CCU only) on page 239. This requires that the RADIUS server has been