Search squid archive

Re: CentOS/Squid/Tproxy but no transfer

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2009/7/14 Amos Jeffries <squid3@xxxxxxxxxxxxx>:

> Aha!  duplicate syn-ack is exactly the case I got a good trace of earlier.
> Turned out to be missing config on the cisco box.

Do you have an example of this particular (mis) configuration? The
note in the Wiki article isn't very clear.

> The Features/Tproxy4 wiki page now makes explicit mention of this and
> several possible workarounds.

> The problem seems to be that the WCCP automatic bypass for return traffic
> uses IP, which is not usable under TPROXY. Some other method of traffic
> detection and bypass must be explicitly added for traffic
> Squid->Cisco->Internet. In the old tproxy v2 configs (which still apply)
> the class 90 was used for this.

.. uhm, again, that isn't very clear. "automatic bypass" isn't
explicitly configured anywhere nor do I see anything in the tproxy2
config which mentions bypass with class 90. So I'm very curious what
exactly it is that people are seeing, with what exact
configuration(s).


Adrian


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux