From 75226c157fa9687bea7f0f4b7684cd6a30477012 Mon Sep 17 00:00:00 2001
From: gferg <>
Date: Wed, 9 Jan 2002 17:29:01 +0000
Subject: [PATCH] updated

---
 LDP/howto/linuxdoc/TransparentProxy.sgml | 18 +-----------------
 1 file changed, 1 insertion(+), 17 deletions(-)

diff --git a/LDP/howto/linuxdoc/TransparentProxy.sgml b/LDP/howto/linuxdoc/TransparentProxy.sgml
index 8cfbae8b..0d191303 100644
--- a/LDP/howto/linuxdoc/TransparentProxy.sgml
+++ b/LDP/howto/linuxdoc/TransparentProxy.sgml
@@ -4,7 +4,7 @@
 
 <title>Transparent Proxy with Linux and Squid mini-HOWTO</title>
 <author>Daniel Kiracofe</author>
-<date>v1.11, January 2002</date>
+<date>v1.12, January 2002</date>
 <abstract>
 This document provides information on how to setup a transparent caching
 HTTP proxy server using only Linux and squid.
@@ -304,22 +304,6 @@ this is the only command needed.  2.2 kernels required two extra commands
 in order to prevent forwarding loops.  The infastructure of netfilter is 
 much nicer, and only this command is needed.
 </p>
-<sect1>What if I want to redirect packets generated on the squid box as well?
-<p>
-I am aware that a number of people are using squid and Transparent Proxy
-in small home networks.  In that case, the squid box happens to be a 
-personal machine as well, so they would like to redirect packets generated
-from the local web browser.  Thus, an additional command is needed.  
-</p><p><itemize>
-<item>iptables -t nat -A OUTPUT -p tcp --dport 80 -j REDIRECT --to-port 3128
-</itemize>
-<p>Note the the chain used is different (PREROUTING is for packets coming
-in from other boxen, OUTPUT is for locally generated packets) and I that I
-have omitted the interface (so packets going out any interface will be
-redirected.  If you have multiple interfaces, you could probably add the
-interface specification back in to only redirect packets going out certain
-interfaces).  
-</p>
 
 
 <sect>