Proxy Server How To

Start by installing Arch Linux (or your chosen distribution) onto the hardware you selected. If you are in need of a little assistance with the installation, I recommend using this wiki guide and then set up yaourt. Once you have completed your standard Linux installation you need to ensure your network is configured properly. In the case of my transparent proxy, I plugged one network port directly into my cable router and allowed it to grab and IP address via DHCP. The second adapter is then given an IP address of your choice (I chose; other common IP addresses would be 192.168.x.x).

At this point you will want to test your network configuration. Start with trying to get out to the internet. If this works, plug your secondary network adapter into whatever switch/router you have available. Take your desktop or laptop that's plugged into the same switch and assign it an IP address in your 10.4.20.x range. (For DHCP setups, see below.) You should now be able to ping your new proxy server ( from your desktop/laptop. As a quick note for the users who only have a wireless cable modem, it is okay to have both interfaces of your proxy server and desktop plugged into the same cable modem hub.

Now that we have the configuration of the network cards complete, we just need to do a quick installation and configuration of Shorewall/Squid. That may sound like a daunting task to the Linux initiate, but this is actually very simple. First go ahead and install both Squid and Shorewall. Arch has both readily available in the package repository (from a command prompt: yaourt –S shorewall squid). If you are not utilizing Arch, you can download the packages manually from and

Whether you installed Arch Linux or another distribution as your base OS, Shorewall has one simple command to get it set up: cp /usr/share/shorewall/Samples/two-interfaces/* /etc/shorewall. (This copies the base two-NIC example to your live Shorewall directory, which saves a lot of manual work.) Make a quick edit to /etc/shorewall/shorewall.conf and change the Startup_Enabled to yes and you now have a functioning Shorewall. The only thing you need to do for Shorewall at this point is add the following rule into the /etc/shorewall/rules file: REDIRECT loc 3128 tcp www. Start Shorewall by typing: shorewall start from the command line, and add it to your boot process by putting shorewall into the DAEMONS section of /etc/rc.conf.

Now that Shorewall is fully functional and configured, we need to configure Squid. I found a short wiki guide that will assist with the initial set up of Squid. Once you have completed the configuration in the wiki guide, you need to pay close attention to a few configuration settings located in /etc/squid/squid.conf. The cache_memline should be set to half of your installed ram on your proxy server. In my case I have 512MB of total memory so I configured cache_mem to 256. The other setting that you need to pay attention to is maximum_object_size. This setting is the maximum file size your proxy will retain. I set my maximum size to 2048MB in order to retain everything up to a CD ISO. Be cautious of using 2048 if you have anything less than a 120gb drive as your storage space could be gone in the matter of a few days. To get the caching proxy in place and running, the most important line to add is http_port 3128 transparent. The key here is the addition of "transparent", which turns squid into a caching proxy that won't require any additional configuration on your client PCs.

If you followed all of the directions correctly, you're now ready to configure all the machines on your network with a 10.4.20.x IP address with the gateway set as Don't forget to configure your DNS as well (in /etc/resolve.conf). Now that you have everything fired up give your new proxy a spin around the internet. If you would like to do a good test, download a decent size file (i.e. larger than 1MB). Once the download is complete, you should be able to download it again a second time and get LAN speeds on the download. If you have multiple computers, use another machine on your network and attempt to download the same file and you should again see LAN download speeds.

Proxy Server with DHCP

Although I wanted to keep this short and to the point, a common question inevitably comes up: what if you still want to use DHCP? There are a few ways to tackle this issue. If you're lucky enough to have a router/cable modem that will allow you to change what IP addresses it assigns to the network, simply change it over to your new 10.4.20.x subnet and have it assign the gateway of If this is not the case, you will need to disable DHCP on your router and install the DHCP server package (in Arch: pacman –S dhcp). The configuration can be a bit of a hassle, so here's my /etc/dhcpd.conf.

Start the DHCP service on your proxy (/etc/rc.d/dhcpd start) and test DHCP on your desktop/laptop. Assuming all goes well, add dhcpd to your DAEMONS in /etc/rc.conf. If you happen to reboot your Linux box, after a minute or so your proxy should be back up and running.

Introduction to Proxy Servers Linux Neophyte Troubleshooting
Comments Locked


View All Comments

  • mindless1 - Tuesday, May 11, 2010 - link

    Given a motherboard with the features needed, you can underclock most system configurations to reach a power level similar enough to an Atom or Notebook... especially if the Atom system is using the relatively power hungry (for its feature set) 945 chipset.

    For example, take what many call a power hungry setup like an Athlon XP @ 60W peak load. Undervolt and underclock to 1/4th it's original speed and you still get enough performance for most people's needs, but only 15W at peak power. Now consider that it is hardly ever running at peak power, that the power savings is a single-digit # of watts at most. Only catch is, some motherboards limit how low you can undervolt, the above example only assumed power savings from running at 1/4th clock frequency but if you can undervolt too, the power savings go up even more.
  • MySchizoBuddy - Tuesday, May 11, 2010 - link

    can i use sheevaplug as my cache proxy
  • MySchizoBuddy - Tuesday, May 11, 2010 - link

    OK it can
    From SheevaPlug FAQ
    Sheevaplug can be used for
    "Web proxy, enabling fast, cached access to your favorite web sites"
  • ibloomfield - Tuesday, May 11, 2010 - link

    i use squid for the sole reason of working my way around filters at school.

    if you set up ssh to work off port 443 (in case outgoing 22 is blocked) and then tunnel squids port through the connection (port 3128) then you can set the browser to proxy port 3128 and your are set to go.

    easy workaround
  • Pinski - Tuesday, May 11, 2010 - link

    Or you can just use ssh -D localhost:### host, and you'll setup a SOCKS proxy via SSH and use that to browse the web without ever having to deal with configuring/running Squid.
  • Pinski - Tuesday, May 11, 2010 - link

    Woops, forgot ### would be a port number of your choosing.
  • mfenn - Tuesday, May 11, 2010 - link

    Should say /etc/resolv.conf instead of /etc/resolve.conf
  • JarredWalton - Tuesday, May 11, 2010 - link

    Fixed... I blame *nix and their fetish for dropping letters. LOL.
  • bob4432 - Tuesday, May 11, 2010 - link

    " I set my maximum size to 2048MB in order to retain everything up to a CD ISO"

    am i reading this wrong? what cd iso is 2GB in size? why not set it too 700MB or 4.7GB? or even 8.5GB for a d/l dvd?
  • RamarC - Tuesday, May 11, 2010 - link

    you post a great little article! keep it up since there doesn't seem to be anything new/big/amazing on the hardware front. ;)

Log in

Don't have an account? Sign up now