- Preface
- Using the Command-Line Interface
- Using the Web Graphical User Interface
-
- Configuring the Switch for Access Point Discovery
- Configuring Data Encryption
- Configuring Retransmission Interval and Retry Count
- Configuring Adaptive Wireless Intrusion Prevention System
- Configuring Authentication for Access Points
- Converting Autonomous Access Points to Lightweight Mode
- Using Cisco Workgroup Bridges
- Configuring Probe Request Forwarding
- Optimizing RFID Tracking
- Configuring Country Codes
- Configuring Link Latency
- Configuring Power over Ethernet
-
- Preventing Unauthorized Access
- Controlling Switch Access with Passwords and Privilege Levels
- Configuring TACACS+
- Configuring RADIUS
- Configuring Kerberos
- Configuring Local Authentication and Authorization
- Configuring Secure Shell (SSH)
- Configuring Secure Socket Layer HTTP
- Configuring IPv4 ACLs
- Configuring IPv6 ACLs
- Configuring DHCP
- Configuring IP Source Guard
- Configuring Dynamic ARP Inspection
- Configuring IEEE 802.1x Port-Based Authentication
- Configuring Web-Based Authentication
- Configuring Port-Based Traffic Control
- Configuring IPv6 First Hop Security
- Configuring Cisco TrustSec
- Configuring Wireless Guest Access
- Managing Rogue Devices
- Classifying Rogue Access Points
- Configuring wIPS
- Configuring Intrusion Detection System
-
- Administering the System
- Performing Switch Setup Configuration
- Configuring Right-To-Use Licenses
- Configuring Administrator Usernames and Passwords
- Configuring 802.11 parameters and Band Selection
- Configuring Aggressive Load Balancing
- Configuring Client Roaming
- Configuring Application Visibility and Control
- Configuring Voice and Video Parameters
- Configuring RFID Tag Tracking
- Configuring Location Settings
- Monitoring Flow Control
- Configuring SDM Templates
- Configuring System Message Logs
- Configuring Online Diagnostics
- Managing Configuration Files
- Configuration Replace and Configuration Rollback
- Working with the Flash File System
- Working with Cisco IOS XE Software Bundles
- Troubleshooting the Software Configuration
- Index
Configuring IPv6 ACL
Prerequisites for IPv6 ACL
You can filter IP Version 6 (IPv6) traffic by creating IPv6 access control lists (ACLs) and applying them to interfaces similarly to the way that you create and apply IP Version 4 (IPv4) named ACLs. You can also create and apply input router ACLs to filter Layer 3 management traffic when the switch is running the IP base feature set.
Restrictions for IPv6 ACL
With IPv4, you can configure standard and extended numbered IP ACLs, named IP ACLs, and MAC ACLs. IPv6 supports only named ACLs.
The switch does not support matching on these keywords: flowlabel, routing header, and undetermined-transport.
The switch does not support reflexive ACLs (the reflect keyword).
The switch does not apply MAC-based ACLs on IPv6 frames.
When configuring an ACL, there is no restriction on keywords entered in the ACL, regardless of whether or not they are supported on the platform. When you apply the ACL to an interface that requires hardware forwarding (physical ports or SVIs), the switch checks to determine whether or not the ACL can be supported on the interface. If not, attaching the ACL is rejected.
If an ACL is applied to an interface and you attempt to add an access control entry (ACE) with an unsupported keyword, the switch does not allow the ACE to be added to the ACL that is currently attached to the interface
Information About IPv6 ACL
An access control list (ACL) is a set of rules used to limit access to a particular interface (for example, if you want to restrict a wireless client from pinging the management interface of the controller). ACLs are configured on the switchnd applied to the management interface, the AP-manager interface, any of the dynamic interfaces, or a WLAN to control data traffic to and from wireless clients or to the controller central processing unit (CPU) to control all traffic destined for the CPU.
You can also create a preauthentication ACL for web authentication. Such an ACL is used to allow certain types of traffic before authentication is complete.
IPv6 ACLs support the same options as IPv4 ACLs including source, destination, source and destination ports.
![]() Note | You can enable only IPv4 traffic in your network by blocking IPv6 traffic. That is, you can configure an IPv6 ACL to deny all IPv6 traffic and apply it on specific or all WLANs. |
Understanding IPv6 ACLs
IPv6 router ACLs are supported on outbound or inbound traffic on Layer 3 interfaces, which can be routed ports, switch virtual interfaces (SVIs), or Layer 3 EtherChannels. IPv6 router ACLs apply only to IPv6 packets that are routed.
IPv6 port ACLs are supported on inbound traffic on Layer 2 interfaces only. IPv6 port ACLs are applied to all IPv6 packets entering the interface.
A switch running the IP base feature set supports only input router IPv6 ACLs. It does not support port ACLs or output IPv6 router ACLs.
![]() Note | If you configure unsupported IPv6 ACLs, an error message appears and the configuration does not take affect. |
The switch does not support VLAN ACLs (VLAN maps) for IPv6 traffic.
When an input router ACL and input port ACL exist in an SVI, packets received on ports to which a port ACL is applied are filtered by the port ACL. Routed IP packets received on other ports are filtered by the router ACL. Other packets are not filtered.
When an output router ACL and input port ACL exist in an SVI, packets received on the ports to
which a port ACL is applied are filtered by the port ACL. Outgoing routed IPv6 packets are filtered by the router ACL. Other packets are not filtered.
![]() Note | If any port ACL (IPv4, IPv6, or MAC) is applied to an interface, that port ACL is used to filter packets, and any router ACLs attached to the SVI of the port VLAN are ignored. |
Types of ACL
Per User IPv6 ACL
For the per-user ACL, the full access control entries (ACE) as the text strings are configured on the ACS.
The ACE is not configured on the Controller. The ACE is sent to the switch in the ACCESS-Accept attribute and applies it directly for the client. When a wireless client roams into an foreign switch, the ACEs are sent to the foreign switch as an AAA attribute in the mobility Handoff message.
Filter ID IPv6 ACL
For the filter-Id ACL, the full ACEs and the acl name(filter-id) is configured on the switch and only the filter-id is configured on the ACS. The filter-id is sent to the switch in the ACCESS-Accept attribute, and the switch looks up the filter-id for the ACEs, and then applies the ACEs to the client. When the client L2 roams to the foreign switch, only the filter-id is sent to the foreign switch in the mobility Handoff message. The foreign switch has to configure the filter-id and ACEs beforehand.
Downloadable IPv6 ACL
For the downloadable ACL(dACL), the full ACEs and the dacl name are all configured on the ACS only.
![]() Note | The controller does not configure any ACL. |
The ACS sends the dacl name to the switch in its ACCESS-Accept attribute, which takes the dacl name and sends the dACL name back to the ACS, for the ACEs, using the access-request attribute.
The ACS responds to the corresponding ACEs of the switch in the access-accept attribute. When the wireless client roams to an foreign switch, only the dacl name is sent to the foreign switch in the mobility Handoff message. The foreign switch contacts the ACS server with the dacl name to retrieve the ACEs.
IPv6 ACLs and Switch Stacks
The stack master supports IPv6 ACLs in hardware and distributes the IPv6 ACLs to the stack members.
![]() Note | For full IPv6 functionality in a switch stack, all stack members must be running the IP services feature set. |
If a new switch takes over as stack master, it distributes the ACL configuration to all stack members. The member switches sync up the configuration distributed by the new stack master and flush out entries that member switches sync up the configuration distributed by the new stack master and flush out entries that are not required.
When an ACL is modified, attached to, or detached from an interface, the stack master distributes the change to all stack members.
Configuring IPv6 ACLs
To filter IPv6 traffic, you perform these steps:
Before configuring IPv6 ACLs, you must select one of the dual IPv4 and IPv6 SDM templates.
1. Create an IPv6 ACL, and enter IPv6 access list configuration mode.
2. Configure the IPv6 ACL to block (deny) or pass (permit) traffic.
3. Apply the IPv6 ACL to the interface where the traffic needs to be filtered.
4. Apply the IPv6 ACL to an interface. For router ACLs, you must also configure an IPv6 address on the Layer 3 interface to which the ACL is applied.
DETAILED STEPS
Default IPv6 ACL Configuration
There are no IPv6 ACLs configured or applied.
Interaction with Other Features and Switches
-
If an IPv6 router ACL is configured to deny a packet, the packet is not routed. A copy of the packet is sent to the Internet Control Message Protocol (ICMP) queue to generate an ICMP unreachable message for the frame.
-
If a bridged frame is to be dropped due to a port ACL, the frame is not bridged.
-
You can create both IPv4 and IPv6 ACLs on a switch or switch stack, and you can apply both IPv4 and IPv6 ACLs to the same interface. Each ACL must have a unique name; an error message appears if you try to use a name that is already configured.
You use different commands to create IPv4 and IPv6 ACLs and to attach IPv4 or IPv6 ACLs to the same Layer 2 or Layer 3 interface. If you use the wrong command to attach an ACL (for example, an IPv4 command to attach an IPv6 ACL), you receive an error message.
- You cannot use MAC ACLs to filter IPv6 frames. MAC ACLs can only filter non-IP frames.
-
If the hardware memory is full, for any additional configured ACLs, packets are dropped to the CPU, and the ACLs are applied in software. When the hardware is full a message is printed to the console indicating the ACL has been unloaded and the packets will be dropped on the interface.

