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

  • Jeff7181 - Tuesday, May 11, 2010 - link

    A Pentium 4 3.06 GHz chip with HT? Are you insane? You're going to use one of the most power hungry consumer grade CPU's of all time to run a firewall & proxy? I'm all for dinking around with old hardware and turning them into a Linux box... file server... router... whatever. But a 3.06 GHz P4???

    Regardless... I like this... in fact, I'd like you see you add DNS and Samba to the build. (hey... if you can afford the power draw of a P4, what's another 20 watts for a couple high capacity hard drives?)
  • mariush - Tuesday, May 11, 2010 - link

    It would have been much easier to install FreeBSD and squid... it's just a question of adding pre-made packages that configure and install by themselves. Reply
  • GullLars - Wednesday, May 12, 2010 - link

    Thanks a lot for this guide. It will get a bookmark for later use. Reply
  • Brian B - Wednesday, May 12, 2010 - link

    I have a VM host system in the basement. It would be very easy to bring up a tiny VM with two virtual NICs and install LINUX. But does anyone know if this setup should function correctly? Since the VMs are in most every way just PC's on the network, I cant think of a good reason it *shouldnt* work but maybe I'm missing something... Reply
  • ChrisRice - Thursday, May 13, 2010 - link

    Yes it will work. Reply
  • CZroe - Thursday, May 13, 2010 - link

    I want to set up OpenVPN to allow me to route my Internet traffic through a certain PC from another Internet connection. I can think of many uses. For example, if I want to hide tethering traffic from my cellphone provider, I can open a an encrypted VPN tunnel using a VPN client on the tethered PC to connect to my home network's VPN server but, instead of just using it to access remote files and LAN services, I want to use it to route Internet traffic through it (through VPN connection over Internet to LAN and back out onto the 'net). I know this is possiblem I just don't know how. Reply
  • thebeastie - Thursday, May 13, 2010 - link

    I have always liked the idea of proxy servers, but the problem I have always seen with them is that people who set them up only set them up to proxy small content like web images etc and ignore some one watching a web cast of CNN or something.

    maximum_object_size 2048 MB
    ? Why bother.

    Web proxies were huge in the 90s but died away as general internet got fast or people just unfairly blamed or assumed the proxy is ruining their internet under any circumstance where the internet wasn't working.

    I think there is a bigger future in 'large content only' proxy servers where if something is more then 8megs, then cache it.

    I would say proxies were started when web images were the biggest thing on web pages in the 90s but that has turned full circle and is now the smallest thing on the internet.

    The other crazy part of it all is that a lot of web sites that have only large content like news videos go out of their way to make sure it cant be cached, why bother.
  • Kenazo - Thursday, May 13, 2010 - link

    Not sure if it's been mentioned in any of the comments yet, but I've used Smoothwall Express with good results for home and small business use. Linux based, easy to install and can run on any garbage Pentium III you have kicking around. Reply
  • pkoi - Sunday, May 16, 2010 - link

    +1, "easy to install and can run on any garbage Pentium III you have kicking around. " Reply
  • gwolfman - Thursday, May 13, 2010 - link

    I'd go the transparent method, except for the fact that the Netflix plugin/addon for WMC (Windows Media Center) gives me a bogus error. Without the proxy, all works as is should. Anyone else run into this? Reply

Log in

Don't have an account? Sign up now