On Apr 7, 2013, at 0:44 , Jim Ohlstein wrote:
> This way there is no competition for what is listening on IPv6 addresses
> and you should not see that error. I've been doing it this way for at
> least a couple of years now, certainly before 1.0.x series came out. It
> may not be the "recommended" approach but it's what I had to do to get
> it back then. One caveat - I am using FreeBSD and IPv6 may be
> implemented differently in GNU/Linux.
On FreeBSD dual stack sockets are disabled by default:
>sysctl net.inet6.ip6.v6only
net.inet6.ip6.v6only: 1
while on Linux they are enabled:
>cat /proc/sys/net/ipv6/bindv6only
0
--
Igor Sysoev
http://nginx.com/services.html
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
> This way there is no competition for what is listening on IPv6 addresses
> and you should not see that error. I've been doing it this way for at
> least a couple of years now, certainly before 1.0.x series came out. It
> may not be the "recommended" approach but it's what I had to do to get
> it back then. One caveat - I am using FreeBSD and IPv6 may be
> implemented differently in GNU/Linux.
On FreeBSD dual stack sockets are disabled by default:
>sysctl net.inet6.ip6.v6only
net.inet6.ip6.v6only: 1
while on Linux they are enabled:
>cat /proc/sys/net/ipv6/bindv6only
0
--
Igor Sysoev
http://nginx.com/services.html
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx