Installation Guide

Table Of Contents
Task 5: Configuring security PMP 450i and PTP 450i Configuration and User
Guide
AP PreShared Key - The AP acts as the authentication server to its SMs and will
make use of a user-configurable pre-shared authentication key. The operator enters
this key on both the AP and all SMs desired to register to that AP. There is also an
option of leaving the AP and SMs at their default setting of using the “Default Key”.
Due to the nature of the authentication operation, if you want to set a specific
authentication key, then you MUST configure the key on all of the SMs and reboot
them BEFORE enabling the key and option on the AP. Otherwise, if you configure
the AP first, none of the SMs is able to register.
RADIUS AAA - When RADIUS AAA is selected, up to 3 Authentication Server
(RADIUS Server) IP addresses and Shared Secrets can be configured. The IP
address(s) configured here must match the IP address(s) of the RADIUS server(s).
The shared secret(s) configured here must match the shared secret(s) configured in
the RADIUS server(s). Servers 2 and 3 are meant for backup and reliability, not for
splitting the database. If Server 1 doesn’t respond, Server 2 is tried, and then server
3. If Server 1 rejects authentication, the SM is denied entry to the network, and
does not progress trying the other servers. For more information on configuring the
PMP 450i network to utilize a RADIUS server, see Task 15: Configuring a RADIUS
server on page 184
Filtering protocols and ports
You can filter (block) specified protocols and ports from leaving the AP and SM and
entering the network. This protects the network from both intended and inadvertent
packet loading or probing by network users. By keeping the specified protocols or
ports off the network, this feature also provides a level of protection to users from
each other.
Protocol and port filtering is set per AP/SM. Except for filtering of SNMP ports,
filtering occurs as packets leave the AP/SM. If a SM is configured to filter SNMP,
then SNMP packets are blocked from entering the SM and, thereby, from
interacting with the SNMP portion of the protocol stack on the SM.
Port Filtering with NAT Enabled
Where NAT is enabled, you can filter only the three user-defined ports. The
following are example situations in which you can configure port filtering where
NAT is enabled.
To block a subscriber from using FTP, you can filter Ports 20 and 21 (the FTP ports)
for both the TCP and UDP protocols.
To block a subscriber from access to SNMP, you can filter Ports 161 and 162 (the
SNMP ports) for both the TCP and UDP protocols.
In only the SNMP case, filtering occurs before the packet interacts with the
protocol stack.
pmp-0957 (April 2015) 85