4.4. Installing Satellite behind an HTTP Proxy
rhn.confto control its connection settings, there is no way to add options to that file prior to installation of RHN Satellite. If your network is behind an HTTP proxy in your organization, you cannot activate the RHN Satellite at installation time. A workaround to this issue is to first perform a disconnected installation of RHN Satellite, then switch the configuration to a connected method after installation is completed. The following demonstrates how to create a connected RHN Satellite installation behind an HTTP proxy:
- Complete a minimal installation of Red Hat Enterprise Linux 4 or 5 (depending on the version of RHN Satellite that you will install).
- Configure the system so that it can connect to RHN behind the HTTP proxy. Edit the file
enableProxy=1 enableProxyAuth=1 httpProxy=<http-proxy-fqdn> proxyUser=<proxy-username> proxyPassword=<proxy-password>
- Register the system to RHN.
- Begin the installation of RHN Satellite with the disconnected option:
- Once the installation is complete, you will need to add or modify your settings in the
server.satellite.http_proxy = <http-proxy-fqdn> server.satellite.http_proxy_username = <proxy-username> server.satellite.http_proxy_password = <proxy-password> disconnected=0You will also need to update the
/etc/rhn/rhn.conffile to include the parent parameter
server.satellite.rhn_parent = satellite.rhn.redhat.com
NoteAlternatively, if you are using the RHN Satellite web interface, log in as a user with
Administratorprivileges. Browse to → → . From here, enter the HTTP Proxy settings, and toggle the Disconnected RHN Satellite option.
- Restart the Satellite service:
service rhn-satellite restart
- Reactivate the Satellite as a connected Satellite: