Re: [squid-users] NF getsockopt(SO_ORIGINAL_DST) failed: (92) Protocol not available

On Mon, 24 May 2010 14:12:01 +0000, sameer khan <khanzadap_at_hotmail.com>
wrote:
> Hi
>
> i am getting this in my cache.log, what this error mean ? is there any
> misconfiguration ?
>
>
> clientNatLookup: NF getsockopt(SO_ORIGINAL_DST) failed: (92) Protocol
not
> available
>
>
> My settup
>
> <*> Squid Cache: Version 2.7.STABLE6
> configure options: '--enable-async-io' '--enable-icmp' '--enable-snmp'
> '--enable-cache-digests' '--enable-follow-x-forwarded-for'
> '--enable-storeio=aufs,ufs,null,diskd,coss'
> '--enable-removal-policies=heap,lru' '--with-maxfd=65535'
> '--disable-ident-lookups' '--enable-truncate' '--enable-linux-tproxy'
> '--enable-linux-netfilter' '--enable-large-cache-files'
>
> <*> Kernel 2.6.31.13
>
> <*> Debain lenny 5.04
>
> machine is setup in bridge mode, with ip configured on br0 interface.
>
> any help will be much appreciated.

This message means that Squid received a request but the kernel has no NAT
tracking information about it's IP address.

In Squid-2.7 it appears on some requests if configuring both the "troxy"
and the "transparent" modes on the same port, or receiving normal proxy
traffic directly on a "transparent" flagged port.

Amos
Received on Tue May 25 2010 - 02:26:30 MDT