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


View All Comments

  • Lio - Saturday, May 15, 2010 - link

    Would be interesting to have some focus on cost of running this setup. Linux may be free but running a machine 24 hours a day to provide a proxy service is not. Older hardware such as that based on Intel's Pentium 4 chips are famous for high power consumption, I wonder what the additional charge on the power bill would be after one year. Is there anything that can be done to reduce the operating cost of such a set up via software which supports some kind of sleep mode? Reply
  • pkoi - Sunday, May 16, 2010 - link

    One way to curb power consumption is to do meaningful computation on idle time 24/7.
    BOINC ect. And run linux in a VM.
  • RoboJ1M - Sunday, May 16, 2010 - link


    A bit late in the day but I'd like to point everybody's attention to "eBox", a web based configurator for linux based server.

    It combines the ease of use of the "home router" with the tremendous power of the linux server and I absolutely love it.

    We use two of them at work for proxy, firewall and vpn duties and I use one at home for all of the above and domain, print and file services.

    For reference it's based on ubuntu server (8.04 LTS at the mo but 10.04 coming soon)

    Anyway, I absolutely love it. :)

  • zabby113 - Monday, May 17, 2010 - link

    Does the proxy take over as your router? Since it leases your IP from the Modem, is this not where port forwarded and such should take place? If so, how does one perform such tasks? If not, can anyone explain to me what is happening? Reply
  • Fineghal - Monday, May 17, 2010 - link

    This seems like the perfect task for a "plug" computer ala GuruPlug. 2Gb Ethernet, 1 eSata, 2 usb and b/g wireless. 130 USD or so - if you want to do this, the power savings of 5 watts vs 100 watts comes close to paying for itself in a year. Obligatory link: Reply
  • jtleon - Tuesday, July 20, 2010 - link

    I realize Anandtech probably will not touch this subject - but lets face it - Ads eat up bandwidth. More than we may EVER want to admit.

    Using a proxy that has filtering built-in, like CCProxy, can GREATLY eliminate all those hungry Ads, and save that precious bandwidth for what you REALLY need it for - Useful data, of course!

    We use CCProxy both at work, and at home, and build our webfilter using the updated host file from:

    This way not only do we eliminate redundant downloads, but we stop the Ads - before they hit the router! Talk about truly efficient bandwidth!!!

  • bridal gonws - Tuesday, July 26, 2011 - link

    Hello I am so delighted I found your site, I really found you by mistake, while I was watching on yahoo for something else, Anyways I am here now and would just like to say thank for a tremendous post and a all round entertaining blog. Please do keep up the great work.

Log in

Don't have an account? Sign up now