Project

General

Profile

Feature #7839

Support IPv6

Added by Stephen Bowman over 4 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Core
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

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

foreman-proxy-1.7.3-bind-ipv6.diff foreman-proxy-1.7.3-bind-ipv6.diff 501 Bytes Minimalistic patch to make the Foreman Smart Proxy listen on IPv6 Simon Leinen, 03/06/2015 06:26 PM

History

#1 Updated by Dominic Cleal over 4 years ago

  • Category set to Core

#2 Updated by Joshua Hoblitt over 4 years ago

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

#3 Updated by Simon Leinen about 4 years ago

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.

#4 Updated by Dmitri Dolguikh over 3 years ago

  • 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.

#5 Updated by Ewoud Kohl van Wijngaarden about 3 years ago

#6 Updated by Ewoud Kohl van Wijngaarden about 3 years ago

  • Related to deleted (Feature #13544: Support IPv6 DNS in smart-proxy)

#7 Updated by Michael Moll almost 2 years ago

  • 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