RE: Nginx 1.4 problem

2013-05-06 Thread Lukas Tribus
Even when explicitly setting the socket option IPV6_V6ONLY to 0 (man 7 ipv6) - and thus ignoring ´cat /proc/sys/net/ipv6/bindv6only´ this doesn't work. > While looking into this, I found that, when given ::1, nc(1) > explicitly listens to both ::1 and :::127.0.0.1. The behavior here is exac

Re: Nginx 1.4 problem

2013-05-06 Thread James Cloos
> "LT" == Lukas Tribus writes: LT> Hi Jim, >> Everything else sees conenctions to anything in 127.0.0.0/8 LT> Not sure what you mean by everything else, but I don't think LT> thats the case. Some time ago a message on debian-devel noted that deb was going to start defaulting to bindv6only=1

RE: Nginx 1.4 problem

2013-05-06 Thread Lukas Tribus
Hi Jim, > Everything else sees conenctions to anything in 127.0.0.0/8 Not sure what you mean by everything else, but I don't think thats the case. See this example: > lukas@ubuntuvm:~$ grep Listen /etc/ssh/sshd_config > ListenAddress ::1 > ListenAddress 10.0.0.55 > lukas@ubuntuvm:~$ sudo netst

Re: Nginx 1.4 problem

2013-05-06 Thread Miguel Clara
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., :::. E.g., :::192.168.0.27 maps the IPv4 address 192.168.0.27

Re: Nginx 1.4 problem

2013-05-06 Thread James Cloos
> "LT" == Lukas Tribus 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 cone

RE: Nginx 1.4 problem

2013-05-03 Thread Lukas Tribus
> Although [::]:80 ipv6only=off; does work as advertized (including for > localhost sockets), [::1]:80 ipv6only=off; fails to respond to v4 > connections. Which is expected, since ::1 is an ipv6 address. Lukas ___ n

Re: Nginx 1.4 problem

2013-05-02 Thread James Cloos
> "AN" == Alder Network writes: AN> I tried AN> listen [::]:80 ipv6only=off; Although [::]:80 ipv6only=off; does work as advertized (including for localhost sockets), [::1]:80 ipv6only=off; fails to respond to v4 connections. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 ___

Re: Nginx 1.4 problem

2013-05-01 Thread Maxim Dounin
Hello! On Wed, May 01, 2013 at 02:18:44PM -0700, Paul N. Pace wrote: > On Wed, May 1, 2013 at 2:07 PM, Maxim Dounin wrote: > > Hello! > > > > On Wed, May 01, 2013 at 11:17:10AM -0700, Alder Network wrote: > > > >> Just for clarity, I want to be listening on both IPv4 and IPv6 on the same > >> po

Re: Nginx 1.4 problem

2013-05-01 Thread Alder Network
I tried listen [::]:80 ipv6only=off; and the TCP connection went through, but got an http 400 bad response. It would be nice to have a corresponding config upgrade manual as well. Thanks, On Wed, May 1, 2013 at 2:18 PM, Paul N. Pace wrote: > On Wed, May 1, 2013 at 2:07 PM, Maxim Dounin wr

Re: Nginx 1.4 problem

2013-05-01 Thread Paul N. Pace
On Wed, May 1, 2013 at 2:07 PM, Maxim Dounin wrote: > Hello! > > On Wed, May 01, 2013 at 11:17:10AM -0700, Alder Network wrote: > >> Just for clarity, I want to be listening on both IPv4 and IPv6 on the same >> port. > > You have to write > > listen 80; > listen [::]:80; > > to listen on b

Re: Nginx 1.4 problem

2013-05-01 Thread Maxim Dounin
Hello! On Wed, May 01, 2013 at 11:17:10AM -0700, Alder Network wrote: > Just for clarity, I want to be listening on both IPv4 and IPv6 on the same > port. You have to write listen 80; listen [::]:80; to listen on both IPv4 and IPv6. > > > On Wed, May 1, 2013 at 11:00 AM, Alder Netwo

Re: Nginx 1.4 problem

2013-05-01 Thread Alder Network
Just for clarity, I want to be listening on both IPv4 and IPv6 on the same port. On Wed, May 1, 2013 at 11:00 AM, Alder Network wrote: > netstat -pln shows the server is waiting on that port. > > Yes, I have been using in server section > listen [::]:80; > What is supposed to be for IPV4 now

Re: Nginx 1.4 problem

2013-05-01 Thread Alder Network
netstat -pln shows the server is waiting on that port. Yes, I have been using in server section listen [::]:80; What is supposed to be for IPV4 now? I'll go over the changelist later, Thanks, - Alder On Wed, May 1, 2013 at 10:40 AM, Maxim Dounin wrote: > Hello! > > On Wed, May 01, 2013 a

Re: Nginx 1.4 problem

2013-05-01 Thread Maxim Dounin
Hello! On Wed, May 01, 2013 at 10:13:34AM -0700, Alder Network wrote: > Tried to upgrade to just-released Nginx1.4. TCP 3-way hand-shake > aborted by server's ACK+RST packet, but netstat shows server > is listening on that port. Any config has been changed since Nginx 1.2 > to 1.4 in this regar

Nginx 1.4 problem

2013-05-01 Thread Alder Network
Tried to upgrade to just-released Nginx1.4. TCP 3-way hand-shake aborted by server's ACK+RST packet, but netstat shows server is listening on that port. Any config has been changed since Nginx 1.2 to 1.4 in this regard? Thanks, - Alder ___ nginx mail