EGO supports IPv6. Among other benefits of IPv6, longer address lengths (128 bit) result in increased address availability for networked devices, allowing you to allocate addresses in large blocks.
Notes on EGO support for IPv6 include the following:
Scope: You must assign global unicast addresses to IPv6-enabled hosts.
Compatibility: IPv4 and IPv6 hosts can only communicate with corresponding hosts of the same type or with dual-stack hosts. However, dual-stack hosts can communicate with both IPv4 and IPv6 hosts, allowing compatibility between the two host types. Therefore, if you have a mixed cluster with both IPv4 and IPv6 hosts, configure it to be dual-stack.
DNS cache: To locally store host names and mapped addresses (both IPv4 and IPv6 types), EGO uses a host DNS cache.
Hosts file: You can define a hosts file to provide address-to-name translation. Create hosts in $EGO_CONFDIR (Linux/UNIX) or %EGO_CONFDIR% (Windows). This file is most useful if you have multi-homed hosts (hosts with multiple interface cards/nics) or dual-stack hosts. It assists you in authenticating hosts, and viewing host mappings in cases where there are multiple addresses and names.
To enable, disable, and/or configure IPv6 support, set these parameters.
Set EGO_DUALSTACK_PREFER_IPV6 in ego.conf to sort address presentation in the cache library. For example, set EGO_DUALSTACK_PREFER_IPV6 to “Y" so that IPv6 addresses appear at the top of the list; set it to “N" so that IPv4 addresses appear at the top. This parameter only affects the sort order of the list, and communication between dual-stack hosts. It does not enable IPv6, nor does it filter the address list.