Pfsense 2.2.3 + squid3 0.2.8 always getting tcp_miss
-
From the looks of your WA rules, pfSense is not your border router (WAN is in private IP space)? Is it possible that something upstream is interfering with squid's caching?
-
no is not. Im running pfsense on an VM for testing. but pfsense is the border router to the internet for my VMs. I dont think so that something from my pc is interfering. :(
-
My pfSense test box is a VM under vSphere 5.5U2. I'm out of ideas. I installed a default 2.2.3 instance, added the squid package with all defaults and then just changed the few values you see in my screens. Nothing else.
-
:( :'( thank you.
any one else any idea?
-
any one else any idea?
Your Speedtest link shows you are from Greece? I think I know what your problem is. Greece has no cache right now :(
(Sorry if my bad joke offends you. I'm not trying to make light of the problems facing the Greek people at the moment.)
-
dont worry I laught ;D
-
still nothing… any one? :'(
-
btw I forgot to tell you that Im running it on x64 "pfsense 2.2.3-release (amd64)" no idea if this is a problem
-
No, x64 is common and what I use for testing and production. 2.2.4 is out in a week or so. Maybe try again with that one.
-
I have just install 2.2.4
:'(
I have no clue why is this happening to me…. >:(
-
There isn't much there to show what you mean. The only duplicate in the list is the nVidia driver. The status codes beside the error give more context about what happened. Squid Log Wiki. Plus, that realtime view doesn't give as much detail as the real access.log. Quite often a miss is a miss even though the file has the same name because the file size is reported different than the other file with the same name. Anything ending in a ? is a query that changes the response dynamically.
-
hello,
Im still having problem on this topic. :'(
new pfsense installed and last version of squid3.
2.2.6+ 0.4.7
