NETWORK CONFIGURATION
Example 1-- No IPv6 support (Applies to all platforms)
No change required. IPv6 is off by default.
Example 2 -- UNIX platform supporting all valid IPv4 and IPv6 addresses
TCP_EnableIPv6=1
Example 2 assumes that no ports are bound to any addresses. By default, on UNIX®, the single unbound listening socket is IPv6. The IPv6 socket can receive connections from any IPv4 or IPv6 address.
Example 3 -- Microsoft Windows platform supporting all valid IPv4 and IPv6 addresses
TCPIP=TCP, 0, 15, 0
TCPIP6=TCP, 0, 15, 0
PORTS=TCPIP,TCPIP6
TCPIP_TCPIPADDRESS=0,[::ffff:0.0.0.0]:1352
SMTPNotesPort=TCPIP,TCPIP6
Example 3 assumes that no ports are bound to any addresses. On Microsoft® Windows®, by default, the TCPIP6 port is an IPv6 socket because IPv6 is enabled. The TCPIP port is an IPv4 socket, because its bound address has the IPv4 format. Both listen to all addresses because the bound address is 0. The SMTPNotesPort variable is required to force the SMTP listener to listen on two sockets -- one for IPv4 and one for IPv6.
Example 4 -- UNIX (but not Linux 2.4) partitioned servers. Each server listens to its assigned IPv4 and IPv6 addresses only
Each Server:
TCPIP_TCPIPADDRESS=0,9.33.162.84:1352
TCPIP6_TCPIPADDRESS=0,[fe80::209:6bff:fecd:5b93]:1352
Example 5 -- Microsoft Windows (and Linux 2.4) partitioned servers. Each server listens to its assigned IPv4 and IPv6 addresses only
TCPIP6_TCPIPADDRESS=0,[fe80::209:6bff:fecd:5b93%4]:1352
The difference here is that Microsoft Windows and Linux® 2.4 require the use of the zone in the address even for addresses bound to listeners if the address is a link local address. The same effect can also be achieved as shown in Example 5A.
Examle 5A -- Microsoft Windows and Linux 2.4 partitioned servers. Each server listens to its assigned IPv4 and IPv6 addresses only
For each server:
TCP_DefaultZone=4
Example 6 -- Any client wants to make outbound IPv4 connections
No change required
Example 6A -- A UNIX client (not Linux 2.4) wants to make an outbound IPv6 connection
Connect to an IPv6 address, or to a DNS or hosts file resident name that resolves to an IPv6 address.
Example 7 -- Microsoft Windows/Linux 2.4 client wants to make outbound connection via IPv6
Connect to an IPv6 address, or to a DNS or hosts file resident name that resolves to an IPv6 address. If the address is a link local address, it must include the zone, such as fe80::209:6bff:fecd:5b93%4, or the local NOTES.INI file must contain a default zone, or the zone must be included in the local bound address. Such addresses must NEVER be stored in DNS, in Server documents, or Connection documents. If an IPv6-capable computer running Windows XP enables IPv6 and it is DHCP, it will automatically have its QUAD A record stored in DNS and it is stored without a zone, because the zone is a local construct. Therefore, the ONLY way to use such a DNS entry is to have a default zone in NOTES.INI.
Example 7A -- Microsoft Windows / Linux 2.4 client wants to make outbound connection via IPv6
Connect to an IPv6 address, or to a DNS or hosts file resident name that resolves to an IPv6 address. If the address is a link local address, it need not include the zone, such as fe80::209:6bff:fecd:5b93 because the zone is defaulted by the NOTES.INI variable.
Example 7B -- Microsoft Windows / Linux 2.4 client wants to make outbound connection via IPv6
TCP_EnableIPV6=1
PORTS=TCPIP
TCPIP_TCPIPADDRESS=0,[fe80::209:6bff:fecd:5b93%4]:1352
Connect to an IPv6 address, or to a DNS or hosts file resident name that resolves to an IPv6 address. If the address is a link local address, it need not include the zone, such as fe80::209:6bff:fecd:5b93 because it is defaulted by the bound address's zone.
Enabling Internet protocols on both TCP/IP and TCP/IPV6 ports
Add the following settings to the file, NOTES.INI: