Hi Dean,
Quote:>Squid is capable of doing transparent proxying, but it does require the
help
>of the gateway to force all the traffic into Squid. You might find the
>information that you require at the http://www.linuxdoc.org site. There is
a
>HOWTO there which talks about setting up Transparent Proxying and what
needs
>to be done. I am not sure whether the document is also mirrored at the
>http://www.squid-cache.org site as well.
Thanks, (and thanks for the info on SquidGuard--got that working today), but
unfortunately, it was in the Transparent Proxy with Squid miniHOWTO that I
got the message that using Squid for transparent ftp proxying (its working
for http) wasn't such a good idea, and saw the recommendation for frox
(http://frox.sourceforge.net). Frox does look like it works OK, until I try
to get it to talk to the socks server, at which point it gives a "writeall:
Bad file descriptor" (or something very close to that) error message. Oh
well, I guess you can't have it all :(.
Unfortunately though, for the environment that I'm setting this up in, its
required that the content filtering work for both http and ftp. It looks
like frox supports routing the ftp requests into back to squid (it
translates them into http for input into squid) for caching purposes. I
don't care about the caching so much, but there might be a chance that this
would get around the problem with frox not working with socks--squid would
do the communication with socks. I'll give this a try tomorrow and see what
happens.
Thanks again,
--Andy