Note
Only packets of the same type as the ACL that could not be added (ipv4, ipv6, MAC) will be dropped on the interface.
How To Configure an IPv6 ACL
Creating IPv6 ACL
Beginning in privileged EXEC mode, follow these steps to create an IPv6 ACL:
1.
configure terminal
2.
ipv6
access-list
acl_name
3.
{deny|permit}
protocol
4.
{deny|permit}
tcp
5.
{deny|permit}
udp
6.
{deny|permit}
icmp
7.
end
8.
show
ipv6
access-list
9.
copy
running-config
startup-config
DETAILED STEPS
Applying an IPv6 to an Interface
This section describes how to apply IPv6 ACLs to network interfaces. You can apply an IPv6 ACL to outbound or inbound traffic on layer 2 and Layer 3 interfaces. You can apply IPv6 ACLs only to inbound management traffic on Layer 3 interfaces.
Beginning in privileged EXEC mode, follow these steps to control access to an interface:
1.
configure terminal
2.
interface
interface_id
3.
no
switchport
4.
ipv6
address
ipv6_address
5.
ipv6
traffic-filter
acl_name
6.
end
7.
show
running-config
interface
tenGigabitEthernet
1/0/3
8.
copy
running-config
startup-config
DETAILED STEPS
Creating WLAN IPv6 ACL
1.
ipv6
traffic-filter
acl
acl_name
2.
ipv6
traffic-filter
acl
web
DETAILED STEPS
| Command or Action | Purpose |
|---|
Switch(config-wlan)# ipv6 traffic-filter acl <acl_name>
Switch(config-wlan)#ipv6 traffic-filter acl web <acl_name-preauth>
Verifying IPv6 ACL
Displaying IPv6 ACLs
You can display information about all configured access lists, all IPv6 access lists, or a specific access list by using one or more of the privileged EXEC commands.
| Command or Action | Purpose |
|---|
Configuration Examples for IPv6 ACL
Example: Creating IPv6 ACL
![]() Note | Logging is supported only on Layer 3 interfaces. |
Switch(config)# ipv6 access-list CISCO Switch(config-ipv6-acl)# deny tcp any any gt 5000 Switch (config-ipv6-acl)# deny ::/0 lt 5000 ::/0 log Switch(config-ipv6-acl)# permit icmp any any Switch(config-ipv6-acl)# permit any any
Example: Applying IPv6 ACLs
Switch(config)# interface TenGigabitEthernet 1/0/3 Switch(config-if)# no switchport Switch(config-if)# ipv6 address 2001::/64 eui-64 Switch(config-if)# ipv6 traffic-filter CISCO out
Example: Displaying IPv6 ACLs
Switch #show access-lists
Extended IP access list hello
10 permit ip any any
IPv6 access list ipv6
permit ipv6 any any sequence 10
Switch# show ipv6 access-list
IPv6 access list inbound
permit tcp any any eq bgp (8 matches) sequence 10
permit tcp any any eq telnet (15 matches) sequence 20
permit udp any any sequence 30
IPv6 access list outbound
deny udp any any sequence 10
deny tcp any any eq telnet sequence 20
Example: Configuring RA Throttling and NS Suppression
This task describes how to create an RA throttle policy in order to help the power-saving wireless clients from being disturbed by frequent unsolicited periodic RA's. The unsolicited multicast RA is throttled by the controller.
Enable IPv6 on the client machine.
1.
configure terminal
2.
ipv6 nd ra-throttler policy Mythrottle
3.
throttle-period 20
4.
max-through 5
5.
allow at-least 3 at-most 5
6.
switch (config)# vlan configuration 100
7.
ipv6 nd suppress
8.
ipv6 nd ra-th attach-policy attach-policy_name
9.
end
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
configure terminal Example: Switch# configure terminal
|
Enters global configuration mode. |
| Step 2 | ipv6 nd ra-throttler policy Mythrottle Example: Switch (config)# ipv6 nd ra-throttler policy Mythrottle
| Creates a RA throttler policy called Mythrottle. |
| Step 3 | throttle-period 20 Example: Switch (config-nd-ra-throttle)# throttle-period 20
| Determines the time interval segment during which throttling applies. |
| Step 4 | max-through 5 Example: Switch (config-nd-ra-throttle)# max-through 5
| Determines how many initial RA's are allowed. |
| Step 5 | allow at-least 3 at-most 5 Example: Switch (config-nd-ra-throttle)# allow at-least 3 at-most 5
| Determines how many RA's are allowed after the initial RAs have been transmitted, until the end of the interval segment. |
| Step 6 | switch (config)# vlan configuration 100 Example: Switch (config)# vlan configuration 100
| Creates a per vlan configuration. |
| Step 7 | ipv6 nd suppress Example: Switch (config)# ipv6 nd suppress
| Disables the neighbor discovery on the Vlan. |
| Step 8 | ipv6 nd ra-th attach-policy attach-policy_name Example: Switch (config)# ipv6 nd ra-throttle attach-policy attach-policy_name
| Enables the router advertisement throttling. |
| Step 9 | end Example: Switch(config)# end
| Returns to privileged EXEC mode. Alternatively, you can also press Ctrl-Z to exit global configuration mode. |
Example: Configuring RA Guard Policy
1.
ipv6 nd raguard policy MyPloicy
2.
trusted-port
3.
device-role router
4.
interface tenGigabitEthernet 1/0/1
5.
ipv6 nd raguard attach-policyMyPolicy
6.
vlan configuration 19-21,23
7.
ipv6 nd suppress
8.
ipv6 snooping
9.
ipv6 nd raguard attach-policy MyPolicy
10.
ipv6 nd ra-throttler attach-policy Mythrottle
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | ipv6 nd raguard policy MyPloicy Example: Switch (config)# ipv6 nd raguard policy MyPolicy
| |
| Step 2 | trusted-port Example: Switch (config-nd-raguard)# trusted-port
| Configures the trusted port for the policy created above. |
| Step 3 | device-role router Example: Switch (config-nd-raguard)# device-role [host|monitor|router|switch] Switch (config-nd-raguard)# device-role router | Defines the trusted device that can send RAs to the trusted port created above. |
| Step 4 | interface tenGigabitEthernet 1/0/1 Example: Switch (config)# interface tenGigabitEthernet 1/0/1
| Configures the interface to the trusted device. |
| Step 5 | ipv6 nd raguard attach-policyMyPolicy Example: Switch (config-if)# ipv6 nd raguard attach-policy Mypolicy
| Configures and attaches the policy to trust the RA's received from the port. |
| Step 6 | vlan configuration 19-21,23 Example: Switch (config)# vlan configuration 19-21,23
| Configures the wireless client vlans. |
| Step 7 |
ipv6 nd suppress Example: Switch (config-vlan-config)# ipv6 nd suppress
|
Suppresses the ND messages over wireless. |
| Step 8 |
ipv6 snooping Example: Switch (config-vlan-config)# ipv6 snooping
|
Captures IPv6 traffic. |
| Step 9 |
ipv6 nd raguard attach-policy MyPolicy Example: Switch (config-vlan-config)# ipv6 nd raguard attach-policy Mypolicy
|
Attaches the RA Guard policy to the wireless client vlans. |
| Step 10 |
ipv6 nd ra-throttler attach-policy Mythrottle Example: Switch (config-vlan-config)#ipv6 nd ra-throttler attach-policy Mythrottle
|
Attaches the RA throttling policy to the wireless client vlans. |
Example: Configuring IPv6 Neighbor Binding
1.
ipv6 neighbor binding [vlan ]19 2001:db8::25:4 interface tenGigabitEthernet 1/0/3 aaa.bbb.ccc
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
| Step 1 | ipv6 neighbor binding [vlan ]19 2001:db8::25:4 interface tenGigabitEthernet 1/0/3 aaa.bbb.ccc Example: Switch (config)# ipv6 neighbor binding vlan 19 2001:db8::25:4 interface tenGigabitEthernet 1/0/3 aaa.bbb.ccc
| Sets and validates the neighbor 2001:db8::25: 4 only valid when transmitting on VLAN 19 through interface te1/0/3 with the source mac-address as aaa.bbb.ccc. |
Additional References
Related Documents
| Related Topic | Document Title |
|---|---|
| IPv6 command reference | IPv6 Command Reference (Catalyst 3650 Switches) |
| ACL configuration | Security Configuration Guide (Catalyst 3650 Switches) |
Error Message Decoder
| Description | Link |
|---|---|
|
To help you research and resolve system error messages in this release, use the Error Message Decoder tool. |
https://www.cisco.com/cgi-bin/Support/Errordecoder/index.cgi |
MIBs
| MIB | MIBs Link |
|---|---|
| All supported MIBs for this release. |
To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco MIB Locator found at the following URL: |
Technical Assistance
| Description | Link |
|---|---|
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. |
Feature Information for IPv6 ACLs
|
Feature |
Release |
Modification |
|---|---|---|
|
IPv6 ACL Functionality |
Cisco IOS XE 3.3SE |
This feature was introduced. |
Feedback