Summary: How to install a squid proxy server.
Date: Around 2014
Refactor: 22 March 2025: Checked links and formatting.
This is the article on installing and configuring squid on SLES11. The SLES 11 server is installed like this. Squid is in the support channel for SLES 11, so you'll also need to add the update repository to the server. See SLES Installation Update Server 11 on how to do that. The end situation will be two networks (private and public), with squid in the middle and protected by the firewall for the public network.
Yast → 'Security and Users' → 'Firewall'.
Config:
Default Allowed services for internal zone are fine.
Go to yast → 'Software' → 'Software Management'. Search for squid, and select the appropriate version in the list with search results. That is currently 2.7.STABLE5-2.4.1. Click 'Accept'.
Can be done with yast → 'Network Services' → Squid.
There is an extra configuration option which is a nice to have for troubleshooting and log handling etc. Configure the visible_hostname for this:
# TAG: visible_hostname # If you want to present a special hostname in error messages, etc, # define this. Otherwise, the return value of gethostname() # will be used. If you have multiple caches in a cluster and # get errors about IP-forwarding you must set them to have individual # names with this setting. # #Default: # none visib le_hostname proxy.getshifting.com
To make proxy.pac work create a file in the documentroot of apache. So we need apache:
Go to yast → 'Software' → 'Software Management'. Search for apache, and select the appropriate version in the list with search results. That is currently 2.2.10-2.24.5. Click 'Accept', as well as for the dependencies.
For further configuration check here.
Yast → system → runlevel
Change the runlevel for Apache to automatic.