[squid-users] Re: Protocol not available

I found this in the archives.

>> >> 2006/09/19 11:44:30| parseHttpRequest: NF getsockopt(SO_ORIGINAL_DST)
>> >> failed: (92) Protocol not available
>> >>
>> >> ...in our cache.log.
>> >>
>> >> Any idea on what is going on?
>> >
>> > Do you have the NAT iptable loaded?
>>
>> On the squid-box? No, I have not loaded iptable nat. Should I? NAT is
>> applied in a box before the packets reach squid.
>
> Then transparent interception will not work properly as there will not
> be any way for the proxy to find out the originally intended destination
> address.
>
> It will in most cases still work however as nearly all clients sends
> Host headers indicating the requested web site, but in such setups you
> should not be using the "transparent" option. Instead use "vport=80
> vhost" and always_direct, configuring your Squid as an accelerator for
> the whole Internet..
>
> Regards
> Henrik

I changed:
http_port transparent
to>
http_port 7080 vport=80 vhost

I also added:
always_direct allow all

Will this fix my problem of the cache dropping out on occasion for
certain IP's then just magically coming back?

Matt

> I am running Squid2.6STABLE9 as transparent proxy.
>
> What do these error messages mean?
>
> 2007/02/03 17:09:41| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST)
> failed: (92) Protocol not available
> 2007/02/03 17:14:43| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST)
> failed: (92) Protocol not available
> 2007/02/03 17:19:45| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST)
> failed: (92) Protocol not available
> 2007/02/03 17:24:47| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST)
> failed: (92) Protocol not available
> 2007/02/03 17:27:18| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST)
> failed: (92) Protocol not available
> 2007/02/03 17:29:49| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST)
> failed: (92) Protocol not available
> 2007/02/03 17:34:52| clientNatLookup: NF getsockopt(SO_ORIGINAL_DST)
> failed: (92) Protocol not available
>
> Sometimes some clients just quit working for few minutes and I notice
> these errors in cache.log.
>
> Matt
>
Received on Sat Feb 03 2007 - 18:35:39 MST