[squid-users] Transparent proxy with NTLM fake_auth for tracking purposes. Asking for trouble?

I have the following setup running right now and it appears to
work. However I am wondering if anyone might know of a reason this could
cause problems later.

Squid 2.5 Stable 1
configure
        --prefix=/usr/local/squid-2.5
        --enable-linux-netfilter
        --enable-auth=ntlm
        --enable-ntlm-auth-helpers="fakeauth no_check"

squid.conf
        auth_param ntlm program /usr/local/squid-2.5/libexec/fakeauth_auth
        auth_param ntlm children 1
        auth_param ntlm max_challenge_reuses 0
        auth_param ntlm max_challenge_lifetime 2 minutes

        acl authhost src 192.168.100.150/255.255.255.255
        acl Prince src 192.168.0.0/255.255.0.0
        acl Prince_WAN src 10.0.0.0/255.0.0.0
        acl passwdauth proxy_auth REQUIRED

        http_access allow authhost passwdauth
        http_access allow Prince
        http_access allow Prince_WAN

This is working perfectly for all users on the network with no proxy
setup.(Except users on 192.168.100.150)
Users of that IP have the proxy configured in the browser.

In case you are wondering the reasoning, the server at 192.168.100.150 is a
WinNT Terminal Server with 24 thin clients using it. I am trying to
account for our web usage and just getting the IP for the terminal server
didn't really help me. I am using Sarg to judge bandwidth allocation.

Thanks for any insight.
-Greg
Received on Wed Nov 27 2002 - 10:23:29 MST