From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: 'Peter Schobel' <pschobel@porchlight.ca>, netfilter@lists.netfilter.org
Subject: RE: Problems with Transparent Proxy using IPTables, Squid and 2.6 kernel
Date: Sun, 11 Jan 2004 09:00:48 -0800 [thread overview]
Message-ID: <200401111700.i0BH0oHu031652@server5.bandwidthco.com> (raw)
In-Reply-To: <F41C404D-4311-11D8-AFEE-000393677A36@porchlight.ca>
I haven't been following all of this Peter, but it would seem you now need
to add a rule allow the packets to get through the FORWARD chain now that
they have been successfully REDIRECTED. Try something like:
$IPT -t filter -A FORWARD -i eth0 -p tcp --dport 3128 -j ACCEPT
-----Original Message-----
From: netfilter-admin@lists.netfilter.org
[mailto:netfilter-admin@lists.netfilter.org] On Behalf Of Peter Schobel
Sent: Friday, January 09, 2004 6:09 PM
To: netfilter@lists.netfilter.org
Subject: Re: Problems with Transparent Proxy using IPTables, Squid and 2.6
kernel
ok, I removed the error line and the cat autoconf line from the config.h and
got iptables 1.2.9 to compile against my kernel source and headers and
reinstalled
if i turn on ip_forward and try to access external sites, i get forwarded
through to the external page without problem
if i enable the iptables rule
iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT
--to-port 3128
my pages just time out when i try to access external sites
but if i try to access the proxyhost directly using http, it redirects me to
the proxy site without problem
i get exactly the same results using this rule
iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to-destination
$LOCALHOST:3128
does anyone have any idea why traffic destined for external sites will not
transparently redirect to squid for me?
does anyone have any idea as to what further steps I can take to
troubleshoot this problem?
Thx in advance,
Peter Schobel
On Thursday, January 8, 2004, at 09:33 PM, Alistair Tonner wrote:
> On January 8, 2004 03:05 pm, Peter Schobel wrote:
>> ok, I downloaded the source ball for iptables 1.2.9, and compiled
>> using
>>
>> make KERNEL_DIR=/usr/src/linux-2.6.0-1.107
>>
>> i got an error from config.h telling me to use the glibc version so i
>> symlinked /usr/src/linux-2.6.0-1.107 to /usr/include/linux/config.h
>>
>> then i compiled successfully and installed using
>>
>> make install KERNEL_DIR=/usr/src/linux-2.6.0-1.107
>>
>> without incident
>>
>> i checked the timestamp on the iptables binary to make sure that it
>> had been overwritten
>>
>> I rmmod'd all the iptables modules and then reloaded my iptables rule
>>
>> iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j REDIRECT
>> --to-port 3128
>>
>
> Ummm ... I don't understand where the error came from.... I'm using
a
> slackware based box with many upgrades
> (gcc glibc binutils and modutils....) my switch from 2.4.23 to 2.6.0
> required a binutils and modutils
> upgrade FIRST -- I would hope that RPM dependencies are in place to
> enforce this as it will likely
> apply to your situation ... when I rebuilt iptables source it went
> painlessly --- no error from config.h.
>
> I *DONT* like the relink .. I've a feeling this will break some
> inportant defines....
>
> what do you get for modprobe --version and ld -v ?
> I suspect your modutils is incorrect for 2.6.0
>
>> lsmod gives me
>>
>> Module Size Used by
>> ipt_REDIRECT 2048 1
>> iptable_nat 20140 2 ipt_REDIRECT
>> ip_tables 15104 2 ipt_REDIRECT,iptable_nat
>> ip_conntrack 28464 2 ipt_REDIRECT,iptable_nat
>>
>> iptables -t nat -L gives me
>>
>> Chain PREROUTING (policy ACCEPT)
>> target prot opt source destination
>> REDIRECT tcp -- anywhere anywhere tcp
>> dpt:http redir ports 3128
>>
>> Chain POSTROUTING (policy ACCEPT)
>> target prot opt source destination
>>
>> Chain OUTPUT (policy ACCEPT)
>> target prot opt source destination
>>
>> testing it reveals that it is still not working - did i do anything
>> wrong in the above steps? what further steps would you recommend to
>> troubleshoot this problem?
>>
>> Peter Schobel
>> ~
>
>
*****************************
Peter Schobel
Network Administrator
Porchlight.ca
Unlimited Internet
*****************************
In a world without walls or fences
We will have no need for gates or windows
*****************************
next prev parent reply other threads:[~2004-01-11 17:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200401082133.38574.Alistair Tonner <>
2004-01-09 3:58 ` Problems with Transparent Proxy using IPTables, Squid and 2.6 kernel Peter Schobel
2004-01-09 14:50 ` Unknown, Alistair Tonner
2004-01-10 2:08 ` Peter Schobel
2004-01-10 5:26 ` Unknown, Alistair Tonner
2004-01-11 17:00 ` Mark E. Donaldson [this message]
2004-01-12 20:09 ` Peter Schobel
[not found] <200401100026.01870.Alistair Tonner <>
2004-01-12 20:04 ` Peter Schobel
2004-01-12 20:57 ` Peter Schobel
2004-01-12 21:31 ` John A. Sullivan III
2004-01-12 22:45 ` Peter Schobel
2004-01-13 5:47 ` Arthur Meyer
[not found] <200401090950.56343.Alistair Tonner <>
2004-01-09 16:57 ` Peter Schobel
2004-01-08 16:56 Peter Schobel
2004-01-08 17:02 ` Antony Stone
2004-01-08 17:28 ` Peter Schobel
2004-01-08 17:35 ` Antony Stone
2004-01-08 18:28 ` Peter Schobel
2004-01-08 18:51 ` Antony Stone
2004-01-08 20:05 ` Peter Schobel
2004-01-08 21:07 ` Antony Stone
2004-01-08 21:45 ` Sven Schuster
2004-01-08 22:03 ` Peter Schobel
2004-01-08 21:56 ` Peter Schobel
2004-01-09 2:33 ` Unknown, Alistair Tonner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401111700.i0BH0oHu031652@server5.bandwidthco.com \
--to=markee@bandwidthco.com \
--cc=netfilter@lists.netfilter.org \
--cc=pschobel@porchlight.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox