diff options
author | Jeff Trawick <trawick@apache.org> | 2003-02-14 13:39:43 +0000 |
---|---|---|
committer | Jeff Trawick <trawick@apache.org> | 2003-02-14 13:39:43 +0000 |
commit | b69f8fa5d35fcf5376cf18ad7d7266379873cdfb (patch) | |
tree | 9b695c3b133ca3275ab283cd74ced3c15b6c1eee /docs/manual/bind.xml | |
parent | e3efb1a8cf70d0e5787a32a7fb4fa5f35b910d30 (diff) | |
download | httpd-b69f8fa5d35fcf5376cf18ad7d7266379873cdfb.tar.gz |
Replace the section on IPv6 with new text that accounts for
--[enable|disable]-v4-mapped configure option and the varying
default for it.
PR: 16739
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@98650 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/bind.xml')
-rw-r--r-- | docs/manual/bind.xml | 58 |
1 files changed, 36 insertions, 22 deletions
diff --git a/docs/manual/bind.xml b/docs/manual/bind.xml index 4f342ee06a..5eeb8ea0f1 100644 --- a/docs/manual/bind.xml +++ b/docs/manual/bind.xml @@ -77,44 +77,58 @@ <section id="ipv6"> <title>Special IPv6 Considerations</title> - <p>When APR supports IPv6, Apache will create IPv6-capable listening - sockets by default (i.e., when no IP address is specified on the - Listen directive). In other words, when APR supports IPv6,</p> + <p>A growing number of platforms implement IPv6, and APR supports + IPv6 on most of these platforms, allowing Apache to allocate IPv6 + sockets and handle requests which were sent over IPv6.</p> + + <p>One complicating factor for Apache administrators is whether or + not an IPv6 socket can handle both IPv4 connections and IPv6 + connections. Handling IPv4 connections with an IPv6 socket uses + IPv4-mapped IPv6 addresses, which are allowed by default on most + platforms but are disallowed by default on FreeBSD, NetBSD, and + OpenBSD in order to match the system-wide policy on those + platforms. But even on systems where it is disallowed by default, a + special configure parameter can change this behavior for Apache.</p> + + <p>If you want Apache to handle IPv4 and IPv6 connections with a + minimum of sockets, which requires using IPv4-mapped IPv6 addresses, + specify the <code>--enable-v4-mapped</code> configure option and use + generic Listen directives like the following:</p> <example> Listen 80 </example> - <p>is equivalent to</p> + <p>With <code>--enable-v4-mapped</code>, the Listen directives in the + default configuration file created by Apache will use this form. + <code>--enable-v4-mapped</code> is the default on all platforms but + FreeBSD, NetBSD, and OpenBSD, so this is probably how your Apache was + built.</p> - <example> - Listen [::]:80 - </example> - - <p>When APR does not support IPv6,</p> + <p>If you want Apache to handle IPv4 connections only, regardless of + what your platform and APR will support, specify an IPv4 address on all + Listen directives, as in the following examples:</p> <example> - Listen 80 + Listen 0.0.0.0:80 + Listen 192.170.2.1:80 </example> - <p>is equivalent to</p> + <p>If you want Apache to handle IPv4 and IPv6 connections on separate + sockets (i.e., to disable IPv4-mapped addresses), specify the + <code>--disable-v4-mapped</code> configure option and use specific Listen + directives like the following:</p> <example> + Listen [::]:80 Listen 0.0.0.0:80 </example> - <p>On some platforms, such as NetBSD, binding to the IPv6 wildcard address - ("::") does not allow Apache to accept connections on IPv4 interfaces. - In this situation, multiple Listen directives are required, as shown - below:</p> - - <example> - Listen 0.0.0.0:80<br /> - Listen [::]:0 - </example> + <p>With <code>--disable-v4-mapped</code>, the Listen directives in the + default configuration file created by Apache will use this form. + <code>--disable-v4-mapped</code> is the default on FreeBSD, NetBSD, and + OpenBSD.</p> - <p>Apache does not currently detect this, so the Listen statements must - be edited manually by the administrator.</p> </section> <section id="virtualhost"> |