Nginx 1.4 problem
miguelmclara at gmail.com
Mon May 6 16:32:31 UTC 2013
If this is a linux box you could simple use [::]:80 and it should, by
default, responde to both v4 and v6...
"In Linux by default any IPv6 TCP socket also accepts IPv4 traffic using
the IPv4 to IPv6 mapped address format, i.e., ::ffff:<IPv4 adddress in
dotted decimal notation>. E.g., ::ffff:192.168.0.27 maps the IPv4 address
192.168.0.27 to an IPv6 address.
When you enable the address [::]:80, binding port 80 using IPv6, in the
listen directive, in Linux, by default, the IPv4 port 80 is also enabled.
Meaning that nginx listens for both IPv4 and IPv6 incoming traffic.
Therefore if you erroneously specify also a IPv4 address you'll get an
already bind address error when reloading nginx configuration." (
So I guess ipv6only=off should do the same... and it should work.... I can
be 100% sure since I don't have any box with nginx 1.4 + ipv6 yet!
On Mon, May 6, 2013 at 5:19 PM, James Cloos <cloos at jhcloos.com> wrote:
> >>>>> "LT" == Lukas Tribus <luky-37 at hotmail.com> writes:
> >> Although [::]:80 ipv6only=off; does work as advertized (including for
> >> localhost sockets), [::1]:80 ipv6only=off; fails to respond to v4
> >> connections.
> LT> Which is expected, since ::1 is an ipv6 address.
> No it is not expected.
> Everything else sees conenctions to anything in 127.0.0.0/8 when
> listen(2)ing to ::1 with bindv6only off.
> James Cloos <cloos at jhcloos.com> OpenPGP: 1024D/ED7DAEA6
> nginx mailing list
> nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx