2.4.3. DMZ Proxy Solution

Unless the Satellite server is in disconnected mode, it needs to initiate outbound connections on ports 80 and 443 to the Red Hat Network Hosted service (rhn.redhat.com, xmlrpc.rhn.redhat.com, and satellite.rhn.redhat.com). To ensure correct functioning of the satellite system, do not restrict access to these hosts and ports. If required, an http or https proxy can be used, by issuing the satellite-sync --http-proxy command.

The Satellite server needs to allow inbound connections on ports 80 and 443 from client systems and any Red Hat Network Proxy servers connected to the Satellite, as well as any system that needs to access the Satellite Web UI. WebUI and client requests come in via either http or https.

The Red Hat Network Monitoring functionality requires outbound connections to individual mMnitoring-enabled client systems on port 4545. Red Hat Network Satellite Monitoring makes connections to rhnmd running on client systems if Monitoring is enabled and probes are configured for registered systems.

The Red Hat Network push functionality requires both outbound and inbound connections on port 5269 to and from each registered Red Hat Network Proxy server with Red Hat Network push functionality enabled. This is used for two-way communications between the jabberd service on Satellite and Proxy, respectively. In addition, it needs to allow inbound connections on port 5222 from client systems directly registered to the Satellite. This is used for one-way (client to server) communications between the osad service on client systems and the jabberd service on the Satellite.