Red Hat NETWORK PROXY 5.3.0 -, Installation Manual

Page: 11 / 48

Additional Requirements
7
2.4. Additional Requirements
The following additional requirements must be met before the RHN Proxy Server installation can be
considered complete:
Full Access
Client systems need full network access to the RHN Proxy Server services and ports.
Firewall Rules
RHN strongly recommends firewalling the RHN Proxy Server solution from the Internet. However,
various TCP ports must be opened on the Proxy, depending on your implementation of RHN
Proxy Server:
Port Direction Reason
80 Outbound Proxy uses this port to reach
rhn.redhat.com
,
xmlrpc.rhn.redhat.com
,
and your Satellite URL (depending on
whether RHN Proxy is talking to either
RHN Hosted or a Satellite Server).
80 Inbound Client requests come in via either http or
https
443 Inbound Client requests come in via either http or
https
443 Outbound Proxy uses this port to reach
rhn.redhat.com
,
xmlrpc.rhn.redhat.com
,
and your Satellite URL (depending on
whether RHN Proxy is talking to either
RHN Hosted or a Satellite Server).
4545 Outbound If your Proxy is connected to an RHN
Satellite Server, Monitoring makes
connections to
rhnmd
running on client
systems via this TCP port, if Monitoring
is enabled and probes configured to
registered systems.
5222 Inbound Opening this port allows
osad
client
connections to the
jabberd
daemon
on the Proxy when using RHN Push
technology.
5269 Outbound If your Proxy is connected an RHN
Satellite Server, this port must be open to
allows server-to-server connections via
jabberd
for RHN Push Technology.
Table 2.1. Ports to open on the Proxy
Synchronized System Times
There is great time sensitivity when connecting to a Web server running SSL (Secure Sockets
Layer); it is imperative the time settings on the clients and server are reasonably close together so
the that SSL certificate does not expire before or during use. It is recommended that Network Time
Protocol (NTP) be used to synchronize the clocks.