Re: cvs commit: squid/src cf.data.pre wccp2.c

From: Reuben Farrelly <reuben-squid-dev@dont-contact.us>
Date: Thu, 25 May 2006 20:03:42 +1200

Hi Paul,

On 25/05/2006 7:51 p.m., Paul P Komkoff Jr wrote:
> Replying to Reuben Farrelly:
>> I'll test this assumption out tonight. I am running 12.4(6)T2 at the
>> moment and
>> seeing that problem. I'll do some more testing tonight on this with some
>> older
>> mainline software on a 1721.
>
> I think this behavior wis present in all IOS versions.

Seem so. I have just tested 12.3(19), 12.4(8) and 12.4(6)T - same problem on
all versions. I am assuming this is a platform independent thing - I'm using
low end routers to test.

What is interesting is that WCCPv1 works just fine with the same code.

>> Did you open a case up with the TAC about this? If so, what was the case
>> number? My router is under maintenance so I've the option of doing that if
>> you
>
> No, I don't have support contract of enough level to do this :)

I do, but I've not the expertise to know about WCCP to take on the TAC. That's
a possible avenue to take this but it won't fix the immediate problem.

>> haven't already tried to....however my past experience is that the
>> frontline TAC
>> people often tend to shy away once you start talking third party (ie non
>> cisco)
>> software.....
>
> As every proprietary software vendor do :)

RFC compliance then becomes nothing more than marketing hype if the vendor isn't
interested in actually maintaining and fixing bugs that increase RFC compliance
or fix bugs relating to this.

>> If it is an RFC compliance problem in IOS it would be good to get this fixed
>> going forward, I guess. Or at least have it documented.
>
> Right now we need to have working workaround because many people
> around the world may be unable to upgrade their IOS but they should be
> able to use newer linux kernel on their proxy servers :)

Yes, I agree entirely. But to have any hope of not having the workaround, it
needs to be fixed properly going forward.

I should dust off the old CE500 cache engine I have here (it's now obsoleted by
much more modern gear, it's sitting in the spare room taking up space) but it
will do WCCPv2 I think...might be interesting to see what it sends over the wire
compared to what squid-2.6 does.

You may wish to view and add comments to
http://www.squid-cache.org/bugs/show_bug.cgi?id=1584 where this WCCPv2 problem
is being tracked.

reuben
Received on Thu May 25 2006 - 02:03:42 MDT

This archive was generated by hypermail pre-2.1.9 : Thu Jun 01 2006 - 12:00:04 MDT