Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Network > RHN Proxy Server > Issue <<  6 of 38 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 2738
Last update: 08-13-04
Issue:
What ports need to be open for RHN Proxy if I wish to protect it with a firewall?
Resolution:
The up2date clients behind a firewall are configured to communicate via either http or https, so you would need to open internally port 80 and 443 for the up2date clients to connect to the RHN Proxy server. The RHN Proxy will then make outgoing connections to xmlrpc.rhn.redhat.com - so you would need to allow outgoing port 80 and 443 access from the RHN Proxy server to xmlrpc.rhn.redhat.com.

Depending on how locked down and if this is being done with iptables/ipchains locally on the server, the following would also apply:
Apache redirects/queries requests to the local squid proxy running on port 8080 via localhost (127.0.0.1) and also communicates with the rhn_auth_cache daemon listening on port 9999 via localhost. So you would need to ensure that these localhost connections are also allowed.


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Network > RHN Proxy Server > Issue <<   6  of  38  >>