search

docker-flow / docker-flow-proxy

Docker Flow Proxy
https://docker-flow.github.io/docker-flow-proxy/
MIT License
317 stars 189 forks source link

Support IPv6 #14

Closed ruudboon closed 6 years ago

ruudboon commented 6 years ago

By default docker-flow-proxy isn't listening only to ipv4 could we have an option to listen to ipv6 also?

root@f22d1f4a9ec5:/# netstat -anp | grep :80
tcp        0      0 172.x.x.x:44546        123.123.123.123:80        TIME_WAIT   -               
tcp        0      0 172.x.x.x:34684        123.123.123.123:80        TIME_WAIT   -               
tcp        0      0 172.x.x.x:37834        123.123.123.123:80         TIME_WAIT   -
BretFisher commented 6 years ago

AFAIK Docker Overlay networks only support IPv4

vfarcic commented 6 years ago

Thanks @BretFisher.

@ruudboon I somehow lost track of this issue. As @BretFisher said, making the proxy support IPv6 would not help since Overlay is still IPv4.

ruudboon commented 6 years ago

Are you sure ipv6 isn’t supported on overlay?

Thing like this are working ‘’’ version: '2.1'

networks: app_net: enable_ipv6: true driver: overlay ipam: driver: default config:

    subnet: 172.16.238.0/24
  -
    subnet: 2001:3984:3989::/64

‘’’

BretFisher commented 6 years ago

It would be great if you could reference a PR or issue where it works... every moby/moby and libnetwork and swarmkit issue related to ipv6 overlay ends in "not supported on overlay driver" from what I see.

On Wed, Jun 6, 2018 at 4:11 PM Ruud Boon notifications@github.com wrote:

Are you sure ipv6 isn’t supported on overlay?

Thing like this are working ‘’’ version: '2.1'

networks: app_net: enable_ipv6: true driver: overlay ipam: driver: default config:

subnet: 172.16.238.0/24

subnet: 2001:3984:3989::/64 ‘’’

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/docker-flow/docker-flow-proxy/issues/14#issuecomment-395198115, or mute the thread https://github.com/notifications/unsubscribe-auth/AAwW33Xh5zUfRNNCgJKQb83mlcFcC-00ks5t6DeKgaJpZM4Tu6Dv .

tommyseus commented 6 years ago

Would it be enough to just remove the asterisk from the bind (bind *:%s)? Then you could activate the IPV6 by constant.

DEFAULT_PORTS = ::80 v4v6,::443 v4v6:ssl

Result: bind :::80 v4v6 bind :::443 v4v6 certtext