in Squid 3.5 running on Debian 9
I'm back to square one then, and it looks like there is no way to tell Squid to
use the same connecting ip for the outgoing ip, which is what I need.
On Thu, Oct 5, 2017 at 3:49 AM, Amos Jeffries <mailto:squ...@treenet.co.nz>
wrote:
On 05/10/17 15:0
You will need to transpareny redirect the traffic and not explicitly
pointing your browser to squid. Seems that the mentioned firewall rules are
correct. You will need a policy route also for the marked traffic.
On Oct 5, 2017 7:54 PM, "xpro6000" wrote:
I'm back to square one then, and it looks
I'm back to square one then, and it looks like there is no way to tell
Squid to use the same connecting ip for the outgoing ip, which is what I
need.
On Thu, Oct 5, 2017 at 3:49 AM, Amos Jeffries wrote:
> On 05/10/17 15:01, xpro6000 wrote:
>
>> I'm trying to setup tproxy with Squid 3.5 for the p
On 05/10/17 15:01, xpro6000 wrote:
I'm trying to setup tproxy with Squid 3.5 for the purpose of having the
same outgoing ip as the connecting ip. (I have thousands of IPs and I
can not add them one by one)
I started with a fresh install of Debian 9, installed Squid by
apt install squid
then
I'm trying to setup tproxy with Squid 3.5 for the purpose of having the
same outgoing ip as the connecting ip. (I have thousands of IPs and I can
not add them one by one)
I started with a fresh install of Debian 9, installed Squid by
apt install squid
then I added
http_port 3129 tproxy
to squi
