On 23/11/2015 7:25 a.m., Eliezer Croitoru wrote: > Hey Andre, > > There are couple things to the picture. > It's not only squid that is the "blame". > It depends on what your OS tcp stack settings are. > To verify couple things you can try to use the netstat tool. > run the command "netstat -nto" to see what is the timers status. > You can then see how long will a new connection stay in the established > state. > It might be the squid settings but if the client is not there it could > be because of some tcp tunable kernel settings. Eliezer is right. The TCP layer itself should be terminating the connection within a short time (30sec default) after the clients last packet. Even if you use the TCP level keep-alive feature, that works by ensuring small packets go back and forth between the Squid device and the user device to keep the router state alive. Something is making the TCP stack itself think the client device is still connected *and active* on the network. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
