Hello Frank,
I'm running SuSEFirewall2 and Squid from the 8.2 distribution. On an other internal machine, I run bind for DNS resolution and which is set as primary dns server for all clients. The Squid seems to be well configured, as it runs fine when the squid-port 3128 on the firewall is directly entered in the proxy settings of a browser.
I wanted to use the firewall feature to redirect traffic to the squid port, so I did the foloowing settings in SuSEfirewall: FW_SERVICES_INT_TCP="ssh 3128" FW_SERVICES_INT_UDP="" FW_SERVICES_INT_IP="" FW_SERVICE_SQUID="yes" FW_REDIRECT="192.168.30.0/24,0/0,tcp,80,3128"
where 192.168.30.0/24 is my "home" network.
Any http request should now be redirected via squid, but there seems to be an error with the URL transmission to squid, the FQDN is truncated, so squid gives me the error, when searching for computer.domain.tld/directory/somedoc.htm that /directory/somedoc.htm is no valid URL.
I'm not quite sure if I'm on the right track, but it seems to me as if in the first case you run a classic proxy, and in the second case you want a transparent proxy. There's a difference between the two, which results in a different proxy configuration. Bye Uli -- Ulrich Roth IMPACT Business & Technology Consulting GmbH Im Mediapark 8 / KölnTurm D-50670 Koeln Phone +49-221-93 70 80-29 Fax +49-221-93 70 80-15 E-Mail: roth@impact.de