How To Setup IPv6 | → 6.13.3 | Created: 6.0.6; Updated: 6.0.6 |
Table of Contents |
IPv6 (Internet Protocol Version 6) is the successor, respectively the replacement, of the current version Internet Protocol, IPv4. The main problem using IPv4 is the growing shortage of IPv4 Addresses caused by the growing number of machines added to the internet.
IPv6 fixes a number of problems in IPv4, such as the limited number of available IPv4 addresses. It also adds many improvements to IPv4 in areas such as routing and network autoconfiguration. IPv6 is expected to gradually replace IPv4, with the two coexisting for a number of years during a transition period.
For this reason ePages supports IPv6 in version 6.0.6 and higher.
ip -6 addr show
If command returns nothing or an error occurs, ask your system administrator to add the IPv6 network interface (ip -6 addr add ...).
PATH=$PATH:/usr/sbin:/sbin iptables -L
If not, ask your system administrator to change the firewall settings.
Control Panel -> Network Connections -> Local Area Connection -> Properties -> Install... -> Protocol (Add) -> Microsoft TCP/IP version 6
Control Panel -> Windows Firewall
Administrative Tools -> IIS Manager -> Default Web Site -> IP Address (All Unassigned)
Activate IPv6 either in the setup process or after the setup process. Windows only supports IPv6 activation after setup, skip to the respective section.
This section shows how to IPv6 during the setup. This works only for Linux, not for Windows. See section 'IPv6 Activation after Setup' if you want to enable IPv6 in ePages on Windows.
Enable IPv6 by customizing your install.cnf file prior the installation process. You can skip the section "Post Installation" then.
Set EPAGES_ENABLE_IPv6=1. The environment variable EPAGES_IPLIST must contain the IPv6 address or the hostname (whether you use IPv6 addresses or hostnames in Webinterface.conf) if EPAGES_IPBINDING is set.
Set EPAGES_ENABLE_IPv6=1. The environment variable LOCAL_IPS must contain the IPv6 address or the hostname (whether you use IPv6 addresses or hostnames in Webinterface.conf) if IP_BINDING is set.
If a host name is resolved to both IPv4 and IPv6, then the IPv6 address is used if EPAGES_ENABLE_IPv6=1, otherwise the IPv4 address.
In Windows, "localhost" is resolved to both 127.0.0.1 and ::1. In Linux, "localhost" is resolved to 127.0.0.1 and "ipv6-localhost" is resolved to ::1.
If IP binding isn't used, a server can be connected with IPv6 and IPv4 clients if the server is set to IPv6 and has an IPv4 address too.
All IPv4 addresses can be replaced by IPv6 addresses or relevant host names. The hostname must be short (without ".") or the result of the command `hostname --fqdn`.
In section "URLRewrite", line ExceptionHost, an IPv6 address has to be added in squared brackets, e.g.:
[URLRewrite] ExceptionHost=shop.domain.ex [2001:4bd8:2:2:213:d3ff:fe62:f1f0]
When using IP-Masks the part of the IP following the wildcard ("*") will be truncated and is considered as the beginning of the IP to be tested. IPv6 masks must be written in short form, i.e.:
If you use host names in WebInterface.conf, the corresponding IP entry or IP mask must also exit.
Host masks as follows are not allowed: [*.epages.de]
IPv6 addresses can be entered in addition to IPv4 addresses and domain names.
The Sybase interfaces file (Linux: $SYBASE/interfaces; Windows: %SYBASE%\ini\sql.ini) may contain IPv4 addresses, IPv6 addresses or host names.
For Windows, Sybase recommends to use IPv6 addresses instead of host names, see http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.dc38421_1500/html/ntconfig/X36043.htm. Hostnames will be resolved to IPv4 addresses on Windows, i.e. IPv4 is used if host names are entered in "sql.ini".
If you want to support IPv4 and IPv6, you will need to have entries for both protocols, e.g.:
DBServer master tcp ether revival.sybase.com 17100 query tcp ether revival.sybase.com 17100 master tcp ether revival.v6.sybase.com 17100 query tcp ether revival.v6.sybase.com 17100
The "*.res" files in $Sybase/ASE-15_0 can contain IPv6 addresses.
Windows hosts must be rebooted to take effect of the changes.
After starting ePages, check if the services run with IPv6:
Windows:
netstat -a -n | perl -ne "s/ +/ /g; /TCP.*LISTENING/ && print"
Linux:
netstat -tulpn
If the web server runs with IPv6, you can use the IPv6 address in square brackets in the URL, e.g.:
http://[2001:4bd8:2:2:2e0:7dff:fe76:8613]:80/WebRoot/WebAdapterError.html