Issue

• Kickstart target unable to retrieve ks configuration file from satellite. Target is isolated from satellite by firewall, but ports opened per Satellite Installation manual (80, 443), and multiple clients already connect to satellite for management and updates from that side of firewall.
• Kickstart url and network configuration supplied as kernel arguments, target appears to set up network correctly, but still unable to get ks config from satellite using ip_range, org default, or bare metal URLs.
• The systems that successfully kickstart are on a different subnet than the ones that won't. We aren't able to determine any difference between the two subnets, as far as ports on the Satellite being accessible to both subnets.
• Clients on both subnets are able to complete all other functions, ie, updates, remote commands, reboots, etc; it's just that the clients in our DMZ are unable to locate the ks configuration.