
When configured properly, the functions described in the table above could be used to apply an ACL to:
•
All subscribers facilitated within a specific context by applying the ACL to the profile of the subscriber
named
default
.
•
All subscribers facilitated by specific services by applying the ACL to a subscriber profile and then
using the
default subscriber
command to configure the service to use that subscriber as the "default"
profile.
Applying an ACL to Multiple Subscriber via APNs
To apply the ACL to multiple subscribers via APN, use the following configuration:
configure
context dest_context_name [-noconfirm]
apn apn_name
{ ip | ipv6 } access-group acl_list_name [ in | out ]
end
Notes:
•
The ACL to be applied must be in the destination context of the APN (which can be different from the
context where the APN is configured).
•
If neither the
in
nor the
out
keyword is specified, the ACL will be applied to all inbound and outbound
packets.
•
This command supports only one ACL. However, the ACL can have up to 256 rules.
•
Four access-groups can be applied for each APN, for example:
ip access-group acl_list_name_1 in
ip access-group acl_list_name_2 out
ipv6 access-group acl_list_name_3 in
ipv6 access-group acl_list_name_4 out
Applying an ACL to Multiple Subscriber via APNs
If IP ACLs are applied to subscribers via attributes in their profile, the subscriber profile could be configured
locally on the system or remotely on a RADIUS server.
To reduce configuration time, ACLs can alternatively be applied to APN templates for GGSN subscribers.
When configured, any subscriber packets facilitated by the APN template would then have the associated
ACL applied.
This section provides information and instructions for applying an ACL to an APN template.
This section provides the minimum instruction set for applying the ACL list to all traffic within a context.
For more information on commands that configure additional parameters and options, refer to the
Subscriber
Configuration Mode Commands
chapter in the
Command Line Interface Reference
.
Important
ASR 5500 System Administration Guide, StarOS Release 21.5
199
Access Control Lists
Applying a Single ACL to Multiple Subscribers