According to the FAQ, and postings I have read in the mailing list archives
I should be able to run Squid through a socks firewall by just starting
it with runsocks
When I try this (using the Debian Squid 2.1.2 and Debian runsocks) I get
messages in my cache.log complaining that it is unable to run the
/usr/lib/squid/dnsserver processes.
When I run squid without the runsocks line it all works (except that I can not
access hosts beyond my firewall. I can use 'runsocks telnet' to access
hosts beyond the firewall. My socks.conf says to go direct for hosts on my
local network, and to 127.0.0.1
If I use an external authenticator (I really want to authenticate against an
LDAP directory) then this works if I do not use socks, but when I do I get
similar messages about being unable to start the authenticator processes.
My feeling is that there is some problem with communicating with helper
processes when runsocks is used.
I suspect that the people reporting success may have been using Squid 1.x
Has anyone succeeded in getting Squid 2.x working with socks ?
John Lines
p.s. For some items in the FAQ it might be useful to have a note to say that
they refer to Squid 1.x - for example there is a description of how to
go out through a fwtk firewall, but (according to my squid.conf and messages
I came across in the archives) this is done differently for 2.x
Received on Wed Mar 03 1999 - 07:12:38 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:45:07 MST