|
| 1 | +[id="ipv6-and-ipv4-requirements"] |
| 2 | += IPv6 and IPv4 requirements |
| 3 | + |
| 4 | +You can install {Project} in an IPv4 network or in an IPv6 network. |
| 5 | +ifdef::satellite[] |
| 6 | +Dual-stack {Project} installations that use both IPv4 and IPv6 are not supported. |
| 7 | +endif::[] |
| 8 | + |
| 9 | +The following requirements apply to installations in an IPv4 network: |
| 10 | + |
| 11 | +* Ensure an IPv6 loopback is configured on the base system. |
| 12 | +The loopback is typically configured by default. |
| 13 | +Do not disable it. |
| 14 | +* Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter. |
| 15 | + |
| 16 | +The following requirements apply to installations in an IPv6 network: |
| 17 | + |
| 18 | +ifdef::satellite[] |
| 19 | +* Deploy an external HTTP proxy server that supports both IPv4 and IPv6. |
| 20 | +This is required because Red Hat Content Delivery Network distributes content only over IPv4 networks, therefore you must use this HTTP proxy to pull content into the {Project} on your IPv6 network. |
| 21 | +You must configure {Project} to use this dual-stack (supporting both IPv4 and IPv6) HTTP proxy as the default HTTP proxy. |
| 22 | +endif::[] |
| 23 | +ifndef::foreman-deb,foreman-el,satellite[] |
| 24 | +* If you rely on content from IPv4-only networks, use an external dual-stack HTTP proxy. |
| 25 | +Configure {Project} to use this dual-stack (supporting both IPv4 and IPv6) HTTP proxy as the default HTTP proxy. |
| 26 | +endif::[] |
| 27 | +* {Project} does not support configuring an HTTP proxy using a direct IPv6 address. |
| 28 | +Instead, configure the HTTP proxy with a FQDN that resolves to the IPv6 address. |
| 29 | + |
| 30 | +If you intend to provision hosts in an IPv6 network, the following requirements also apply: |
| 31 | + |
| 32 | +* Deploy an external DHCPv6 server and configure it manually to communicate with the network boot process and to manage IP address assignment because {Project} cannot integrate with a DHCPv6 server and manage its configuration. |
| 33 | +For more information about DHCPv6 server configuration, see {ProvisioningDocURL}options-in-unmanaged-dhcpv6[Options in unmanaged DHCPv6] in _{ProvisioningDocTitle}_. |
| 34 | +* Configure {Project} for UEFI HTTP boot provisioning. |
| 35 | +Although {Project} provisioning templates include IPv6 support for PXE and HTTP (iPXE) provisioning, the UEFI HTTP Boot provisioning is the only tested and certified provisioning workflow. |
| 36 | +For more information, see xref:common/modules/proc_configuring-for-uefi-http-boot-ipv6-provisioning.adoc#configuring-for-uefi-http-boot-provisioning-in-an-ipv6-network_{context}[]. |
| 37 | + |
| 38 | +.Additional resources |
| 39 | +ifdef::satellite[] |
| 40 | +* link:https://access.redhat.com/solutions/5045841[_How do I disable the IPv6 protocol on Red Hat Satellite and/or Red Hat Capsule server?_ in Red Hat Knowledgebase] |
| 41 | +endif::[] |
| 42 | +* xref:common/modules/proc_adding-a-default-http-proxy.adoc#adding-a-default-http-proxy_{context}[] |
0 commit comments