Regarding: "Squid is missing a logcheck rule to ignore the seemingly routine and impossible to stop message that follows:
Dec 4 14:04:11 ursine squid[2869]: parseHttpRequest: NF getsockopt(SO_ORIGINAL_DST) failed: (92) Protocol not available" The above error is a useful indicator of bad config. It is produced when receiving non-NAT intercepted requests on a port flagged as receiving ONLY NAT intercepted requests. The above message will be produced once for every ten or so non-NAT message the system NAT table fails to locate. This is resolve by using two ports like so: http_port 3128 http_port 10000 transparent .. with the firewall interception passing traffic to Squid 10000. Regular users configured for use of 3128. Amos Squid Team -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
