httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 59396] New: Could not bind to an IPv6 listening socket with link-local scope id
Date Fri, 29 Apr 2016 12:27:51 GMT

            Bug ID: 59396
           Summary: Could not bind to an IPv6 listening socket with
                    link-local scope id
           Product: Apache httpd-2
           Version: 2.4.6
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core

In order to make httpd listen to a link-local scoped IPv6 address you have to
specify either the scope_id or the interface along with the address
Binding to link-local scoped IPv6 socket with httpd is possible.
However, is not possible with the way suggested from the documents right now.
Currently, If you try to make httpd listen to an IPv6 address with link-local
scope_id, for example
*httpd.conf: * (I'm adding the scope_id in the address after the scope_id
Listen [fe80::4eeb:42ff:fedb:9dbd%3]:80
You'll get the following error:
AH00526: Syntax error on line 52 of /usr/local/apache2/conf/httpd.conf:
Scope id is not supported
In that case we're falling into this:

  if (scope_id) {
        /* XXX scope id support is useful with link-local IPv6 addresses */
        return "Scope id is not supported";

Which means that apr is fine and filling correctly scope_id but httpd itself
drops the scope_id and giving this error.
As noted in the Apache httpd documentation, in order to make httpd listen to an
IPv6 address you have to place the address in brackets hence speaking for the
above configuration, per documentation is correct. Note that, no matter the
scope_id value you'll enter there, you'll always get the same error.
Now if you have the same configuration but without the brackets you'll be able
to correctly make httpd listen to link-local IPv6 address.
For example:
Listen fe80::4eeb:42ff:fedb:9dbd%3:80
However this is not suggested(as per RFC) as it will create a confusion between
interfaces with zone-ids. For example we could have an interface along with
zone-id "3:80"

Found in 2.4.6, it is still the same in trunk

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message