I’ve been using OpenWrt on my for a while now. It’s lovely and with all the additional software you can install on it it’s even better.

Source: packages / net / tinyproxy / Makefile @ 12822. 2006 OpenWrt.org: 3 # 4. Define Package/tinyproxy/install: 46. Note also that by default tinyproxy does not allow connections from other hosts so you will need to enable this. One way is to comment out the 'Allow' line from the config. Install TinyProxy on each Access Point running OpenWrt to act as a transparent proxy. Implement a dynamic firewall on each Access Point running OpenWrt by using the 'Dynamic firewall with ChilliSpot and IP Tables' recipe in this cookbook.

I’ve got for example installed on it. Privoxy is a (non-caching) proxy with filtering capabilities. So it basically means that Privoxy can filter out malware, ads & other junk from the webpages you visit. Esper Retirement Edition Flac.

What I’m going to show you is: • how to install Privoxy on OpenWrt • how to configure the firewall on your router to make the proxy transparent • how to feed Privoxy with AdBlock rules and automatically keep them up to date All the bash commands below are ment the be executed on the router. Preferably via a ssh connection ( ssh router). Install Privoxy Let’s first install Privoxy on the router. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 confdir / etc/ privoxy logdir / var/ log filterfile default. Filter logfile privoxy actionsfile match- all. Action # Actions that are applied to all sites and maybe overruled later on. Actionsfile default.

Action # Main actions file filterfile user. Filter listen- address 192.

1: 8118 toggle 1 enable- remote- toggle 1 enable- remote- http- toggle 0 enable- edit- actions 1 enforce- blocks 0 buffer- limit 4096 forwarded- connect- retries 0 accept- intercepted- requests 1 allow- cgi- request- crunching 0 split- large- forms 0 keep- alive- timeout 300 socket- timeout 300 permit- access 192. 0/ 24 debug 8192 # Errors - * we highly recommended enabling this* Make sure to replace the 192.168.5.x addresses with ones that match your network setup. If everything is ok, start up Privoxy with /etc/init.d/privoxy start. Check if it’s running by doing ps grep -i privoxy And to make sure everything is running fine: tail -n20 /var/log/privoxy.log Configure the firewall Next up we’re going to adjust the firewall on the router so Privoxy becomes our transparent proxy. Add this rule to /etc/config/firewall. 1 2 3 4 5 6 7 8 9 10 config redirect option proto 'tcp' option target 'DNAT' option dest 'lan' option _ name 'transparent-proxy for HTTP' option src 'lan' option dest_port '8118' option src_dport '80' option dest_ip '192.168.5.1' option src_dip '!192.168.5.1' Again, make sure you adjust the ip addresses properly. Next up, restart the firewall: /etc/init.d/firewall restart.

You could also do this via the OpenWrt webinterface (LuCI): Automate fetching and updating of Adblock filters We’re going to use a script made by that automatically downloads and converts adblock filters to privoxy filters (their format is different). First install the dependencies for this script. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20. Actionsfile match- all. Action # Actions that are applied to all sites and maybe overruled later on. Actionsfile default. Action # Main actions file filterfile malwaredomains_full.

Filter filterfile fanboy- social. Filter filterfile easyprivacy. Filter filterfile easylist. Filter filterfile easylistdutch.

Filter filterfile user. Filter actionsfile malwaredomains_full. Action actionsfile fanboy- social. Action actionsfile easyprivacy.

Action actionsfile easylist. Action actionsfile easylistdutch. Action actionsfile user. Action listen- address 192. Restart Privoxy again and check /var/log/privoxy.log to make sure everything is still allright.

You could also check in your browser to see if Privoxy is running ok. To keep your filters up to date add this to your crontab ( crontab -e).