Document URL: 

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/installing_satellite_server_in_a_connected_network_environment/preparing-environment-for-installation-in-ipv6-network_satellite#doc-wrapper

( Same for 6.13 and below )


Section Number and Name: 

Chapter 2. Preparing your Environment for Satellite Installation in an IPv6 Network


Describe the issue: 

2.1. Limitations of Satellite Installation in an IPv6 Network

You can install Satellite and Capsules in IPv6-only systems, dual-stack installation is not supported.

2.2. Requirements for Satellite Installation in an IPv6 Network

You must deploy an external IPv4 HTTP proxy server. This is required because Red Hat Content Delivery Network distributes content only over IPv4 networks, therefore you must use this proxy to pull content into the Satellite on your IPv6 network.

You must configure Satellite to use this IPv4 HTTP proxy server as the default proxy. For more information, see Adding a Default HTTP Proxy to Satellite.


So, We are recommending 

IPv6-only Sat -> IPv4-only Proxy -> IPv4 cdn

This is not possible unless there is some sort of special 6 to 4 address conversion ( NAT64 + DNS64 ) happening between Satellite and Proxy.



Suggestions for improvement: 

One way would be to have the Proxy server deployed on Dual-Stack and working with both IPv4 and IPv6 but I don't know how QE has tested this or if this is easy to configure or not.

If that is possible then , The proxy should accept the connection from Satellite using IPv6 connection and initiate the communication to CDN with IPv4 connection.


Additional information: 

Please reach out to Foreman\Katello team and get some clarifications about these two statements we mention. It seems we are missing something there to inform to our end-users.