IPv6 Compatibility¶
As of version 6.4, many features of bonding are now IPv6-compatible. However, some features are still non-compatible or only partially compatible. This document is meant to serve as a concise summary of IPv6 compatibility in bonding.
Note
Legacy nodes (pre-6.4) do not support any IPv6 features. All IPv6-related configuration parameters in a configuration update will be ignored by a legacy node.
Complete or Partial Compatibility¶
- Aggregators and private WAN routers can be configured with IPv6 addresses, however both node types still require an IPv4 address at this time, even if the intention is to operate only via IPv6.
- Full IPv6 support for internal tunnel traffic.
- All leg address schemes support IPv6 with the exception of DHCP, which is an IPv4 protocol.
- Connected IPs, routes, and private WAN outbound gateways support IPv6.
- QoS and classification profiles support IPv6 network addresses and protocols.
- Flow collection is fully IPv6 compatible.
Warning
When using a PPPoE address scheme with IPv6 links, only Router Advertisements are supported. DHCPv6 support in this scenario may be re-evaluated at a later date.
Non-Compatible¶
- CPE NAT IPs do not support IPv6 addresses.
- Private WAN port forward, NAT, & NAT via PWAN router rules do not support IPv6 addresses
- Tunnel bypass does not currently support IPv6 traffic classification
- TCP Proxy does not currently support IPv6 traffic
- IPv6 addresses are not managed using allocations and delegations at this time
Note
As per general IPv6 recommendations, features employing NAT do not support IPv6