Filter
Top Products
147 | IPv6 Support DellPowerConnectW-SeriesArubaOS6.2 | User Guide
l Remote AP supports IPv6 clients in tunnel forwarding mode only. The Remote AP bridge and split-tunnel
forwarding modes do not support IPv6 clients. Secure Thin Remote Access Point (STRAP) cannot support IPv6
clients.
l The controller cannot terminate VPNs for IPv6 clients.
l VPN authentication cannot be performed for IPv6 clients.
l ArubaOS does not support RADIUS over IPv6 as an authentication protocol.
l Authentication of management users on IPv6 clients is not supported.
l A client can have an both IPv4 address and an IPv6 address, but the controller does not relate the states of the
IPv4 and IPv6 addresses on the same client. For example, if an IPv6 user session is active on a client, an IPv4
user session on the same client will be deleted if the idle timeout for the IPv4 session is reached.
IPv6 best practices:
l IPv6 should be globally enabled.
(host) (config) #ipv6 enable
l Uplink port must be trusted. This is the same behavior as IPv4.
l Ensure validuser session ACL does not block IPv6 traffic.
l There must not be any ACLs that drop ICMPv6 or DHCPv6 traffic. It is acceptable to drop DHCPv6 traffic if
the deployment uses StateLess Address Auto Configuration (SLAAC) only.
l If controller provides Router Advertisements (RA):
n IPv6 VLAN interface address must be configured which maps to the prefixes configured.
n 3 prefixes limit is enforced.
n Controller does not support off-link prefixes.
l If controller does not provide RA:
n It is not recommended to advertise too many prefixes in RA.
n Controller limits four IPv6 address per user including link-local address (fe80::/64). When a large number of
prefixes are configured on the upstream router, the client can use an IPv6 address that is beyond the allowed
limit of number of IPv6 address per user.