W dniu 2012-12-20 10:48, Steve Hill pisze:
Squid's TPROXY sockets only seem to bind to the IPv4 stack - Some
Googling suggests it can be made to work with IPv6, but I've not found
anything explaining how. What am I missing?
Thanks.
Search the list archives.
I posted working config for ipv
W dniu 2012-12-12 11:53, Muhammed Shehata pisze:
Dears,
Is there any on can help
[...]
Hi;
Could you please tell me what is your deployment scenario?
Regards;
Pawel Mojski
W dniu 2012-01-03 23:41, Amos Jeffries pisze:
[...]
config?
tried 3.2.0.14?
All works fine now.
I made a mistake, squid had no rights to write var/run/squid/*.ipc files.
Thanks for your help Amos.
Regards;
Pawel Mojski
port. In cache.log file I found:
2012/01/03 15:11:05 kid1| commBind: Cannot bind socket FD 12 to [::]:
(13) Permission denied
repeated for all instances.
What I made wrong?
Thanks in advance;
Regards
--
Paweł Mojski
s
for me.
Regards;
--
Paweł Mojski
Hi Guys;
Regarding my problem with squid and ssl compilations I'd like to check
the version specified by author of the patch, I mean: Squid v3.1 (r9820)
this one.
How can I download it? I couldn't find any way for it, no cvs (auth
required) or svn.
Regards;
--
Paweł Mojski
Hi.
I'm using squid ssl interception in transparent proxy mode. But, of
course I have problem with invalid common name in any ssl transaction. I
found this: "...We believe it is technically possible to implement
dynamic certificate generation for transparent connections. Doing so
requires tur
rt=/etc/squid/cert.pem
And it works very fine with DNAT redirection.
Also, please anyone explain me what is the difference in deprecated
sslBump and new one ssl-bump.
I tried to upgrade squid, but to new sslbumping format was not working fine.
How should I use it?
Regards;
--
Paweł Mojski