httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colm MacCarthaigh <c...@stdlib.net>
Subject Re: cvs commit: httpd-2.0/docs/conf httpd-std.conf.in
Date Sun, 28 Sep 2003 18:43:00 GMT
On Sun, Sep 28, 2003 at 02:09:57PM -0400, Jeff Trawick wrote:
> jwoolley@apache.org wrote:
> 
> >jwoolley    2003/09/28 09:27:24
> >
> >  Modified:    .        configure.in
> >               docs/conf httpd-std.conf.in
> >  Log:
> >  "Listen 80" just works now, using v4-only, v6-only, mapped address
> >  or non-mapped address.
> 
> so --enable-v4-mapped and one "Listen <port>" gets you one listening 
> socket that handles v4 and v6 and IPV6_V6ONLY socket option is used when 
> available/as appropriate

Yep, --enable-v4-mapped will give you just one socket per port when
appropriate/available.

> and --disable-v4-mapped and one "Listen 
> <port>" gets you two listening sockets, one for v4 and one for v6, and 
> the IPV6_V6ONLY socket option is used when available/as appropriate?

Again, yep. In my opinion that makes the two situations more
consistent than different. If an administrator wants to listen
on port 80; that's what they get, in both scenarios.

If an administator wants to Listen on port 80 in IPv4 only
they should use "Listen 0.0.0.0 80", in both scenarios. If
an administator wants to Listen on port 80 in IPv6 only
they should use "Listen [::] 80", in both scenarios. 

Previously "Listen 80" did different things depending on how you
had configured. I'd say this inconsistency is more dangerous than
the relatively unimportant inconsistency of how many sockets are
being used!

> (longing for the days when I knew how to explain to non-experts how to 
> know how many listening sockets they had and/or when the accept mutex 
> was actually used)

That's what netstat is for ;) Though you're right, it is a real pain.
There's no easy way around it either, since platforms which only do
V6ONLY (windows) and that don't do it all (Linux, Tru64) have to be
supported it's always going to be messy.

In general though, anyone administrating IPv6 boxen either very quickly
becomes aware of how things like V6ONLY work, or the need to know
never arises in the first place. If a module-writer, or administrator 
needs to know what's happening they shouldn't have much difficulty. 

-- 
Colm MacCárthaigh                        Public Key: colm+pgp@stdlib.net
colm@stdlib.net					  http://www.stdlib.net/

Mime
View raw message