Yep - ipchains redirect from ports 80 and 8080 to 3128.
But I've managed to get it working again - seems that wccp will only
work with the cisco if the cache is off the primary address on the
interface...
Thanks for your help,
Thomas
-----Original Message-----
From: francisv@dagupan.com [mailto:francisv@dagupan.com]
Sent: Wednesday, 11 July 2001 12:47 p.m.
To: thomas@radionet.co.nz
Subject: RE: [squid-users] Squid 2.4STABLE1 and wccp
You also have to make it hijack traffic from port 8080 or 3128 to port 80.
Did you follow the instructions on the Squid website?
-----Original Message-----
From: Thomas Salmen [mailto:thomas@radionet.co.nz]
Sent: Wednesday, July 11, 2001 6:01 AM
To: squid-users@squid-cache.org
Subject: [squid-users] Squid 2.4STABLE1 and wccp
Hi all,
I'm having a little trouble getting wccp working with a new Squid box (Linux
2.2kernel).
We have a Cisco 7200 with several transparent caches sitting directly off it
- its not
having any problems with the ones we already have in place, but it won't use
this new one.
As far as I can see, the wccp sessions are actually working properly (but
not) - netstat shows
the udp link between the linux box and the cisco as established, and the
cisco picks up the
squid, but seems to think its unavailable. Squid itself works - if you
specify it as a proxy
in a browser, you can surf through it without any problems.
The darned thing is, I had it working just fine at another ISP round the
corner from here with their
7200... so I'm sure its just something I've overlooked...
Anyone have any ideas?
Cheers,
Thomas
Received on Tue Jul 10 2001 - 19:16:32 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:01:05 MST