4.4. Installing Satellite behind an HTTP Proxy

Due to the way that RHN Satellite uses the rhn.conf to 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:
  1. Complete a minimal installation of Red Hat Enterprise Linux 4 or 5 (depending on the version of RHN Satellite that you will install).
  2. Configure the system so that it can connect to RHN behind the HTTP proxy. Edit the file /etc/sysconfig/rhn/up2date as follows:
  3. Register the system to RHN.
  4. Begin the installation of RHN Satellite with the disconnected option:
    ./install.pl --disconnected
  5. Once the installation is complete, you will need to add or modify your settings in the /etc/rhn/rhn.conf file:
    server.satellite.http_proxy = <http-proxy-fqdn>
    server.satellite.http_proxy_username = <proxy-username>
    server.satellite.http_proxy_password = <proxy-password>
    You will also need to update the /etc/rhn/rhn.conf file to include the parent parameter satellite.rhn.redhat.com:
    server.satellite.rhn_parent = satellite.rhn.redhat.com


    Alternatively, if you are using the RHN Satellite web interface, log in as a user with Administrator privileges. Browse to AdminRHN Satellite ConfigurationGeneral. From here, enter the HTTP Proxy settings, and toggle the Disconnected RHN Satellite option.
  6. Restart the Satellite service:
    service rhn-satellite restart
  7. Reactivate the Satellite as a connected Satellite:
    rhn-satellite-activate --rhn-cert=<path-to-cert>
You should now have a connected RHN Satellite that will work behind an HTTP proxy.