Re: [squid-users] Squid 3.1.0.3 WCCP2 not announcing itself to router?

Guy Helmer wrote: (sorry - replying to myself after further investigation) Guy Helmer wrote: Amos Jeffries wrote: I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0 + sslBump patches, but would like to move up to Squid 3.1 to resolve some quirks. Here is the wccp configur

Re: [squid-users] Squid 3.1.0.3 WCCP2 not announcing itself to router?

(sorry - replying to myself after further investigation) Guy Helmer wrote: Amos Jeffries wrote: I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0 + sslBump patches, but would like to move up to Squid 3.1 to resolve some quirks. Here is the wccp configuration I was using w

Re: [squid-users] Squid 3.1.0.3 WCCP2 not announcing itself to router?

Amos Jeffries wrote: I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0 + sslBump patches, but would like to move up to Squid 3.1 to resolve some quirks. Here is the wccp configuration I was using with Squid 3.0: wccp2_router 10.10.10.1 wccp2_address 10.10.10.250 wccp2_servi

Re: [squid-users] Squid 3.1.0.3 WCCP2 not announcing itself to router?

> I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0 > + sslBump patches, but would like to move up to Squid 3.1 to resolve > some quirks. > > Here is the wccp configuration I was using with Squid 3.0: > wccp2_router 10.10.10.1 > wccp2_address 10.10.10.250 > wccp2_service dynam

[squid-users] Squid 3.1.0.3 WCCP2 not announcing itself to router?

I had a WCCP2 configuration (using a gre tunnel) working with Squid 3.0 + sslBump patches, but would like to move up to Squid 3.1 to resolve some quirks. Here is the wccp configuration I was using with Squid 3.0: wccp2_router 10.10.10.1 wccp2_address 10.10.10.250 wccp2_service dynamic 80 wccp2_