Feature #7839
closed
Added by Stephen Bowman about 10 years ago.
Updated over 7 years ago.
Description
Using foreman-installer (1.6.0), the smart-proxy is not listening on IPv6. It's only bound to IPv4. Please support dual-stack environments, listening on both IPv6 and IPv4.
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN
Files
ipv6 support would be great. Foreman/proxy would need modification in multiple ways to support it (beyond changing the puppet module that configures ISC DHCP).
At least:
- The internal IP address validation would need to be changed to allow ipv6 IP addresses.
- DNS record support would need to be modified to allow the creation of AAAA records
- DHCP reservation would need to be modified to allow ipv6 IPs, as would parsing of dhcpd.conf
- IP auto-suggest would need to understand ipv6
- subnet IP address and subnet mask handling would need to be modified to allow ipv6
It would be great if the Foreman got comprehensive IPv6 support along the lines of what Joshua wrote. But I would be interested in even just what the original requestor asked for. In fact we have been using this in our setup: We have clusters in multiple geographically distributed sites, and we don't have IPv4 routing between these sites (because they use private addresses), only IPv6. By enabling IPv6 on the Smart Proxy, we have been able to manage OS installs across sites in this situation. A minimalistic way to do this is the attached patch (against 1.7.3). A better way would be to introduce an additional configuration parameter, e.g. "host", to allow a user to specific which address the proxy should bind to.
- Status changed from New to Feedback
Try setting 'bind_host' config parameter to '::' or an ipv6 address -- it should bind to an ipv6 socket then.
- Status changed from Feedback to Resolved
this should work now, there might be differences between specific OSes how to specifiy the listener
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by Anonymous 
Updated by