Helo! i think i did almost everything right, firstly i made it in a test
enviroment with debian stretch running squid 3.5 and a windows server 2008
based domain controller, and it worked!
but when i tried to deploy it in the production enviroment running debian
stretch, squid 3.5 and windows serve
On 2/15/20 6:42 AM, Scott wrote:
>> From: Alex Rousskov
>> >a Client source IP address
>> >la Local IP address the client connected to
>> la Local listening IP address the client connection was...
>> > > icap::>
>>
>> If we add support for automated IP version
On 16/02/20 2:58 am, Felipe Polanco wrote:
> Thanks for the reply,
>
> Speaking strictly about TPROXY, are there any limitations compared to
> regular transparent intercept?
I assume that by "regular transparent intercept" you mean NAT intercept.
The primary difference between TPROXY and NAT ...
Thanks for the reply,
Speaking strictly about TPROXY, are there any limitations compared to
regular transparent intercept?
We have full control of the network and TCP routing.
We have done regular https intercept in the past and is working fine, but
now we would like to try TPROXY in bridging mo
On 16/02/20 12:42 am, Scott wrote:
>> Date: Fri, 14 Feb 2020 11:03:50 -0500
>> From: Alex Rousskov
>>
>> On 2/14/20 10:36 AM, Scott wrote:
>>
>>> I know it's derivable by other means, but it would be nice to have a
>>> logformat format code that provided the client and server IP version
>>> numbe
> Date: Fri, 14 Feb 2020 11:03:50 -0500
> From: Alex Rousskov
> To: squid-users@lists.squid-cache.org
> Subject: Re: [squid-users] [Feature request] add IP version to logformat
> format codes
>
> On 2/14/20 10:36 AM, Scott wrote:
>
> > I know it's derivable by other means, but it would be nice
