Angela is correct.
If you set client_netmask to 255.255.255.255 it will block ip addresses
from being logged. That is the whole point in client_netmask.
Here's the tag, from the documentation:
# TAG: client_netmask
# A netmask for client addresses in logfiles and cachemgr output.
# Change this to protect the privacy of your cache clients.
#
#client_netmask 255.255.255.255
What you want to do, is comment out the client_netmask feature.
Regards,
Tim Rainier
"Angela Burrell" <[EMAIL PROTECTED]>
07/07/2004 03:59 PM
To: <[EMAIL PROTECTED]>
cc: "squid users" <[EMAIL PROTECTED]>
Subject: RE: [squid-users] FW: no client IP address
A question: Why would you set the netmask to 255.255.255.255?
This effectively filters out the entire IP address... ?
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: July 7, 2004 12:37 PM
To: [EMAIL PROTECTED]
Subject: [squid-users] FW: no client IP address
I have a RedHat Linux server running Squid. My squid.conf file has the
client_netmask set to 255.255.255.255 but access.log is not capturing the
client ip address. I have restarted the server many times. As far as web
browsing, all users have access, and that is functional. However, the
following is what is logged into access.log:
proxy - - [07/Jul/2004:11:15:59 -0500] "GET http://www.google.com/search?
HTTP/1.0" 200 18902 TCP_MISS:DIRECT
proxy - - [07/Jul/2004:11:16:01 -0500] "GET
http://www.google.com/images/logo_sm.gif HTTP/1.0" 304 194
TCP_CLIENT_REFRESH_MISS:DIRECT
Any idea why the client ip address isn't there when the netmask is set to
255.255.255.255?
