Re: [squid-users] squid 2.6STABLE9 WCCPv2 CISCO 2600 w/bad recv_id 00000000

Hi,

thank you very much for helping me troubleshooting this.

What we found out was, that the message about "w/bad recv_id" happens only
once when squid is started.

My other problem was solved by using the standard wccp2_service instead of the
dynamic one.
Finally, and most embarrassing to admit, by fooling around with different
kernels, I had lost my gre tunnel and therefore made successfull url
redirecting impossible....

The gre tunnel is back up and the redirecting is working fine.
Now I just need to adjust my helper software to accept the additional group
parameter (the url_rewrite helper).

Thanks to all of you especially Henrik!

You guys rock!

Regards,
Martin

On Thursday 08 February 2007 20:05, Henrik Nordstrom wrote:
> tor 2007-02-08 klockan 11:56 -0500 skrev Martin Kobele:
> > For now I use one squid and one router. But once I get this to work, I
> > plan on using 2 routers and most likely a second squid. Thus the dynamic
> > configuration.
>
> The standard 0 (http) service is fine. The service definitions is just a
> pattern on what kinds of packets to redirect.
>
> > wccp2_service dynamic 97 password=exPAS12
> > wccp2_service_info 97 protocol=tcp flags=src_ip_hash,ports_source
> > priority=240 ports=80
>
> This wccp service definition does not match client web requests. It
> matches only server responses to client web requests. Such service is
> only meaningful in tproxy enabled setups, and only in combination with
> the standard 0 service..
>
> Btw the "standard 0" (http) service is more or less equivalent to
>
> protocol=tcp flags=dst_ip_hash priority=240 ports=80
>
> Regards
> Henrik
Received on Fri Feb 09 2007 - 07:05:04 MST