Re: wccpv2 and L2 redirection

On Tue, 11 Nov 2003, John El-Rassi wrote:

> So i tried implementing wccpv2. to my dismay the cisco 3550 does not
> support wccpv2 with GRE packet redirection.

No problem in theory. L2 redirection just makes life a whole lot easier as
you don't need any GRE module, just normal interception rules to intercept
port 80 traffic at the cache server. Only drawback is that the cache
server must be locally attached to the same Ethernet segment as the
router.

> it must use Layer 2 redirection. so when i run squid with the wccpv2 i
> get the following errors on the cisco 3550 (off course i change both
> configs on cisco and squid wccp2_router and ip wccp version 2)
>
> 17:19:43: WCCP-EVNT:wccp_update_assignment_status: enter
> 17:19:43: WCCP-EVNT:wccp_update_assignment_status: exit
> 17:19:43: WCCP-EVNT:S00: Here_I_Am packet from 142.46.145.4 w/bad fwd method 00000001, was offered 00000002
> 17:19:43: WCCP-EVNT:S00: Here_I_Am packet from 142.46.145.4 with incompatible capabilites
>
> Questions
>
> 1. i was wondering if there has been anywork done to support
> wccpv2+Layer 2 (instead of GRE)

In general one can say that there has been very little work done on WCCPv2
for Squid and the WCCPv2 patch is best described as WCCPv1 using the
WCCPv2 protocol syntax

If it is the case that the WCCP protocol specifies the encapsulation
method the router should use when forwarding packets to the cache then the
Squid WCCPv2 patch needs to be extended with a parameter for specifying
this in the WCCP_HERE_I_AM packet. From a quick glance in the WCCPv2
Internet-Draft this does seem to be the case.

The above error message seems to confirm this.. if I am reading it
correctly the error says that the WCCP_HERE_I_AM packet wanted GRE
encapsulation.

> 2. what is causing the cisco (in wccpv1) to only redirect traffic when destined to itself.

Please explain this a little further. I am not sure exacly what you refer
to.

Regards
Henrik
Received on Tue Nov 11 2003 - 14:25:00 MST