simple squid + shorewall question

[albright]

I've got shorewall and squid (transparent) running on my desktop.

This works fine for computers on the lan. They all use the squid
proxy.

My question is: is it possible for my desktop to also
use squid proxy?

relevant rules in /etc/shorewall/rules

[666threesixes666]

can you set your browser to 127.0.0.1:3128 in proxy settings and get sites? ie use the proxy in non transparent mode.

[albright]

thanks but no dice, if I set the proxy in a browser manually, I get

[666threesixes666]

http://ubuntuforums.org/archive/index.php/t-1685730.html

from the output of the local box, you're clearly reaching squid. i think that post might help you. if it doesnt googling your error might help.

[albright]

thanks again ... I have tried googling to little avail

my problem is not a general problem of access; all computers
on the lan *except* localhost access the net via squid
perfectly.

only localhost gets the error if I set the proxy manually, or,
if no proxy set, localhost retrieves directly from the net
ignoring squid's proxy

I think the problem is that shorewall cannot redirect
traffic from the net to localhost via proxy because the
proxy is running on localhost, so redirects would loop
and squid couldn't get to the net. To put it another way,
localhost has to have access to the net for squid to
get content, but I want localhost to query squid for
content which entails a redirect of localhost away
from the net (if you see what I mean )

This looks impossible but I suspect there is
a way to do it somehow ...????
_________________
.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme)

[666threesixes666]

in browser proxy settings try keeping port the same, but try 0.0.0.0, localhost, 127.0.0.1, and finally the boxes internal lan ip address (ie 10.0.0.2, 192.168.0.2)

[albright]

further research into squid, shorewall and iptables suggest this answer

1. turn off shorewall's redirection rules
2. add these iptables commands after shorewall starts: