On Fri, Dec 2, 2016 at 6:27 AM, klops wrote:
> Does this mean the squid box has to be the overall gateway for the internal
> network for transparrancy to work?
>
> The reason the proposed setup the way it is is because AWS VPC service has
> a service based NAT gateway which we have not low level
On 2/12/2016 6:27 a.m., klops wrote:
> Does this mean the squid box has to be the overall gateway for the internal
> network for transparrancy to work?
That is just one option. The other two are routing or tunnel, as I
mentioned in the second sentence.
>
> The reason the proposed setup the way i
Does this mean the squid box has to be the overall gateway for the internal
network for transparrancy to work?
The reason the proposed setup the way it is is because AWS VPC service has
a service based NAT gateway which we have not low level control over and it
is the default gateway. We want to
On 29/11/2016 10:33 a.m., kevin2345 wrote:
Hello, new to squid here. I'm trying to setup a transparent proxy with squid
for my internal hosts to reach outbound destinations. We are hosted in AWS
with a VPC setup and multiple subnets. The squid host is in a "public"
subnet that has outbound ac
Hello, new to squid here. I'm trying to setup a transparent proxy with squid
for my internal hosts to reach outbound destinations. We are hosted in AWS
with a VPC setup and multiple subnets. The squid host is in a "public"
subnet that has outbound access, while the other subnets are "private" wi
