On 17/04/11 05:14, AZHAR CHOWDHURY wrote:
Hi,
I am following http://wiki.squid-cache.org/Features/Tproxy4 strictly
but failed to configure with CISCO router& WCCP2.
My setup as follow:
Clients PCs>-----------------------------[Core
switch]-------->>-----------[Edge CISCO Router with
WCCP2]--------------->Internet
||
[Squid 3.1.10 with Fedora 14, iptables, tproxy]
I can't configure Cisco router with following configuration as there
is no other interface there (only two, one connected with core
internal switch and rest with internet.
Please help me.
You have not stated anything about a problem. We cannot help unless we
now what is going wrong.
Finding the problem can be time consuming or tricky unless you are
fairly familiar with TCP. The "Troubleshooting" section on the tproxy4
page has many hints about what can go wrong and how to find/resolve them.
=============================
interface GigabitEthernet0/3.100
description ADSL customers
encapsulation dot1Q 502
ip address x.x.x.x y.y.y.y
ip wccp 80 redirect in
ip wccp 90 redirect out
interface GigabitEthernet0/3.101
description Dialup customers
encapsulation dot1Q 502
ip address x.x.x.x y.y.y.y
ip wccp 80 redirect in
ip wccp 90 redirect out
interface GigabitEthernet0/3.102
description proxy servers
encapsulation dot1Q 506
ip address x.x.x.x y.y.y.y
ip wccp redirect exclude in
=====================
Another question, how do check gre is configured at Linux?
"ip link show"
... lists the active interfaces. GRE should be one of them when open.
TPROXY and WCCP are relatively independent operations. Both equally
troublesome and complex.
It is worth checking that TPROXY is fully operational and working before
adding WCCP tunneling on top to complicate things further.
You can test that by having the squid box as router for your
workstation instead of the Cisco.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.12
Beta testers wanted for 3.2.0.6
