Nginx support IPv6 but ebuild dont have USE-flag for it. Reproducible: Always Steps to Reproduce:
Created attachment 195083 [details, diff] patch to add ipv6 use flag
*** Bug 260681 has been marked as a duplicate of this bug. ***
in reply to bug 260681#c2 Yes, it is, nginx still have some problems with epoll reloading with ipv6 enabled and can only listen on it, without proxying. But it is very usefull even with such limitations. Using both IPv4 and IPv6, without using IPv6-mapped-IPv4-addresses untested. Probably warning about experimental nature required. Maybe reload feature must be masked untill epoll fixed, if ipv6 enabled. About bug: it was 3 month older that this, and "patch" was described in words, but it doesn't matter.
About inet_pton: assuming "current version" as 0.8.4: I've found, that my previous decision was wrong. It couldn't be a inet_pton bug, as it not binds anything. Futhermore, from 0.7.42 there is 'listen' option 'ipv6only=on', which will add corresponding sockopt, but it work only for 'default' socket ('listen' flag 'default') and there is no such option for IPv4 (so IPv4 will ). So it is possible to use both IPv4 (not mapped) and IPv6 on same port (for reasons of IPv4/IPv6-only sites or nice logs): You should specify some 'default' server for every binded socket and bind all IPv6 sockets, which should be used with IPv4 ones, as 'ipv6only'. Any futher uses of such sockets will reuse already existing, without bind, Example: server { #server1 listen [::]:80 default ipv6only=on; listen 80; ... } server { #server2 listen [::]:80; listen 443 default ssl; } server { #server3 listen [::]:443 default ipv6only=on; } It will result in: server1 will listen on 0.0.0.0:80 AND on [::]:80 - different binds. All connections comming from IPv4 will be listed in logs with normal ipv4 addresses server2 will listen on [::]:80 - reusing socket from server1, and on IPv4-only socket 0.0.0.0:443 defaulting it as ssl port. server3 will listen only on IPv6-only socket [::]:443, which is not default ssl. ----- Also note, that when using [::]:<port> without ipv6-only it should be only default IPv6 addr for this port (as otherwise other socket may be binded before this and wildcard will be blocked) and you should not use IPv4 addresses on this port, as nginx don't understand that wildcard IPv6 addresses also mapped IPv4. -------------- So, only reload problem exists.
As commented on the other bug, no answer from maintainer - i'll fix this in my free time this week.
Fixed in 0.8.4-r1.
