Dear Amos, Thank you for reply!
2008/5/20 Amos Jeffries <[EMAIL PROTECTED]>: > Anton V.G. wrote: >> >> Extra feedback >> >> started > > This one does appear to be a fatal condition occuring. If you can track it > in gdb or such debugger and get a stack trace of where its happening that > would be a great help. Can we force it to generate a core? If not, I'll try to debug it. >>> IPInterception.cc(169) NetfilterTransparent: NF >>> getsockopt(IP_TRANSPARENT) failed: (92) Protocol not >>> available > > This is bad. It means the TPROXY target is not working in your kernel. > That said squid should at least be handling it well. It working, but partially, it gives this notice once in ~20 requests, seems normal requests is in the access.log > > The only unexpected behaviour there is that the first bind failed with the > error it gave. > > Only you are in a position to say if 82.198.21.17:4008 was the squid > IP:random-port or if it somehow got the client IP and failed when using > that. It means it really tries to occupy the same port as the user connection? > > We first need to determine if 82.198.21.17:4008 was valid, and why its being > used. > > If you are up for some code delving we can work this out. I'll happily do what required! Just need to be guided a little. If more rapid communication is needed I'm available at google jabber (the same email) or ICQ 38119392 > > Amos > -- > Please use Squid 2.6.STABLE20 or 3.0.STABLE5 >
