[squid-users] Client timing out when using squid as tproxy

Hi,

I'm trying to use squid as a transparent proxy. We're using ubuntu 10.04,
2.6.37 kernel, squid 3.1.10, and iptables 1.4.10. Server has 1 nic.

Ports 3128 and ports 3129 are specified in squid.conf.

When client browser proxy prefs are set to proxy server address, port 3128,
traffic passes through squid and returns to client.

When client browser proxy prefs are set to squid address, but using port 80,
traffic shows up in access.log, but never returns to client.

I'm not sure how to troubleshoot this.

I followed the howtos for comping squid for ubuntu:
http://wiki.squid-cache.org/SquidFaq/CompilingSquid#Debian.2C_Ubuntu

and for setting it up as a transparent proxy:
http://wiki.squid-cache.org/Features/Tproxy4

--------------

Here's the output of iptables

test_at_proxy:~$ sudo iptables -t mangle -L

Chain PREROUTING (policy ACCEPT)
target prot opt source destination
DIVERT tcp -- anywhere anywhere socket
TPROXY tcp -- anywhere anywhere tcp dpt:www
TPROXY redirect 0.0.0.0:3129 mark 0x1/0x1

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination

Chain DIVERT (1 references)
target prot opt source destination
MARK all -- anywhere anywhere MARK set 0x1
ACCEPT all -- anywhere anywhere

------------

Here's output from ip rule list:

test_at_proxy:~$ ip rule list
0: from all lookup local
32765: from all fwmark 0x1 lookup 100
32766: from all lookup main
32767: from all lookup default

------------

Here's output from ip route list

test_at_proxy:~$ ip route list
10.15.0.0/16 dev eth0 proto kernel scope link src 10.15.10.10
default via 10.15.0.1 dev eth0 metric 100

-----------

squid.conf

# Recommended minimum configuration:
#
acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
#acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
#acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged)
machines

acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
acl Safe_ports port 70 # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535 # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT

#
# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager

# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS
#

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost

# And finally deny all other access to this proxy
http_access deny all

# Squid normally listens to port 3128
http_port 3128
http_port 3129 tproxy
# We recommend you to use at least the following line.
hierarchy_stoplist cgi-bin ?

# Uncomment and adjust the following to add a disk cache directory.
cache_dir ufs /var/cache 100 16 256

# Leave coredumps in the first cache dir
coredump_dir /var/cache

# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320

-----------

Thanks for any help you can provide.

Marc

-- 
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Client-timing-out-when-using-squid-as-tproxy-tp3243429p3243429.html
Sent from the Squid - Users mailing list archive at Nabble.com.