Internet Protocol version 6 (IPv6) is the next-generation network layer Internet protocol intended to replace version 4 (IPv4) in the TCP/IP suite of protocols. This new version increases Internet global address space to accommodate users and applications that require unique global IP addresses. IPv6 incorporates 128-bit source and destination addresses, providing significantly more addresses than the 32-bit IPv4 addresses. Follow the instructions in this section to configure a WLAN for IPv6 bridging using either the controller GUI or CLI.
Follow these guidelines when using IPv6 bridging
To use IPv6 bridging, multicast must be enabled on the controller.
Hybrid-REAP with central switching is supported for use with IPv6 bridging. Hybrid-REAP with local switching is not supported.
Auto-anchor mobility is not supported for use with IPv6 bridging.
If symmetric mobility tunneling is enabled, all IPv4 traffic is bidirectional tunneled to and from the client, but the IPv6 client traffic is bridged locally.
Clients must support IPv6 with either static stateless auto configuration (such as Windows XP clients) or stateful DHCPv6 IP addressing (such as Windows Vista clients).
Currently, DHCPv6 is supported for use only with Windows Vista clients. For these clients, you must manually renew the DHCPv6 IP address after the client changes VLANs.
Dynamic VLAN function on IPV6 bridging environment is not supported on the Controller software release 6.0 and 7.0.
For stateful DHCPv6 IP addressing to operate properly, you need a switch or router that supports the DHCP for IPv6 feature (such as the Catalyst 3750 switch) and is configured to act like a DHCPv6 server, or you need a dedicated server such as a Windows 2008 server with a built-in DHCPv6 server.
To load the SDM IPv6 template in the Catalyst 3750 switch, enter the sdm prefer dual-ipv4-and-v6 default command and then reset the switch. For more information, see Catalyst 3750 Switch Configuration Guide for Cisco IOS Release 12.2(46)SE.
In controller software release 4.2 or later releases, you can enable IPv6 bridging and IPv4 web authentication on the same WLAN, a combination that previously was not supported. The controller bridges IPv6 traffic from all clients on the WLAN while IPv4 traffic goes through the normal web authentication process. The controller begins bridging IPv6 as soon as the client associates and even before web authentication for IPv4 clients is complete. No other Layer 2 or Layer 3 security policy configuration is supported on the WLAN when both IPv6 bridging and web authentication are enabled. Figure 7-19 shows how IPv6 bridging and IPv4 web authentication can be used on the same WLAN.
In controller software release 6.0 or later releases, all Layer 2 security policies are supported and can be configured when you enable IPv6 bridging on a WLAN.
The Security Policy Completed text box in both the controller GUI and CLI shows "No for IPv4 (bridging allowed for IPv6)" until web
authentication is completed. You can view this text box from the Clients > Detail page on the GUI or from the show client detail CLI command.
Using the GUI to Configure IPv6 Bridging
Some More Details
Basically IPv6 Pass-through and IPv6 Bridging are the same, and are not two separate options, both basically refers on the capability
of passing IPv6 packets from one device to other, which is the only IPv6 option offered on Cisco Wireless LAN controllers
(that will support it) at the moment and that consist on configure Multicast enable on the controller, and then just enable IPv6 on
the WLAN configured on the controller.
Unfortunately the 2100 series controller will have some hardware limitations and will have some unsupported features compared to
another Cisco devices like the 4400 series controller for example, one of those unsupported features will be IPv6 pass through
(bridging) according to the official release notes from the following web link:-
Hello friends. I have several AIR-AP1852I-E-K9 and AIR-AP1562E-E-K9 administered centrally in a controller which is configured in one of the AIR-AP1852I-E-K9. Specifically the AIR-AP1562E-E-K9 are attached with two AIR-ANT2547VG-N antennas connected...
Good day.We have Cisco WLC 2504 with fw ver. 220.127.116.11 that already works with few access points.We purchase new AP 1815i but it has 18.104.22.168 fw ver ( newer than WLC ) All other APs, that we connect to WLC earler, was automaticly updated t...
- AP1 Model : WAP581-A-K9 V01 Serial Number: DNI2141A05W Firmware Version (Active Image): V22.214.171.124- AP2 Model : WAP581-A-K9 V01 Serial Number: DNI2141A04Z Firmware Version (Active Image): V126.96.36.199- AP3 Model : WAP581-A-K9 V01 Serial Number: DNI214...
Hi All,Need help in understanding RRM for 80 MHZ. We have channel width 80 MHz and because of this , we found channel overlapping. We set channel interval time with 10 minutes (default) and DCA set as automatic. But we are not seeing channel change h...
Greetings,I have outdated AIR-BR1310 with broken configuration. This is not about fixing it, but mostly about understanding why it works like it works. BR1310 is connected via trunk interface. Native VLAN have nothing, VLAN 26 is for wireless and VLA...