Jason Haar-2 wrote
> On 15/04/15 22:58, Amos Jeffries wrote:
>> Squid has zero control over what TCP connections the *client* opens.
>> You need to use tcpdump on the Squid machine, or machine(s) at the
>> other end of the WAN1/2 connections to see what the Squid->origin
>> traffic uses.
>
> Amos
On 15/04/15 22:58, Amos Jeffries wrote:
> Squid has zero control over what TCP connections the *client* opens.
> You need to use tcpdump on the Squid machine, or machine(s) at the
> other end of the WAN1/2 connections to see what the Squid->origin
> traffic uses.
Amos is so right. Stop fiddling ar
OK I got it, I added "ip route add" commands ,set up routing tables in
/etc/iptables2/rt_tables and everything is working fine now.
Although I could not get it worked by "tcp_outgoing_address" option, this
way it is working perfectly.
Thanks for the help.
--
View this message in context:
htt
On 15/04/2015 10:21 p.m., naishal0748 wrote:
> Hello,
>
> I received following reply from Amos.
>
> ---
>
> Welcome to the world of application layer gateways.
>
> There is no guarantee that IPv4 is being used outbound. You may in fact
> be using IPv6 to contact servers.
> All that
Hello,
I received following reply from Amos.
---
Welcome to the world of application layer gateways.
There is no guarantee that IPv4 is being used outbound. You may in fact
be using IPv6 to contact servers.
All that means is that you need to set a WAN1 IPv6 address in a second
tcp_
