Re: [squid-users] Squid 3.5 TAG_NONE/503 HIER_NONE

2018-05-22 Thread Amos Jeffries
On 23/05/18 06:30, Rejaine Monteiro wrote: > has now worked after inserting this parameter: > > dns_v4_first on > > the strange thing is that I had tried this parameter before, but it > had not worked (maybe I did something wrong) > That directive is a workaround for IPv6 or ICMP misconfigurati

Re: [squid-users] original_dst wrong when using intercept

2018-05-22 Thread Amos Jeffries
On 23/05/18 09:27, monopot wrote: > I'm trying to setup a Squid proxy to use in one of our AWS accounts. If I > put Squid in with a basic http/https filtering setup (no interception) it > all works great, but the problem is my company wants us to do HTTPS > interception so I need to use ssl bump.

Re: [squid-users] original_dst wrong when using intercept

2018-05-22 Thread Alex Rousskov
On 05/22/2018 03:27 PM, monopot wrote: > ssl_bump peek step1 all > ssl_bump peek step2 all > ssl_bump splice step3 all > ssl_bump terminate step2 all Sorry, I cannot answer your primary question, but please note that the above SslBump configuration is equivalent to ssl_bump peek all ssl_bump

[squid-users] original_dst wrong when using intercept

2018-05-22 Thread monopot
I'm trying to setup a Squid proxy to use in one of our AWS accounts. If I put Squid in with a basic http/https filtering setup (no interception) it all works great, but the problem is my company wants us to do HTTPS interception so I need to use ssl bump. Now if I set Squid up following the AWS

Re: [squid-users] Squid 3.5 TAG_NONE/503 HIER_NONE

2018-05-22 Thread Rejaine Monteiro
has now worked after inserting this parameter: dns_v4_first on the strange thing is that I had tried this parameter before, but it had not worked (maybe I did something wrong) 2018-05-22 14:56 GMT-03:00 Alex Rousskov : > On 05/22/2018 10:54 AM, Rejaine Monteiro wrote: > >> debug_options ALL, 1

Re: [squid-users] Squid 3.5 TAG_NONE/503 HIER_NONE

2018-05-22 Thread Alex Rousskov
On 05/22/2018 10:54 AM, Rejaine Monteiro wrote: > debug_options ALL, 1 33.2 If the above is your actual debug_options line, then you should file a bug report that Squid accepts such a bogus debug_options value and then replace your value with something like "ALL,1" (without quotes). That may expo

[squid-users] Squid 3.5 TAG_NONE/503 HIER_NONE

2018-05-22 Thread Rejaine Monteiro
Hello guys, I had a squid-proxy (squid-3.5.21-5.3.1.x86_64) running on a OpenSUSE Leap 42.2 Everything is working well, access all the sites (http or https sites), except these two: www.uai.com.br or www.em.com.br  There is no blocking on the firewall (if bypass squid , access is normally d

Re: [squid-users] Cert download from AIA information succeeds yet Squid reports ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY

2018-05-22 Thread Alex Rousskov
On 05/21/2018 10:59 PM, Ahmad, Sarfaraz wrote: > Websites where certificates just share AIA information using CA-issuer > method, those work just fine. > >   > > But try this one, https://community.verizonwireless.com/welcome (this > gets bumped in my setup) > > Here the AIA information Is prov

Re: [squid-users] NetfilterInterception: NF > getsockopt(SO_ORIGINAL_DST) errors

2018-05-22 Thread kAja Ziegler
On Tue, May 22, 2018 at 12:24 PM, Amos Jeffries wrote: > On 22/05/18 22:06, kAja Ziegler wrote: > > This is strange because I don't use any NAT iptables/netfilter rules on > > this server: > > > > [root@...]# iptables -n -L -v -t nat > > Chain PREROUTING (policy ACCEPT 26964 packets, 1870K bytes)

Re: [squid-users] NetfilterInterception: NF > getsockopt(SO_ORIGINAL_DST) errors

2018-05-22 Thread Amos Jeffries
On 22/05/18 22:06, kAja Ziegler wrote: > This is strange because I don't use any NAT iptables/netfilter rules on > this server: > > [root@...]# iptables -n -L -v -t nat > Chain PREROUTING (policy ACCEPT 26964 packets, 1870K bytes) >  pkts bytes target     prot opt in     out     source            

[squid-users] NetfilterInterception: NF > getsockopt(SO_ORIGINAL_DST) errors

2018-05-22 Thread kAja Ziegler
Hi, this question/problem is extracted from the other email "The right way how to increase max_filedescriptors on Linux". *- my environment:* CentOS 6.9 Squid 3.1.23 / 3.4.14 IPv4 and IPv6 addresses on interfaces *- error and warning messages from cache.log:* IpIntercept.cc(137) NetfilterInt

Re: [squid-users] The right way how to increase max_filedescriptors on Linux

2018-05-22 Thread kAja Ziegler
On Mon, May 21, 2018 at 3:29 PM, Amos Jeffries wrote: > On 22/05/18 00:08, kAja Ziegler wrote: > > Hi, > > > > I want to ask, if it is really needed to use ulimit or > > /etc/security/limits.conf to increase max_filedescriptors value? From my > > testing, it seems not. > > Sometimes yes, someti