[squid-users] TCP_TUNNEL

Kassir Bariq bariq.kassir at scania.com
Thu Dec 5 09:13:36 UTC 2019


Hi Awesome Squid Users 😊

I’m using Squid transparent proxy on AWS. I’m having a small problem, but I don’t really know what is happening!

From an EC2 in Private Subnet I’m making a request to AWS Endpoints using 443, and the request is going via Squid and says Connected, but unfortunately it is not working in the Client!

Checked the Logs and found that it is going via tcp_tunnel, but still not working in the client.

1575515309.361 20029 10.131.18.170 TCP_TUNNEL/200 430 CONNECT 52.46.200.112:443 - ORIGINAL_DST/52.46.200.112 -
1575515337.544 65650 10.131.18.158 TCP_TUNNEL/200 451 CONNECT 52.46.200.130:443 - ORIGINAL_DST/52.46.200.130 -
1575515490.666 20020 10.131.18.205 TCP_TUNNEL/200 430 CONNECT 52.46.196.121:443 - ORIGINAL_DST/52.46.196.121 -

Is there anything I can add to the config file that can fix this problem ?

Regards
Bariq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20191205/f24feed4/attachment.html>


More information about the squid-users mailing list