On Sat, Oct 07, 2006, Shaun Skillin (home) wrote: > I haven't tried with tproxy, but I did get the same error message on my > 3550. I just changed the forward method to L2 and return method to GRE > (just as the switch asked for) and it's working (though no idea why > Cisco wants different methods). I've managed to get WCCPv2 working on my 3550 with the suggested Cisco config (basic wccp stuff, stick proxy on a routed interface rather than through a SVI one.) Its a switch at heart so IIRC L2 redirection is (mostly) done in hardware. Just ignore the 0'ed counters inside "show ip wccp " commands and it should all be just fine. :) adrian > > -----Original Message----- > From: Adrian Chadd [mailto:adrian@xxxxxxxxxxxxxxx] > Sent: Thursday, September 14, 2006 5:55 PM > To: Henrik Nordstrom > Cc: Errol Neal; squid-users@xxxxxxxxxxxxxxx > Subject: Re: Stuck - Tproxy+WCCPv2 Layer2 > > On Fri, Sep 15, 2006, Henrik Nordstrom wrote: > > tor 2006-09-14 klockan 17:43 -0400 skrev Errol Neal: > > > Henrik wrote: > > > >It means your switch-router is not (yet) supported by Squid. See > the > > > last page of bug 1696 for details. > > > > > > Thanks for the reply. I guess I'll go back to the drawing board.. > > > > Don't forget that one option on that drawing board is to make your > > switch-router supported by Squid.. Shouldn't be that complicated. > > Everything is documented in the WCCP2 draft, only that no one has > > implemented the needed code in Squid yet. > > Funnily enough, Steven Wilton is working on this. > > I've acquired a pair of older Cisco Cache Engines which I -hope- > will speak the mask assignment protocol. Steven and I will then > figure out why it isn't working and get it going. > > (Of course, I'm hoping that my Cisco 3550 here actually speaks the > mask assignment stuff rather than the hash map. If anyone here > has a Cisco 7600 or a Catalyst 6500 in a test lab somewhere then > please let me know. I'd really, really appreciate it..) > > > > > Adrian >
