I think I’ve narrowed down the problem.
Looking at my server logs, I occassionally get a browse session where the first two or three octects of the IP are the same, but the last octet is different for every server request. I’m guessing that this is due to load balancing, or a proxy server (but really, this is just a guess). For example, a page load would look like this:
94.16.116.3 - [09/Mar/2007:10:31:51 -0500] “GET header”
94.16.116.15 - [09/Mar/2007:10:31:52 -0500] “GET css_file”
94.16.117.12 - [09/Mar/2007:10:31:53 -0500] “GET mint?js”
94.16.116.78 - [09/Mar/2007:10:31:54 -0500] “GET image”
94.16.116.214 - [09/Mar/2007:10:31:55 -0500] “GET content”
…
94.16.116.215 - [09/Mar/2007:10:31:55 -0500] “GET etc”
94.16.117.76 - [09/Mar/2007:10:31:55 -0500] “GET etc”
94.16.116.187 - [09/Mar/2007:10:31:56 -0500] “GET etc”
Session tracker groups all of these under a single IP, and Crushes just doesn’t see or count them at all.
Would there be a way to get Crushes to count these as well? I hope I’m not asking for too much here.